cjtwestwood
Contributor
Contributor

This workaround hasn't worked for me. I added the following to my snapvol.cfg in my writable app volume but it doesn't appear to have had an effect. The svchost process associated with the AppReadiness service still uses a consistent 30% CPU.

I submitted a case with VMware last week but they have not yet reached out to me.

SAMPLE SNAPVOL.CFG:

################################################################

# Registry exclusions

################################################################

exclude_registry=\REGISTRY\MACHINE\SOFTWARE\Microsoft\Windows Search\VolumeInfoCache

os=64

exclude_registry=\REGISTRY\MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows Search\VolumeInfoCache

os=any

# https://communities.vmware.com/thread/616037

exclude_registry=\REGISTRY\MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Appx

include_registry=\REGISTRY\MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Appx\AppxAllUserStore\Applications

exclude_registry=\REGISTRY\MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Appx

exclude_registry=\REGISTRY\MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\AppReadiness

################################################################# Registry exclusions################################################################
exclude_registry=\REGISTRY\MACHINE\SOFTWARE\Microsoft\Windows Search\VolumeInfoCache
os=64exclude_registry=\REGISTRY\MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows Search\VolumeInfoCacheos=any
# https://communities.vmware.com/thread/616037exclude_registry=\REGISTRY\MACHINE\SOFTWARE\Microsoft\Wi...

Reply
0 Kudos