I tried a reboot and still get the error.
Do you still have Webroot installed?
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.
