Windows BSOD / hangs on boot when using WSL2

[hafkenscheid]

Environment

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

Computer: Lenovo ThinkPad T590

I emailed a minidump

Steps to reproduce

• Install Windows
• Enable virtualization in BIOS
• Install WSL2 following tutorial
• Reboot
• Windows hangs on boot
• Reboot
• Disable virtualization in BIOS
• Continue tutorial: try to install Ubuntu 20.04 from store (does not succeed, because virtualization needs to be enabled)
• Reboot
• Enable virtualization in BIOS
• BSOD on startup
• Disable virtualization in BIOS
• Windows starts normally, but WSL2 cannot be used

Attempts to solve

The issue first occured around the 12th of August after a windows update. I contacted Lenovo an Microsoft support about the issue. Then performed the following steps:

• Reinstalled Windows from disk with files
• Reinstalled Windows from disk without files
• Reinstalled Windows with the download tool
• Replaced motherboard

Expected behavior

Windows should not crash when virtualization is enabled in my BIOS

Actual behavior

Windows hangs on boot (black screen with blue windows logo) or BSOD (System Thread Exception Not Handled + APCI.sys)

[TheSemicolon]

I can confirm that I am having the same issue. I have gone through the above as well (save for replacing the motherboard on my laptop). If it's of any use, I am having this issue on a Lenovo T490

I had been successfully using WSL until the latest round of patches were applied. Unfortunately, I am not sure what those patches are/were since this is a work issued machine. Once those patches went in, I had boot/crash loops. Had the machine re-imaged, applied the 2004 update, and when getting WSL setup, I get the same crash behavior as described above.

[kepalas]

I also have this issue on my Lenovo T490s.
Windows started BSODing after installing KB4566782 update. It works normally for a minute or two and then throws the BSOD message.
The error message is always "System Thread Exception Not Handled + APCI.sys".

It seems that the KB4566782 update + WSL2 causes the issue. If you disable WSL2 (feature named "Virtual Machine Platform"), but leave WSL1 (feature named "Windows Subsystem for Linux"), the BSODs stop happening.

[hafkenscheid]

As I also posted this issue on the Lenovo forums, I would like to let you know a workaround for this:

https://forums.lenovo.com/t5/ThinkPad-T400-T500-and-newer-T-series-Laptops/BSOD-when-using-Windows-Virtualization-Platform-WSL2-on-T590-T490/m-p/5034580

[andrei-kochetygov]

Another possible workaround, that helped me.

Try to find out "UMA Frame buffer size" option in your BIOS. Select "Auto" mode then save changes and reboot. On loading screen you probably will see failure message, that means you just need to enable Hyper-V again and reboot.

[DaniSheng]

In my old TOSHIBA SATELLITE L755D, the same problem. After fresh install Windows 10 build 2004, I did installig WSL2 and after starting the system, I have a BSOD some minutes after starting the Windows.

[ubremer]

I'm also affected. What's needed to RCA this?

[ghen]

Similar issue on HP Spectre x360.
BSOD started after update to Windows 10 Pro x64 version 20H2 (build 19042.685).
Windows crashes into BSOD and laptop refuses to boot. Disabling virtualization unblocks the boot.

NOTE: Windows WSL2 was working fine before the Windows version 20H2 update roll-out.

[DaniSheng]

Similar issue on HP Spectre x360.
BSOD started after update to Windows 10 Pro x64 version 20H2 (build 19042.685).
Windows crashes into BSOD and laptop refuses to boot. Disabling virtualization unblocks the boot.

NOTE: Windows WSL2 was working fine before the Windows version 20H2 update roll-out.

This is aleatory, in my case for example, I solved the problem reinstalling again Windows 10 20H2 without install the WSL or WSL2, because stay somethings in the system that cause BSOD, or crashing system, same after remove WSL*, its a bomb still, very bugs.

[ghen]

This is aleatory, in my case for example, I solved the problem reinstalling again Windows 10 20H2 without install the WSL or WSL2, because stay somethings in the system that cause BSOD, or crashing system, same after remove WSL*, its a bomb still, very bugs.

After 2 days of trials I am now convinced that this is likely not an WSL related issue. Got to BSOD even after I have disabled virtualization in BIOS, though on overall Windows was much more stable without virtualization.

After all, I have cleaned and reinstalled all major drivers:

• Intell WiFi (released 1 Dec 2020; there is a mention for the BSOD fix in release notes) from Intell web site
• Intell Bluetooth (released 1 Dec 2020) from Intell web site
• Grafics Adapter drivers (complete clean-up with the removall tool, then rboot, then install both, Intell and Radeon Vega, drivers) from Intell web site
• Realtek HD Audio from Windows Update

Finally, at the very last moment, Windows itself offered me to install a new update:

• KB4592438

From the press:

With Windows 10 KB4592438 cumulative update, Microsoft has delivered a fix for a highly frustrating ‘Blue Screen of Death’ bug that has been crashing PCs with Intel NVMe SSDs drives since May. Unfortunately, the update comes with multiple issues, according to user reports on the forums.

Ever since everything works just fine.

[apos]

As I also posted this issue on the Lenovo forums, I would like to let you know a workaround for this:

https://forums.lenovo.com/t5/ThinkPad-T400-T500-and-newer-T-series-Laptops/BSOD-when-using-Windows-Virtualization-Platform-WSL2-on-T590-T490/m-p/5034580

