WSL: Windows BSOD / hangs on boot when using WSL2

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)

About this issue

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

Most upvoted comments

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)

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.

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

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.

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!

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.

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.