stormfront won't lanch plau error code on 02/03/2015 08:47 PM CST
Re: stormfront won't lanch plau error code on 02/03/2015 08:54 PM CST
A couple questions:
1) Which antivirus?
2) Was this working previously?
3) Did you recently change anything about Stormfront's settings (location of files, saving information from server to local, etc.)?
I would like to think we'd see an announcement about SFE if there was an update in the offing. Not having seen one, I am suspecting that if / since this worked before, something else changed.
Doug
1) Which antivirus?
2) Was this working previously?
3) Did you recently change anything about Stormfront's settings (location of files, saving information from server to local, etc.)?
I would like to think we'd see an announcement about SFE if there was an update in the offing. Not having seen one, I am suspecting that if / since this worked before, something else changed.
Doug
Re: stormfront won't lanch plau error code on 02/03/2015 08:59 PM CST
Re: stormfront won't lanch plau error code on 02/03/2015 09:23 PM CST
That's odd. Don't see why that would have any effect.
Assuming all other programs are running (if you're not sure, spend a bit of time testing), and assuming that Webroot hasn't notified you that it has quarantined some file, I think you should reboot - test - disable popups - reboot - test.
If it has quarantined a file, we'll have a bingo, and we can discuss options.
The only other option is a bad definitions file, which doesn't happen often (like, not really worthy of consideration not often), and if that's the case, it'll clear up in a while - but your only recourse right now would be to disable the AV until tomorrow. That is something I do not recommend.
Doug
Assuming all other programs are running (if you're not sure, spend a bit of time testing), and assuming that Webroot hasn't notified you that it has quarantined some file, I think you should reboot - test - disable popups - reboot - test.
If it has quarantined a file, we'll have a bingo, and we can discuss options.
The only other option is a bad definitions file, which doesn't happen often (like, not really worthy of consideration not often), and if that's the case, it'll clear up in a while - but your only recourse right now would be to disable the AV until tomorrow. That is something I do not recommend.
Doug