J
J. Branco
Guest
Disks are mounted read-only in
C:\FADIA-T\VHDM\folder\0\
I've added exclusions for
C:\FADIA-T\VHDM\*\*\*\*
Using MPCmdRun.exe -CheckExclusion -path "C:\FADIA-T\VHDM\folder\
Using MPCmdRun.exe -CheckExclusion -path "C:\FADIA-T\VHDM\folder\0
each shows excluded
but the sub-folder (root of the mounted VHD) returns not excluded with "C:\FADIA-T\VHDM\folder\0\folder\ [Device\HarddiskVolume#\] is not excluded.
I am not concerned about scanning these VHD(x)'s because they are created on a mostly secure capture machine.
My apps that are in these VHD's run incredibly slow since switching to MS Defender with ATP. I don't need these files scanned when the disks are mounted or content is accessed
I can't find a way to tell Defender to not scan these Virtual disks or paths.
Microsoft had a similar problem with FSLogix but somehow fixed with a definition update.
More...
C:\FADIA-T\VHDM\folder\0\
I've added exclusions for
C:\FADIA-T\VHDM\*\*\*\*
Using MPCmdRun.exe -CheckExclusion -path "C:\FADIA-T\VHDM\folder\
Using MPCmdRun.exe -CheckExclusion -path "C:\FADIA-T\VHDM\folder\0
each shows excluded
but the sub-folder (root of the mounted VHD) returns not excluded with "C:\FADIA-T\VHDM\folder\0\folder\ [Device\HarddiskVolume#\] is not excluded.
I am not concerned about scanning these VHD(x)'s because they are created on a mostly secure capture machine.
My apps that are in these VHD's run incredibly slow since switching to MS Defender with ATP. I don't need these files scanned when the disks are mounted or content is accessed
I can't find a way to tell Defender to not scan these Virtual disks or paths.
Microsoft had a similar problem with FSLogix but somehow fixed with a definition update.
More...