Windows 10 - ZwiftApp hangs on startup

When I launch Zwift, the process zwiftapp.exe starts, but never appears on the screen. In task manager, I see the process running, but consuming 0% CPU.

It could related, but I recently updated my display drivers to Nvidia’s 431.02 version.

Here is the contents of my latest log file:

[8:27:52] Log Time: 8:27:52 2019-06-21
[8:27:52] Game Version: 1.0.37294
[8:27:52] Config:       Shipping
[8:27:52] Launcher Version : 1.0.44
[8:27:52] Loading WAD file 'assets/global.wad' with file.
[8:27:52] Loading WAD file 'assets/environment/ground/textures.wad' with file.
[8:27:52] Loading WAD file 'assets/UI/WhiteOrangeTheme/WhiteOrangeTheme.wad' with file.
[8:27:52] Loading WAD file 'assets/UI/minimap/minimap.wad' with file.
[8:27:52] Loading WAD file 'assets/UI/WhiteOrangeTheme/Scotty/Scotty.wad' with file.

Mike -

I have the exact same issue. Am working it through with support. Exact same log for me.

@Terence_Hatten1 - Maybe there is something similar about our systems? I am using Dell Laptop (7530) with a Quadro P3200. Did you recently upgrade drivers too?

1 Like

Running an intel NUC i7 with an intel 8559 with a thunderbolt external GPU with a gefore 1070 ti. Running a preview version of windows which might be causing the problem [Windows 10 Home Insider Preview 64-bit (10.0, Build 18922) (18922.rs_prerelease.190614-1427)]. The driver I’m using is recently update though I need to check which version.

Given I’m using beta releases, I thought it was just me. If it were production I imagine it would be a more widespread problem. I’ve attached the final few lines ofmy launcher log as well, interested if yours is failing at the HasExited.

Blockquote[10:20:40 2019-06-21] Patcher: Fetching version attribute from file: “Zwift_ver_cur.xml”
[10:20:40 2019-06-21] Patcher: Local version is “1.0.37294”.
[10:20:40 2019-06-21] Patcher: Server version is “1.0.37294”.
[10:20:40 2019-06-21] Patcher: Local manifest is “Zwift_1.0.37294_f3539c7a_manifest.xml”.
[10:20:40 2019-06-21] Patcher: Server manifest is “Zwift_1.0.37294_f3539c7a_manifest.xml”.
[10:20:40 2019-06-21] Patcher: Server manifest file checksum is “119920398”.
[10:20:40 2019-06-21] Patcher: Server ver_cur checksum is “85068352”.
[10:20:40 2019-06-21] Patcher: Local Launcher version is “0.0.0”.
[10:20:40 2019-06-21] Patcher: Server Launcher version is “0.0.0”.
[10:20:40 2019-06-21] Patcher: Launcher URL for updating self is “www.zwift.com”.
[10:20:40 2019-06-21] Patcher: No update available, deleting temp files…
[10:20:40 2019-06-21] Launcher: Checking Launcher Version.
[10:20:40 2019-06-21] Launcher: Checking for Game Update.
[10:20:40 2019-06-21] Launcher: No Update found.
[10:20:43 2019-06-21] Launcher: ZwiftApp.exe is not running.
[10:20:43 2019-06-21] Launcher: Starting Zwift App.
[10:20:53 2019-06-21] Launcher: ZL has a valid process pointer and the flag HasExited is False.

Blockquote

I’m on fast ring too.

Operating System: Windows 10 Pro for Workstations Insider Preview 64-bit (10.0, Build 18922) (18922.rs_prerelease.190614-1427)

Here is my launcher_log.txt

[16:08:59 2019-06-21] Patcher: No update available, deleting temp files…
[16:08:59 2019-06-21] Launcher: Launcher Update Process Check
[16:08:59 2019-06-21] Launcher: Checking for Game Update Availability
[16:08:59 2019-06-21] Launcher: Game Update Not Found
[16:09:05 2019-06-21] Launcher: ZwiftApp.exe is not running.
[16:09:05 2019-06-21] Launcher: Starting Zwift App.
[16:09:15 2019-06-21] Launcher: ZL has a valid process pointer and the flag HasExited is False.

Interested in seeing what your driver version is. If this was a driver issue, I expect a lot of people would be reporting it. Maybe it’s related to the driver and this build of windows?

@Mike_Swart_W driver version is 435.27.

Give the differences in spec etc, I think it has to do with this version of windows, given that is probably the only thing in common with our systems.

I’m going to try and rollback to a few previous versions (I rolled back one version and it still wasn’t working - I might try rolling back and installing new drivers)

@Terence_Hatten1 Any update on rolling back to a version that might be working?

I’m on Insider build as well. The issue, from what I can tell, is likely changes to audio in the Insider build. Comparing logs from working to non-working, the next step is audio init. I have noticed in the settings app changes to the audio settings, and so suspect something has changed here.

The App crashes when i try to install it in Windows 10. And i am stuck using it for runs on Android but tye data feed is horrible. Many dropped connections and constant disconnects.

1 Like

Same problem here. Windows 10 on the latest Fast Ring Insider build. I tried to back down my Nvidia Drivers to an older version, but still no luck. I have a Dell XPS laptop with the Intel and Nvidia Graphics cards, but forcing it to the Intel Graphics did not work. It stopped working after a recent Windows Update, so that is probably the issue. Stuck running Zwift on my Android Phone which works, but I miss the larger screen.

This is most probably your issue. I don’t think Zwift optimized the software for Beta windows systems. They are probably testing it before it become an official release.
This is why my Zwift PC is on standard Windows.

@Mike_Swart_W @Fred_Sanders @Melvin_Lai @Jessica_Hamilton_BRT

Hi team -

Ran a full fresh install of windows non-insider builder. This required a complete wipe and reinstall. Took about three hours start to finish downloading windows, then updating, then installing all components. You can use this system: https://www.microsoft.com/en-us/software-download/windows10startfresh

Its painful, but without an understanding of the root cause, it didn’t seem like it was going to get fixed (I tried the latest update and it continued to fail).

Its a solution, not a pretty one, but it work.

Thanks for the update! I run the insiders builds because I am also a developer and need to catch issues (like this one!) before our customers do.

My strategy right now is to run zwift in a VM - works well enough.

FYI, fast ring build 18945.1001 now runs zwift again on my system.