WSL: KB4566782 (OS Build 19041.450) breaks WSL 2

Environment

Windows build number: 10.0.19041.0 Microsoft Windows NT 10.0.19041.0
Your Distribution version: Ubuntu 18.04 LTS
Whether the issue is on WSL 2 and/or WSL 1: WSL 2

Steps to reproduce

Update the Windows. Especially for me KB4566782. After that, WSL 2 stops working.

Expected behavior

WSL2 related services to work normally.

Actual behavior

Docker with WSL2 backend crashes. Linux installations with WSL 2 stops working.

How this bug occurred me

I use Ubuntu 20.04 WSL2 and Docker WSL2 backend. An automatic update was applied on 2020-08-14. The update is August 11, 2020—KB4566782 (OS Build 19041.450). After that Docker started to crash always. Then I tried Windows Terminal. It also started to crash (Coz it’s using Ubuntu 20.04 WSL2 by default)

Workaround I found

I had to uninstall both my WSL2 related Docker and Ubuntu. Then I changed WSL to version 1. Then installed Ubuntu 20.04 and Docker. Docker somehow uses WSL2 even I opt-out from that feature when installing. It takes some time for docker to crash. So in between, I accessed the docker-desktop dashboard and disabled the WSL2 feature. Now both are working fine in WSL1.

Conclusion

Anything related to WSL 2 does not work. Linux distros cannot be installed by changing to WSL 2. Trying to install Ubuntu 18.04 LTS on WSL 2 throws

WslRegisterDistribution failed with error: 0x80041002
Error: 0x80041002 (null)
Press any key to continue...

Please fix this

About this issue

  • Original URL
  • State: closed
  • Created 6 years ago
  • Reactions: 8
  • Comments: 31 (2 by maintainers)

Most upvoted comments

Re-enabling VMP and WSL2 WITHOUT Control Center installed seems to have worked. I now have it running with Docker also working correctly. No crashes so far.

Thanks for the hint @nickgreensgithub !

Thanks for sharing this. I am running Thinkpad X390 with Intel processor.

I’ve decided to dig further and play with BIOS setting, found out disabling Enhanced Windows Biometric Security solved the issue! I’ve re-installed Virtual Machine Platform and it’s now working fine.

Those who are on Thinkpad, can try out that.

image

Hansung TFX5470H laptop that uses AMD Ryzen 4800H (that’s OEM version of XMG’s) posted a new BIOS update(1.07) that says “solved problem related to virtualization”, I tested it, and IT FINALLY WORKS!!! I can boot without any BSOD after enabling Virtual Machine Platform and WSL2!!! Thank you for doing a great job, @XMG-gg !

Same problem. My laptop is MECHREVO code01 with Ryzen 4800H. After having updated to OS Build 19041.450, enabling Hyper-v cause BSOD before entering the system, showing SYSTEM THREAD EXCEPTION NOT HANDLED , but no driver issue is found.

This is currently a known issue and it has also been reported to our ODM from various customers in other regions. Although the Bluescreen points at Control Center, the current assumption is that this is a issue unique on Windows v2004 (May 2020 Update). Our ODM is in touch with Microsoft to find a solution.

When Control Center is uninstalled, you still have some access to different performance profiles with the mode switch button, next to the power button. It has 3 stati:

  • Off
  • Half
  • Full

You’ll see some difference in CPU and GPU clock between these modes, although the difference is not as strong as when having Control Center installed. If this is the only way for you to use WSL2 right now, it’s worth a try.

// Tom

I guess the error already exists in OS Build 19041.450 as I did a fresh install today and still the problem of WSL2 not working existed. Then I updated to the latest (OS Build 19041.508) and now it works perfectly. In my previous install, I did not have Virtual Switch ‘WSL’. So I guess this can be the root cause. But there is no way for me to confirm this as I have a fresh windows. The reason I noticed this is, I have a ‘WSL’ virtual switch in the latest build that I have now.

image

A lot of you guys are talking about ControlCenter and about an AMD processor. But it wasn’t my case as I have a Intel. As this issue is solved, I’m closing this. Thank you!

@benhillis any update on this?

Same situation here, after an update this morning I got stuck in a boot loop and had to disable Hyper-v, WSL, and Virtual Machine Platform to get past the windows login screen.

Everytime the error on the bsod mentioned SparkIO.sys.

I can’t get docker working with just Hyper-V anymore like I used to have, it also wants me to enable Virtual Machine Platform which seems to the the cause of the bsod.

My cpu is also an AMD Ryzen 7 4800h, I hope that’s just a conicidence.

Overall I’ve had an exceptionally unproductive Friday.

@nickgreensgithub SparkIO.sys is part of the control center. Reboot in safe mode and delete the control center that your XMG has installed in order to control the light of your keyboard and other display configuration. Please open a ticket too with them. I have one open

I’m having the same issue. I was using WSL2 to support docker and after Windows installed updates KB4569745 and KB4566782 my system entered a boot loop.

The crash was reliable and would trigger a short time after startup, usually before the “Installing Updates” page was done. A couple of times I could log in but the system never lasts more than a minuet after boot.

The BSOD was an un-handled exception in a system thread (SYSTEM THREAD EXCEPTION NOT HANDLED), always occurring in SparkIO.sys. Unfortunately Windows would not write a minidump otherwise I could provide more information.

I couldn’t find any info on SparkIO.sys and notice that without the VMP feature and WSL enabled it is not present on my system, so I assume it must be related to one of these features.

The only way to fix the problem for me was to disable the Virtual Machine Platform feature. Unfortunately, by the time I saw it (Windows rebooted my machine while I was asleep) the boot loop and recovery process had destroyed my OS, forcing me to re-install windows from an install disk (completely clean reinstall).

On the fresh install, fully updated, if I try to enable Virtual Machine Platform the system will begin crashing again until the feature is removed.

My CPU is an AMD Ryzen 7 4800H.

Is your laptop an XMG Core? because I think I’ve just got WSL2 running again on mine, I did a search for SparkIO.sys on my hard drive and found it in 2 locations, one is in system32, but the other is(was) in the Control Center folder for the program that came with the laptop. So I uninstalled Control Center and now everything’s booting again, though I think that will limit my ability to change performance modes in the meantime.

for me after the update wsl command just hangs. Uninstalling the update resolved the issue (but I’d like to keep up to date). I will try reinstalling this afternoon and get you all some more diagnostic info. I had to revert quickly because work to be done 😄

Same problem. My laptop is MECHREVO code01 with Ryzen 4800H. After having updated to OS

Same problem. Mine MECHREVO Jiaolong Series with 4600h. After enabling VMP, I can login, but within seconds I got bsod referring SparkIO.sys

Maybe romoving OEM software like GamingCenterU will work? it has the same file SparkIOsys. I havent tried though. capture

For me uninstalling Control Centre worked, I’ve been using wsl and docker again for over a week now with no crashes. I guess GamingCenterU is just Control Centre with another name.