Create the following Agent Config: to apply automatic detection configuration to all of your endpoints:
When App Volumes applications are present on the desktop, all writes that are happening on the desktop to any files and the registry are redirected to a writable volume. In the absence of a writable volume, an implicit writable volume (a scratch space) is created on C:\{00000000-0000-0000-0000-000000000000}\SVROOT that will keep all the changes. This may have a negative effect on the path-based approvals. Modified files will not be approved after virtualization is started because the actual file path will be different from the approved path.
App Control does not support Writable Volumes. It is important to prevent the App Control agent database from becoming corrupted. To do this you will need to exclude App Control from being copied to a Writable Volume. In the App Volumes snapvol.cfg file typically found in either (per this KB):
%SVAgent%\Config\Default\snapvol.cfg %SVAgent%\Config\Custom\snapvol.cfg
Please add the following:
# Parity exclude_path=\ProgramData\Bit9 exclude_registry=\REGISTRY\MACHINE\SYSTEM\ControlSet001\services\ParityDriver