Forum Discussion
33 Replies
- Lord_Dwezel5 years agoNot applicable
Just bought the game yesterday with christmas deals was looking forward to getting back into XWing/TIE fighter, been a long time and have now spent hours over last two days just trying to get it to start.
Finally found this and a few other posts pointing at WEBROOT, being issue, which of course I use never had any issues with it in the 6+ years I have used it.
An issue that apparently keeps popping up, please tell me there is a better fix then basically disabling your security????
- Phakez5 years agoNot applicable
I have the same problem - error 2 with webroot. Is there an ETA on the fix or should I request a refund?
- BlaZe09295 years agoNot applicable
I'm also getting the good ole error 2 with Webroot. Why does it have to mess with it?!
- Jediphil215 years agoNot applicable
Webroot respond me that the fix its done now since this night and wont happen again after any update, do a scan and reboot PC, should be fine
- Jediphil215 years agoNot applicable
Message from webroot:
We've made a change to the back end, running a scan and rebooting the system should see the issue resolved. Further we added some rules in place that should prevent this from occurring again in the future.
Thank you,
Lucas Moore
Webroot Sr. Global Escalation Manager - N16H7-W1N65 years agoNot applicable
I made a fast scan, and I restarted the system : not fixed.
I made a complete scan and I restarted the system too : not fixed either. - Martinsito155 years agoNot applicable@phazonvirus I'm not expecting anything before the end of the Christmas break. Their track record ain't good regarding this issue.
- Martinsito155 years agoNot applicable@Phakez Just wait it out. They'll fix it until the next update whereupon it'll break again. It's a vicious cycle most of us with Webroot have been stuck in since launch. Until there's a permanent solution, you play, update, wait, and play again.
- Phakez5 years agoNot applicable
Does not work for me, I am still getting the error 🏈...
- Phakez5 years agoNot applicable
Why is this still not fixed?