Since a couple of days I cannot startup Zwift launcher anymore.
When opening the application (also admin) it gives me an instant blank screen with my mouse icon ‘loading’. After a couple of seconds the screen disapears, without any error messages.
System: Windows 10
App version: Most recent from site = 1.1.5
(GPU) drivers: NVIDIA 1060 - Up to date
Windows: Up to date
Firewall: makes no difference when turned off/on
Connection: Ethernet directly to router
What I tried:
Checked all above;
Delete Zwift + program files and reinstall it;
Delete all browser cookies, history and stuff;
Removed the latest windows updates that I installed in the last days;
Reinstalled these updates afterwards because it had no effect on the crash.
Anyone has a clue what it can be, or how to fix this?
I’ve seen a few of these types of situations over the years with Zwift, and in my experience, it’s usually one of two things. It’s likely either an issue with the WebView2 installation, or a graphics issue. Understanding this is a stab in the dark kind of situation, and an educated guess, since you’ve recently had a Windows update, I’m leaning a bit more towards Webview2 being the issue.
If you want to take the shot in the dark method, you can run a DISM and SFC scan on your computer, which should detect and repair any corrupted or broken windows files. It may seem a little intimidating at first, but the process is reasonably straight forward.
1.Select the start menu
2. Search for "command prompt
3. Right click command prompt and select “run as admin”
4. if the User Account Control (UAC) prompt shows up, click “Yes.”
5. In the command prompt window, type SFC /scannow and press Enter
6. System file checker utility checks the integrity of Windows system files and repairs them if required.
7. After the process is complete, reboot the computer.
Once the computer has restarted, you can perform the same steps, but instead of typing “SFC /scannow” type “DISM /Online /Cleanup-Image /RestoreHealth”
The combination of the two should fix any potentially corrupted or broken files in windows.
If you are still having issues after running those commands, we will need a copy of your windows crash logs to determine what is ocurring.