I’ve suddenly started receiving the following script error on startup of the launcher. I’ve restarted my PC, reinstalled Zwift, and cleared my internet caches, all with no success…I ran Zwift yesterday with no problems, and there has been no change to my pc (that I’m aware of).
I have the same issues. Yesterday everthing was fine but today I get script failure messages. Tried the same things you did and send a email to the Zwift support (no reply yet…)
Did you find a solution?
Update:
I found a solution in earlier posts… Creating another account in Windows and start Zwift from there works for me. Still looking for a proper solution because this is a lame work-around
Well after trying all sorts from messing with IE 11, forcing windows to upgrade to version 1809, reinstalling zwift, the only way it’ll work is by creating a new user on the same pc, and running it from that account. Weird…
Same issue here, Windows 10, Zwift worked fine until two days ago, now I can’t launch it.
I tried everything mentioned in this thread plus the one linked in the first post, only thing that worked was logging into Windows with a different user.
Hope someone at Zwift is looking into this so it can be fixed properly.
My point is that I had a working set-up in Windows10 and Chrome. From one day to the next I could not login anymore. Meanwhile I made another account (on the same laptop) and everything works fine…
I think (being on the same laptop) the software zwift calls upon is the same. So it still puzzles me why on my original account it stopped working and everything is smooth when I login in as another user…
My Internet Explorer is already the latest version, so is Edge. Windows is set to English as it has been since day one.
Something with the security settings and/or Java Script must have changed with a recent Windows 10 update, as all of us with this issue got it at the same time. Something about our default Windows profile no longer lets us access the Zwift servers, but a new profile works. Very odd, and annoying.
I sent an email to support a few days back, including all my log files and I’ve not had any response back since then.
Because the workaround you describe requires a different user, it sounds like something in the specific user settings at the OS level is getting mucked up and preventing Zwift from executing it’s login scripts correctly.
What that could be, or how to potentially fix that is beyond me though.
Sounds like javascript caching issues… after the miserable move from the earlier support platform which rendered all google search results invalid, you would think Zwift needs to hire some competent web developers…