Any thoughts or experiences on this? Is it wise to tell Sophos not to scan a directory?
For Sophos adding the C:\Windows\CSC\ folder to the Active Scanning exceptions list can resolve the issue. The CSC folder is for offline caching of files and folders when that feature is enabled on a network drive. The issue described above can actually be caused by the active scanning of the CSC folder even when offline file caching is turned off. It may also be necessary to explicitly provide exceptions for any files inside the folder, which can be done with wildcards using Sophos’ wildcard syntax. The usable wildcards in Sophos are the ? and * symbols, where ? is used for filenames and * is used for extensions. A known solution is also to add the exclusion “c:\windows\csc\????????????????????????????.*” to the Sophos policy.
Sometimes adding the C:\Windows\CSC\ folder or files inside it to the Active Scanning exceptions list will not fully resolve the stability issue. In these cases, a user may need to add the drive letters of any mapped network drives to the exclusion list as well, so that Sophos does not attempt to scan the mapped network drives for viruses. This should not cause a security problem as presumably the fileserver that is hosting the network drives will have its own antivirus solution, which will continue to scan the drives on its own.