yes, sorry I hadn’t realised this thread was about the laucher update! my bad.
but the game update usually waits for me to launch the game then says zwift needs to apply an update and then I get the windows pop up. this time the windows pop up was there as soon as i logged into windows without me having to launch the game.
Not sure what’s changed but my setup frequently seems to fail to load the launcher these days. I have the shortcut in shell:startup and the window comes up then disappears. The launcher log file shows nothing after a second instance of the line ‘Starting WebView2 Initialization’, as though it’s trying to do something twice and crashing trying to do so.
It looks like the launcher opens the main window, then believes it can’t, so closes.
Hmm, seems to work properly (as I want) with Auto Startup enabled. I always used to disable that because it would occasionally load two instances of the game in the system tray.
Can’t remember if there’s a more recent thread than this about the launcher, but in recent months the game updates seem to take longer than anticipated and it appears to be caused by Microsoft Defender.
Once the new files are downloaded, the launcher log file shows that moving them into place takes a matter of seconds. The launcher progress bar then seems to hang on the ‘Verifying files’ message for a disproportionate amount of time, and Defender can be seen in Task Manager using a lot of CPU resource and disk activity. It’s as though it’s doing a scan on every individual file. The launcher log shows this as iterating the manifest.xml file. I can imagine this being problematic on slow machines, particularly those with mechanical hard drives. It may look like the update has frozen. When a game update includes a large amount of changes, the issue worsens.
We’re only talking a minute or so, but it seems slower than it could be. Is this expected behaviour?
There seem to be some issues with Windows Defender on Intel CPUs. Google “Windows Defender can Significantly Impact Intel CPU Performance, We have the Fix”. There is a tool called ThrottleStop that claims to solve it. Maybe worth a try.