DBin Posted September 20, 2017 ID:1165735 Share Posted September 20, 2017 We have a legacy in-house program that we need some users to run under restrictive permissions (basically execute only, no read rights). Starting on 9/20/2017, that program fails to run and the PC becomes unresponsive if Anti-Ransomware protection is enabled. If the user has full read rights on the executable, Anti-Ransomware has no problem with it. That wouldn't be too much of an issue if Anti-Ransomware honored the exclusion list, but adding either the folder containing the executable or the executable itself does not actually exclude it. It seems Anti-Ransomware wants to be able to read the executable even if it's in its execution list. Link to post Share on other sites More sharing options...
Porthos Posted September 20, 2017 ID:1165738 Share Posted September 20, 2017 5 minutes ago, DBin said: It seems Anti-Ransomware wants to be able to read the executable even if it's in its execution list. What drive is the executable on? Link to post Share on other sites More sharing options...
DBin Posted September 20, 2017 Author ID:1165740 Share Posted September 20, 2017 A network drive, specified by drive letter (didn't try to exclude the executable via UNC path). Link to post Share on other sites More sharing options...
Porthos Posted September 20, 2017 ID:1165750 Share Posted September 20, 2017 (edited) MB 3 currently has a known bug that keeps it from honoring exclusion unless it is on the Main "c" drive. @DBin Edited September 20, 2017 by Porthos Link to post Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now