This is going to drive me quite nuts if it continues. When a manual override is placed on a monitored file, it doesn't override it and prevent monitoring. This is Very Bad™ when the monitoring causes the application in question to crash instantly with a BEX. The only solution is to completely shut down Webroot or have no use of the program until TR fixes it. Kind of odd too, since scanning the folder the program is in shows a [G] for the executable, but a deep scan still shows a . Gathering more information as we speak, however it appears that the deep scan and realtime shield are not honoring local overrides while custom scans of folders are.