Forums
New posts
Search forums
News
Security News
Technology News
Giveaways
Giveaways, Promotions and Contests
Discounts & Deals
Reviews
Users Reviews
Video Reviews
Support
Windows Malware Removal Help & Support
Mac Malware Removal Help & Support
Mobile Malware Removal Help & Support
Blog
Log in
Register
What's new
Search
Search titles only
By:
Search titles only
By:
Reply to thread
Menu
Install the app
Install
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Forums
Security
Video Reviews - Security and Privacy
Webroot SecureAnywhere Test and Review
Message
<blockquote data-quote="ifacedown" data-source="post: 244618" data-attributes="member: 18621"><p>You mean I still have to "unblock" it before Webroot will undo the damage? Will Webroot not prompt me that the process is malicious?</p><p></p><p>I have read also in other forums that Webroot' Journalizing feature is not flawless. Some users report that the "rollback" feature of Webroot failed in some instances making their systems really corrupt. Another flaw is that the WRDATA folder (if I remember it right) as reported by other users containing the journalizing logs of Webroot sometimes reach up to 9 GB in size - pathetic methodology in some cases then.</p><p></p><p>That is why I highly DOUBT the "wait-and-react"/"observe-then-cure" approach of Webroot - for me some damages CANNOT be undone. I will always prefer the PROACTIVE approach. The "wait-and-react" method of Webroot could be worse than the reactive approach of traditional AVs. But Webroot has the advantage of being always up to date in the cloud when online.</p><p></p><p>Anyway I love the lightness and speed of Webroot - I am using it right now, and tested it against 29 malwares, it quarantined 26.</p><p></p><p>Just saying my opinions - which could not be the truth.</p></blockquote><p></p>
[QUOTE="ifacedown, post: 244618, member: 18621"] You mean I still have to "unblock" it before Webroot will undo the damage? Will Webroot not prompt me that the process is malicious? I have read also in other forums that Webroot' Journalizing feature is not flawless. Some users report that the "rollback" feature of Webroot failed in some instances making their systems really corrupt. Another flaw is that the WRDATA folder (if I remember it right) as reported by other users containing the journalizing logs of Webroot sometimes reach up to 9 GB in size - pathetic methodology in some cases then. That is why I highly DOUBT the "wait-and-react"/"observe-then-cure" approach of Webroot - for me some damages CANNOT be undone. I will always prefer the PROACTIVE approach. The "wait-and-react" method of Webroot could be worse than the reactive approach of traditional AVs. But Webroot has the advantage of being always up to date in the cloud when online. Anyway I love the lightness and speed of Webroot - I am using it right now, and tested it against 29 malwares, it quarantined 26. Just saying my opinions - which could not be the truth. [/QUOTE]
Insert quotes…
Verification
Post reply
Top