Fix, which drove me crazy and made me reinstall the system twice, worked for me on Lenovo T490s (intel grafics) and Windows 20H2 - 19042.685 (Windows Feature Experience Pack 120.2212.551.0) with Windows insider (beta channel).
Thanks

[akwodkiewicz]

For me it turned out that the enabled Enhanced Windows Biometric Security UEFI setting was causing the issue. I turned it off and now I have an updated Win10 with AMD-V (virtualization) enabled and WSL2 working.

(Lenovo T14 with AMD)

[ruffyleaf]

Am facing similar issues. Tried updating to latest patches but to no avail.

Currently have these Hotfixes, but still get the BSOD after I enable Virtual Machines and WSL.

Hotfix(s): 7 Hotfix(s) Installed.
[01]: KB4601554
[02]: KB4562830
[03]: KB4577586
[04]: KB4580325
[05]: KB4589212
[06]: KB5000802
[07]: KB5000858

[DaniSheng]

Just solved with a fresh install, the bug happens still in login screen and I can not reinstalling WSL2 because the error happens again, working normally with WSL. This happens in different computers.

[ruffyleaf]

I did a fresh re-install as well. Can’t get the Virtual Machine Platform working. It’s causing the BSOD. Only working off WSL too.

[adcc97]

I have a problem with WSL2, I'm using WSL2 normally but at the moment of turning off my computer a blue screen appears and I don't find solution it's only when I used WSL.

[DanPinGF]

I suspect incompatible hardware. My assumption, but that may be why you're getting so many of those blue screens/hangs.

[aohan237]

i faced the same issue constantly,but cant know why.
so i unistall wsl and disable all hyper v features.

then everything goes smoothly.

so just use linux

[eqn-group]

I also got BSOD yesterday while using WSL, while closing it.
RNDISMP6.SYS
@therealkenc

[hjuivc]

For me it turned out that the enabled Enhanced Windows Biometric Security UEFI setting was causing the issue. I turned it off and now I have an updated Win10 with AMD-V (virtualization) enabled and WSL2 working.

This worked for me with Lenovo T490! Thanks.

[siavee]

For me it turned out that the enabled Enhanced Windows Biometric Security UEFI setting was causing the issue. I turned it off and now I have an updated Win10 with AMD-V (virtualization) enabled and WSL2 working.

(Lenovo T14 with AMD)

This also worked for me on a ThinkPad P53. Thanks!

[DanPinGF]

Is the BSoD still occurring when trying to use WSL2? Also did you check for any updates/hotfixes?

[Agazoth]

For me it turned out that the enabled Enhanced Windows Biometric Security UEFI setting was causing the issue. I turned it off and now I have an updated Win10 with AMD-V (virtualization) enabled and WSL2 working.

(Lenovo T14 with AMD)

Worked for me on Lenovo P15s.

[drwetter]

Same here. I just went through a lengthy, annoying restore procedure with my limited windows emergency boot knowledge. Costed my full three working days to de-bitlock the partition, reinstall windows, install all updates, install programs. In safe mode there wasn't even a hint in the eventmgr.

Fortunately I managed to create a restore point before installing WSL again.

This sucks big time. Just the BSOD with "SYSTEM_THREAD_EXCEPTION_NOT_HANDLED" over and over. Additionally it's a pain in the *** if you also have Bitlocker enabled. The wort thing to me was there wasn't even a hint what's wrong.

System is a factory installed Lenovo P1 Gen4 w Intel graphics only. Patches are recent.

[artyom-boyarov]

I am encountering the same issue on an HP Pavilion, with a ryzen 5 and radeon graphics. The only solution that works for me is simply doing a reset after the laptop crashes.

[nand]

I am facing the same problem.

In my case, there was no problem when I was using Windows 10, and it started occurring after upgrading to Windows 11 and reinstalling Ubuntu.

I am using Ryzen 3950 CPU and I upgraded B550 ChipSet Driver to the latest version at the same time I upgraded to Windows 11.

I am not sure if the problem is caused by updating to Windows 11 or by upgrading the ChipSet Driver, but I will report the situation.

[ogeeDeveloper]

I got this issue as well, but I found out the cause was an incompatible driver which was my network driver.

[TacticsJan]

I am facing the same issue except my BSOD shows: INACCESSIBLE_BOOT_DEVICE
I have tracked it down to the combination of vt-d and Virtual Machine Platform/Hypervisor Platform

[Timibreez]

I can confirm that I am having the same issue. I have gone through the above as well (save for replacing the motherboard on my laptop). If it's of any use, I am having this issue on a Lenovo T490

I had been successfully using WSL until the latest round of patches were applied. Unfortunately, I am not sure what those patches are/were since this is a work issued machine. Once those patches went in, I had boot/crash loops. Had the machine re-imaged, applied the 2004 update, and when getting WSL setup, I get the same crash behavior as described above.

I have the exact same issue with my Lenovo T490. It is disheartening.

[michaelbrylevskii]

Disabling VT-d in BIOS helped me. MSI Creator Z17

[Timibreez]

Disabling VT-d in BIOS helped me. MSI Creator Z17

I also found a fix that worked. On Lenovo T490, if I disable VT-d, it doesnt still work, so I disabled the advance biometric security directly under the virtualization technology setting in bios, and that fixed it for me.

WSL and Hyper V work fine now.

[microsoft-github-policy-service]

This issue has been automatically closed since it has not had any activity for the past year. If you're still experiencing this issue please re-file this as a new issue or feature request.

Thank you!