Capture Client Interoperability with Microsoft Domain Controllers (DC)

Create Capture Client PATH Exclusion with Exclusion Mode as Interoperability.

Folder & Subfolder Exclusion :

File Exclusion :

Paths and Files to Exclude

    \Device\HarddiskVolume*\Windows\SoftwareDistribution\DataStore\
    \Device\HarddiskVolume*\Windows\security\database\
    \Device\HarddiskVolume*\Windows\System32\GroupPolicy\
    \Device\HarddiskVolume*\Windows\Ntds\
    \Device\HarddiskVolume*\Windows\Ntfrs\

For HyperV, also add these folders:

    \Device\HarddiskVolume*\ProgramData\Microsoft\Search\Data\Applications\Windows\
    \Device\HarddiskVolume*\Windows\System32\Wins\
    \Device\HarddiskVolume*\Windows\System32\LogFiles\
    \Device\HarddiskVolume*\Windows\SysWow64\LogFiles\
    \Device\HarddiskVolume*\ProgramData\Microsoft\Windows\Hyper-V\
    \Device\HarddiskVolume*\Program Files\Hyper-V\

For HyperV, also add these files:

    \Device\HarddiskVolume*\Windows\System32\dfsr.exe
    \Device\HarddiskVolume*\Windows\System32\dfsrs.exe
    \Device\HarddiskVolume*\Windows\System32\Vmms.exe
    \Device\HarddiskVolume*\Windows\System32\Vmwp.exe

Best Practices for Exclusions

When you make a path exclusion, we highly recommend that you add the exclusion to the smallest relevant scope of endpoints - a specific group. For example, do not add exclusions to the default policy of the default group. Create a group of endpoints that use the application to exclude.

This guide provides exclusion recommendations for applications that might cause compatibility problems or slowdowns. Use these recommendations if you encounter issues with a specific program.
The exclusion recommendations are based on field experience and recommendations from vendors. Use them if you experience interoperability issues or performance degradation from a specific application.

Also see this Microsoft article and follow the recommendations.