Just wanted to share an experience with an application that failed to get a successful file lock on a special database file on a file server when SG fileencryption was installed with version 8.3 and Patch 37 on Windows 10 Pro.
If the user manually edited the database file by windows explorer or text editor, there was no problem. But the Application FAUST by land-software.de (used for book library management) that was designed to work with the database file on the network share (Windows Server SMB), hung up when creating new entries. When using ProcessMonitor we could see that it was always trying to get file lock and the server responded with successful file lock ack but it failed anyway and the application could not write into the database file and hung up.
We ruled it out to Sophos Safeguard by uninstalling it after which it worked.
Creating a local bypass rule as found here in that KB worked around the issue and the application was usable again. The KB is mentioning only performance issues but it solves other issues too obviously.
https://support.sophos.com/support/s/article/KB-000038386?language=en_US
Reg Key: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\SophosDt2\Parameters]
REG_MULTI_SZ Name:"BypassRules"
Example: "BypassRules"="\\server\share\test\*"
On the network share are encrypted files, so excluding the whole share was not a solution.
This thread was automatically locked due to age.
