Workaround for Windows 10 System Freeze [February 2026]

I downloaded and ran the file. Unfortunately the Zwift icon does not show up in the System tray,so I have no way to select “Debug → Windows KB Workaround”. This in on Windows 10 with extended support, NVidia 750Ti graphics card. What now???

I’m still encountering freezing with Windows 11 25H2 and a GTX 660. I worked around the problem for the last 3 months by switching video cards to a RTX 4060 but this was not sustainable and I needed to switch back. I thought from the forums that it was fixed, but obviously the problem still impacts Windows 11 as well as Windows 10. I’ll try the above Zwift update.

The v1.1.15 worked for me and is the first time I’ve successfully loaded Zwift with the GTX 660 in 2026. If I turn off the “Windows KB Workaround” mode it goes back to crashing again, sometimes before the login screen sometimes after, but always before loading a ride.

Zwift keeps freezing since a month ago Feb 2026. Using surface tablet Win10.

I have tried reducing graphics etc.

Can’t see the debug option in the icon.

May move to Rouvy as repeated crashes are very frustrating.

If that’s an ancient laptop with a 6th generation CPU (or anything with HD5xx series graphics adapter) then you need to head over to this topic and update your video driver: Windows 10 freeze on Surface Pro 4/Intel integrated GPU [February 2026] - #37

If it’s some other generation, let me know which CPU it has.

I didn’t realise it was ancient but it may be that it suddenly can’t cope with the upgrades .

The cpu is core i5 2.50 GHz

Graphics 128MB

That doesn’t clarify the generation of the CPU or which graphics adapter is in it. If you open the System Information app in Windows, it will give you those details. If the CPU is something like “Core i5‑6300U” (note the 6 at the start of the model number) that would be a 6th generation CPU that needs the driver I linked to. The graphics adapter would look something like “HD5xx”. If it’s something else then you would not use that driver.

ok, second time I ran Zwift 1.1.15 (still with the Windows KB Workaround enabled) it froze while trying to launch a ride. This is getting incredibly frustrating.

Try opening task manager and shutting down all other apps. I also shut down background processes for apps that i run such as browsers, whatsapp, phone link. That worked for me. Another trick is to go into details in the task manager and increasing the priority of the task.

Hi Paul. While I have found various workaround to get zwift to run without crashing i’ve noticed that after i exit zwift it shuts down my nvidia gpu. it no longer appears in the performance tab of the task manager. one of the things i did was to force zwift to use the nvidia gpu instead of the native intel gpu. i noticed that occasionally zwift would only use the intel which would always result in a graphic freeze up.

I think you mentioned you have the Intel HD520 integrated graphics (as well as the Nvidia GPU) which means your machine is affected by two different issues. The issue of game freezes when on the Intel HD520 is usually fixed by installing the driver update discussed in this topic: Windows 10 freeze on Surface Pro 4/Intel integrated GPU [February 2026] - #4 by Paul_Southworth

Note you will probably need to fetch the zip file version of the driver.

It is probably possible to disable the integrated GPU in the system BIOS if you want to try that as well. I don’t have one of those laptops to check, but it’s usually an option.

I was able to change a setting which forces zwift to use the nvidia gpu. so, with a bit of manipulation i can get zwift to run (most of the times) in a lower res setting. do you have insight into when this will be resolved (either on zwift side or microsoft side)?

No I haven’t heard any timeline on a fix from either side.

With todays Win 10 update KB5078885 Windows 10 ESU Update build 19045.7058 (22H2) - March 10 -

I see this-

[Graphics] Improved: A stability issue affecting certain GPU configurations.

2 Likes

Just tried this latest update briefly with the -Debug-Windows KB Workaround unticked using a GTX970 and it seems fixed

3 Likes

I just did the update. No joy. Tried it twice after going through instructions twice. 1 minute in on the first try, 2 minutes on the second.

I had success as well. I installed the March 10th Windows 10 ESU update, rebooted my PC. I then started Zwift and then went to the Z icon in the Windows System Tray, clicked Debug and unticked Windows KB Workaround. I then crossed my fingers and clicked “Let’s Go” in Zwift and it ran properly. I am using an Nvidia GeForce 750 Ti graphics card in my Windows 10 PC with Extended Support License.

1 Like

The Windows 10 update KB5078885 finally fixed the problem, and Zwift is running smoothly again. I’m using an Nvidia GeForce GTX 790 :+1:. I am not using the special version of the Zwift Launcher.

Ok, 1.1.15 has definitely helped but it’s definitely still crashing semi-regularly. Paying a lot for a service that doesn’t work reliably tbh.

My rig: Windows 11 Pro, 25H2, GeForce GTX 970.

My history: Have been uninstalling updates since KB5074109 - 26200.7623 the original update which broke everything. I’ve been postponing updates since then in order to still run Zwift, trying every week or two to check the latest Windows updates and having to constantly uninstall since none of them worked (Zwift still freezing upon launch).

Today (3/14/26): Just installed 2026-03 Security Update (KB5079473) (26200.8037). Zwift still would not launch, froze on the opening screen and required a hard reset like the same as when I originally installed KB5074109 - 26200.7623 and every subsequent update. Found this thread, and tried the new 1.1.15 launcher, I’m able to load Zwift successfully running the latest Windows updates! Thank you for at least providing this option.

Note: I did try to run Zwift with the “Windows KB Workaround” option deselected and it still freezes. Wanted to try that since someone above reported they could Zwift without this option selected – but that didn’t work for me, I still have to have it selected.