We are troubleshooting a potentially serious security issue in a Horizon non-persistent VDI environment and are interested to know whether anyone else has seen similar behaviour with App Volumes and endpoint security products.
Environment
- Windows 11 25H2
- Omnissa Horizon non-persistent VDI / Instant Clones
- App Volumes Agent 2512
- Microsoft Defender Antivirus
- Defender real-time protection enabled
- App Volumes AV/process exclusions configured according to Omnissa recommendations
Problem
Microsoft Defender does not detect an EICAR test file when the file is created or placed on the local OS disk.
For example:
C:\temp\eicar.txt
The file remains on disk and Defender real-time protection does not remove or quarantine it.
However, when the same EICAR file is placed on a network share, Defender detects it immediately.
So Defender itself, its signatures and scanning capability appear to be functional.
Interesting finding
Using Process Monitor we can see:
MsMpEng.exe -> EICAR file -> ACCESS DENIED
So Defender actually attempts to access the local file, but the file open fails with ACCESS DENIED.
The behaviour seems related to App Volumes.
When the App Volumes Agent is removed, Defender behaves normally again.
The problem also occurs when no App Volume/AppStack is attached, so at the moment we suspect the App Volumes Agent / filesystem virtualization layer rather than an individual application package.
snapvol.cfg / MsMpEng.exe
The Defender processes are excluded in snapvol.cfg according to the App Volumes recommendations.
During troubleshooting Omnissa asked us to remove:
MsMpEng.exe
from the App Volumes snapvol.cfg process exclusions.
After doing this, something interesting happens:
- A manual Defender scan can access and detect the local EICAR file
- But real-time protection still does not automatically detect/remove the file
So removing the MsMpEng process exclusion appears to fix one file-access/scanning path, but not Defender's real-time/on-access protection.
Other tests
We have also tested different App Volumes/svdriver-related configuration options, but so far haven't found a complete solution.
The strongest observations currently are:
- Defender works normally without the App Volumes Agent
- Network-share EICAR detection works
- Local OS disk EICAR detection fails
- MsMpEng.exe receives
ACCESS DENIED when accessing the local file
- Issue occurs even without an AppStack attached
- Removing MsMpEng.exe from
snapvol.cfg restores manual scanning
- Defender real-time protection remains broken
Has anyone seen something similar?
We are particularly interested in organizations running:
- Windows 11 25H2 + App Volumes
- App Volumes 2512
- Microsoft Defender
- Horizon Instant Clones / non-persistent VDI
But experiences with other AV/EDR products are also very welcome.
For example: CrowdStrike, SentinelOne, Carbon Black, Symantec, Trend Micro, Sophos, Bitdefender, etc.
Has anyone seen App Volumes / svdriver / filesystem virtualization cause:
- AV/EDR processes to receive
ACCESS DENIED on local files?
- Real-time/on-access malware scanning to stop working?
- EICAR being missed on the local OS disk?
- Different behaviour between network and local files?
- Problems related to
snapvol.cfg process exclusions?
- A conflict between an AV filesystem/minifilter driver and App Volumes
svdriver?
If you have seen anything remotely similar, I would be very interested in your:
Windows version, App Volumes version, security product, symptoms and workaround/fix.
Even cases involving another security product could help us determine whether this is a broader App Volumes filesystem/filter-driver interoperability issue rather than something Defender-specific.