Solved
using another anti virus for offline protection

hi ,since sometimes i'm not in places with Internet access i'm going to install an antivirus(maybe nod32) along side the webroot for offline protection because offline protection in webroot is not as brilliant as online protection(when it can contact the cloud) what i' m asking is, is it fully compatible with other antivirus? i know that it is compatible but when i say fully i mean every layer of it's protection(specially rollback and journaling and behavior monitoring ) are working without any problem when an antivirus is along side secure anywhere with adding webroot to it's exclusions .
Best answer by shorTcircuiT
First: my opinion. :-) There isn't really a need for a backup AV: WSA stores the info as to what files should be monitored on the hard drive, and any new files encountered while offline are monitored by default until a connectioc to the Cloud is made to verify things. WSA also will still detect any malicious activity while offline: that is built in and not a part of the Cloud. The definitions are in the Cloud, but the actual monitoring for files doing bad things is all rifht on the computer and active when offline. Anything that might still slip past can be reversed by the monitoring/journaling.
Second: YES. WSA is built so that it is compatible with other AV solutions, and while I do not use a second there are quite a few here who do. One tip is to install the other AV first: while WSA is compatible the other installer doesn't know that and it WILL complain.
A second tip is to 'over-ride' the WSA executable in the other AV, amd over-ride the other AV within WSA to keep them from flagging each other as a risk.
Give it a try and let is know if you have problems: chances are someone here can help work things out if you do encounter any kinks.
View originalSecond: YES. WSA is built so that it is compatible with other AV solutions, and while I do not use a second there are quite a few here who do. One tip is to install the other AV first: while WSA is compatible the other installer doesn't know that and it WILL complain.
A second tip is to 'over-ride' the WSA executable in the other AV, amd over-ride the other AV within WSA to keep them from flagging each other as a risk.
Give it a try and let is know if you have problems: chances are someone here can help work things out if you do encounter any kinks.
Reply
Login to the community
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.