Skip to main content

Veeam v13 + Hyper-V – AAP not working (no production checkpoints) → FIX

  • May 6, 2026
  • 3 comments
  • 52 views

Hi everyone,

just wanted to share something we hit recently after deploying Veeam B&R v13 in a Hyper-V environment.

The issue

After the upgrade, Application-Aware Processing stopped working.

Symptoms:

  • No Hyper-V production checkpoints
  • Multiple VMs affected
  • Happening across different customers

What we checked

We went through all the usual stuff:

  • Firewall → OK
  • Permissions → OK
  • VSS → OK
  • Integration services → OK

Everything looked fine… but still no AAP.

The cause

After a long search, we found a post from mazvazzeg that pointed us in the right direction.

Turns out it’s a wrong registry value for the Hyper-V VSS service (vmicvss).

Path:

 
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\vmicvss

Wrong value in ImagePath:

 
%systemroot%\system32\svchost.exe -k VeeamHvVssGroupstemNetworkRestrictedRedirectionGuard -p

This basically prevents the service from starting.

The fix

Change it to:

 
%SystemRoot%\System32\svchost.exe -k VeeamHvVssGroup -p

After that:

  • Service starts correctly
  • AAP works again
  • Production checkpoints are created 👍

 

We’re still waiting for feedback from Veeam on whether this is officially supported or if there’s a better fix.

 

This is the original post: https://www.reddit.com/r/Veeam/comments/1std7jf/veeam_hyperv_vss_application_aware_processing/?tl=de

 

Hope this helps someone 👍

Hicham

 

3 comments

eblack
Forum|alt.badge.img+2
  • Influencer
  • May 6, 2026

Interesting, I’m going to have to look into this. I may have something this fits. Thanks for sharing. 


Chris.Childerhose
Forum|alt.badge.img+21

Interesting fix as I don't use hyper-v but would definitely check this out. Thanks for sharing with the community.


coolsport00
Forum|alt.badge.img+22
  • Veeam Legend
  • May 6, 2026

Hey ​@hicham.laz ..welcome to the Community! I’ve seen a few posts here & there where users were running into issues with VBR v13 and HV, but not this one yet. Appreciate you sharing your fix. No doubt this will help others who experience this.

Best.