Hello,
recently we've had multiple issues that Intercept X prevented installation or execution of software because it suposedly prevented "Lockdown".
It likes to block our remote maintainance software because of this, and today I was unable to install Datev on a client's PC for the same reason. In this case it wa "Malicious behavior ('Lockdown') prevented in Windows Command Processor" (so apparently the installer tried to access the CMD and that was blocked).
I turned off the manipulation protection and switched off all the toggles in the Settings. Didn't help. I also ticked the box to ignore this detection in Sophos Central, and it still didn't work (although maybe giving it 5 minutes to synchronize wasn't enough, but I ran out of time).
The strange thing is, on an identical PC, same network, same Intercept X, it worked, no issue. Didn't even have to turn anything off.
What can I do about this?
This thread was automatically locked due to age.