There’s a 14 page thread on the Webroot Community Forum that describes a very crippling issue where Webroot Antivirus started flagging Windows system files as malicious. Crippling said systems in the process. Now the company has a manual fix for this that was posted to its community forum that involves logging into the Webroot online console and manually creating override rules for all of the erroneously blocked files. Then wait until it takes effect which may be 24 hours or more.
Users are not happy about this and have taken to the community forum to vent their frustration. And rightly so because this is called a false positive. A case where a clean file is flagged as malicious and is blocked or deleted. To have Windows system files affected by this is a #EpicFail because this should never, ever happen.
Webroot has a lot of explaining to do after they help to clean up the damage that this event has caused.
Like this:
Like Loading...
Related
This entry was posted on April 25, 2017 at 12:45 pm and is filed under Commentary with tags Webroot. You can follow any responses to this entry through the RSS 2.0 feed.
You can leave a response, or trackback from your own site.
#EpicFail: Webroot AV Deletes Windows Files & Causes Serious Problems For Users
There’s a 14 page thread on the Webroot Community Forum that describes a very crippling issue where Webroot Antivirus started flagging Windows system files as malicious. Crippling said systems in the process. Now the company has a manual fix for this that was posted to its community forum that involves logging into the Webroot online console and manually creating override rules for all of the erroneously blocked files. Then wait until it takes effect which may be 24 hours or more.
Users are not happy about this and have taken to the community forum to vent their frustration. And rightly so because this is called a false positive. A case where a clean file is flagged as malicious and is blocked or deleted. To have Windows system files affected by this is a #EpicFail because this should never, ever happen.
Webroot has a lot of explaining to do after they help to clean up the damage that this event has caused.
Share this:
Like this:
Related
This entry was posted on April 25, 2017 at 12:45 pm and is filed under Commentary with tags Webroot. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.