I am running Zwift on PC (Windows) on a decently powerful PC (e.g. can play a number of fairly demanding FPS games) and was in the middle of a training session when my trainer (Wahoo Kickr Core) cut out. I ended the workout as it said ‘connection lost / failed’ and from then on I am unable to launch Zwift. The game boots up but gets stuck and freezes during the load-up blue screen where the white ‘Z’ logo starts shrinking and then freezes and starts very slowly (over a matter of minutes) reducing in size until it gets to the main screen. At this point, nothing is usable and it just crashes if you click anything. I have tried:
Rebooting PC multiple times.
Uninstalling Zwift and reinstalling it (multiple times).
Deleting cache and all history from Microsoft Edge which is apparently used to launch the game.
Updated all my graphics drivers (AMD) to the latest.
Disabled Windows Defender for Zwift.
Uninstalled firewall software to stop blocking Zwift.
Deleted all local files from My Documents within Zwift folder.
Opened Zwift as administrator.
At a loss as to what to do… see logs below for more info.
Honestly, for some reason, after the 20th+ restart and after 5 odd days it just started working of its own accord. Zwift official support is beyond useless and a complete joke. Even here, I had no real help.
I had a lot better luck on r/zwift on Reddit for some meaningful suggestions and I had a guy reached out to me who was WAY more helpful than Zwift’s support. His Reddit name is: johnm_z
I would suggest DMing him as he took a look at my logs for me and gave some good guidance. I shared a session ID with him for a most recent crash and he looked at the files and said the following:
"We noticed a couple of things, there’s a lot of network errors in the log which indicate it’s having a hard time reaching our servers. Any chance this is a work computer, or has a VPN setup?
Also noticed that OneDrive is syncing the my documents folder, which could cause issues with Zwift as it used that folder. Disabling to check if that solves it could help troubleshoot."
However, before I could implement anything further, I thought I would just check another time at random and it started working again of its own accord. No idea why.