I sent a mail to webroot to this morning. Wait and see...
Ok, Easy Anti-Cheat is doing his job well.
But why this message : "Launch Error: Failed to start the game ( 2 ) " ?
This is an error message, not a message for cheaters.
And the messages appeared at the same time for all of us. If we are Cheaters, it should have appeared at different times for each one of us.
And I don't understand what I have done to be considers as a cheater...
And why some of us who have take the risk to uninstalled webroot are not anymore considered as Cheaters after that ?
Squadrons, Easy Anti-Cheat and Webroot worked without any problem from 02 October 2020 to 28 October 2020
The first issue occured with the 28 Octbers 2020 1.3 uptade ; and this one was fixed with the 04 november 2020 2.0 update.
At this time Squadrons, Easy Anti-Cheat and Webroot worked without any problem.
The second issue occured with the 11 December 2020 4.0 update and was fixed the 12 December 2020 with a simple patch.
At this time Squadrons, Easy Anti-Cheat and Webroot worked without any problem.
The third issue occured with the 4.1 update and is still not fixed at this time.
So I think there is something between Webroot and Easy Anty-Cheat, but each issue occured because of one update. So I begin to think that something within the game causes the issue between Webroot and Easy Anti-Cheat.
I meant the Easy Anti Cheat comment sarcastically. Sorry, I should have been more clear. You are absolutely right that it is EA's issue and that they have the know-how to fix it and have not.
@Edgeshark wrote:I meant the Easy Anti Cheat comment sarcastically. Sorry, I should have been more clear. You are absolutely right that it is EA's issue and that they have the know-how to fix it and have not.
EAC has no problems with any other game with Webroot, complaining isnt going to fix anything. The only people that have fixed their problem and are able to play dont come back to this message board because their problems are fixed by going through Webroot from what ive gathered from this board. Like I said everyone should go through Webroot support to raise priority on fixing it on their servers because its cloud based.
I actually did contact Webroot and they told me to just delete it for now since they didn't have a fix for it. I uninstalled Webroot from my computer but it still shows the same message when I try to play.
As stated in the post above this problem has occurred and been fixed twice before without us having to contact Webroot. Combine that with all the other programs that play nice with Webroot and make your own deductions on where this fix need to come from.
@Ngabe1 are you getting failed to launch game ( 2 ) after uninstalling? I'm not exactly sure what's happening for you. i can play if i simply uninstall
@Edgeshark wrote:As stated in the post above this problem has occurred and been fixed twice before without us having to contact Webroot. Combine that with all the other programs that play nice with Webroot and make your own deductions on where this fix need to come from.
you actually think EA did anything the first 2 times? 🤣 that's rich. you should already know they don't fix problems. I have 2 games with licensing and authorization issues they still haven't fixed from 2015, this whole fiasco reminded me that EA games work better on console.
I have mailed webroot last week-end and I have a ticket in work in progress...
In the mean time, there is an update (4.2) today and the game run well now and before Webroot fixed my issue. I wish the issue will not appears with the next update.
I hope @siouxplice is right and Webroot will fixe my issue permanently in the following of my mail.
But I hope so than the issue will be fixed for eveyrone who had it and not just for those who signal it to Webroot.
I saw the update today and was foolishly hopeful.
Still can't play.
😞
I'm sade too read it ☹️
I am sur you already did it but I ask you : do you have restarted your computer after the update ?
I have launch the update, I restart my PC, I have launch the game... and it works.
May the Force be with you pilot !!!
I tried a reboot and still get the error.
Do you still have Webroot installed?
Yes, since the beginning I don't have taken the risk to uninstall it.
And I doesn't had to update anything else but the game itself.
I finally got a different error message after installing the update and restarting, error code 10011 which is related to EAC.
I sent a user report through origin crash tool but now when I start its back to the same old Failed to start game error.
I did purchase it from Epics Games and it has to open Origin to boot up, wonder if thats causing a problem too.
It is very very very frustrating !!
I accesced to the game a few minutes and hoping I could play tomorrow... so I closed it ^^ (I was expected to sleep well until tomorrow night).
But with your last posts, I tryed to run it again....
And now I have the right same message than @siouxplice wich is exactly the same we had after the 2.0 update.
I should probably mention like 2 weeks ago it booted once with Webroot installed, then it failed a bunch of times after.
I spent all day trying to replicate what I did to get it to start but I think it was just luck and EAC didnt get flagged when booting that time.
Thanks to share it.
I don't understand one thing:
why were we all able to play the game between the 02 and the 28 October, between the 04 November and the 11 December, and between the 12 and 17 December ?
Who fixed the issue at those times ? EAC ? Webroot ? EA ?
Or were we just all lucky ?
So, I was wrong and @siouxplice is right: it's a Webroot issue. Thanks to you guy !! 😉
(or it is well an EA issue, but bypassed by Webroot; perhaps we will never don't know...)
As suggested by @siouxplice I have open a ticket on the Webroot website last week-end. In this one I have given the link to the first message of this topic -- where are listed all the other topics about this issue -- hoping that will show them that we are numberous to have it.
So they sent me an app for generate a zip file with some datas inside, and after they receve it, we scheduled a phone meeting with a technician for to night (to night for me; it was morning for him).
The technician done (only) one thing: uninstalled my version of Webroot and install a new updated one.
... and the game works now.
So I can just invited you all to (re)contact Webroot explaining them you have this same issue. I wish they will fixed it for you too 🙂
@N16H7-W1N6 I haven't had the same luck, 2 representatives both told me it'll be fixed in future update. Big issue is wsalog fails to upload my log due to firewall even though I disabled Webroot and defender.
What is weird is that a firewall is still active when Webroot and Defender are disabled.
But I think you can disable this manualy in some options ?
See follow up post... The below was not a permanent fix.....
---------------------------
To copy my steps, make sure you know where your webroot key is. They should have sent it to you in an email.
I uninstalled webroot. (It said I had to be an admin. I was the admin but I guess it shows that warning no matter what because once I clicked OK it allowed me to uninstall)
Then I downloaded webroot again and reinstalled it. Then I launched Squadrons. Took forever to come up, but it did.
Even though webroot is suppose to update automatically, it appears it didn't update fully.
I take it all back. ☹️
The next time I launched the game, I got the error again. Apparently, the brief window of it bein uninstalled bought me a one time launch.
I will say that uninstalling and reinstalling webroot is fairly quick, but what a pain in the *. This game is determined to make me miserable.
