WSL: Can't boot after WSL 2 Install

Happy to provide any additional details to troubleshoot but I’m not sure what else to provide at this point in time. I’ve painstakingly tracked this can’t boot issue down to WSL 2 install (6 PM an on in blog post).

About this issue

  • Original URL
  • State: open
  • Created 7 years ago
  • Reactions: 34
  • Comments: 329 (22 by maintainers)

Most upvoted comments

Same issue here on an HP omen with the Ryzen 5 4600H. Windows will boot with either Virtual Machine Platform or virtualization in bios enabled, but having both on causes a blue screen. Unfortunately I can’t change the UMA buffer size since HP doesn’t provide that option in the bios.

I solved the issue in my new HP omen Ryzen 7 4800H. Steps:

  1. I reinstalled the driver for AMD Radeon (Integrated Graphics) using the auto detect tool. Instructions are provided here https://www.amd.com/en/support/kb/faq/gpu-131. Also when installing check the option to completely remove the previously installed driver. This step will perform 2 reboots.
  2. Go to add and remove programs and remove AMD Ryzen Master SDK.
  3. Reboot

@hanhwi @kyeongsoo I had the same issue with my AMD ryzen APU laptop (Thinkpad T495) but solved by changing “UMA Frame buffer size” value to “1G” or “2G” in BIOS.

Same issue, I enabled the 2 windows features separately tho.

First windows subsystem for linux, which reboot normally, but then enabling windows virtualmachineplatform caused the system to fail at boot.

More specifically, the bootloader does seem to load Windows but just stalls at black screen until forced shutdown.

I have a ThinkPad with Windows 22H2. Installing WSL 2 prevented my computer from booting up; I got the blue screen of death.

I was able to fix it by booting into the bios (press enter during boot) and disabling “Kernal DMA Protection” under Security/Virtualization. See screenshot.

20230421_083953

This ticket really should be fixed because bricking a computer after installing WSL is obviously terrible.

Jumping in for a quick update: We’ve identified that these failures are not from the WSL code paths. I’m working with partner teams here to get the next steps for a solution. This bug is proving tricky to find the root cause, but I can assure you we’re looking into it! I’ll keep staying active on this thread with any updates, thank you all for your patience.

Thank you for the nudge @spottedmahn !

We’re still investigating this internally, I don’t yet have any major updates here but I’ll sync with the relevant teams and see if I can get something more fine grained.

I also have a Dell XPS 15 7590 (i7-9750H CPU) and experienced the INACCESSIBLE_BOOT_DEVICE after installing wsl2. Like @JasonBSteele I was able to fix it by disabling “VT for Direct I/O” in the BIOS. This is with released Win11 22H2 (build 22621.900) and the latest Dell BIOS (1.19.0, 9/14/2022)

I was having issues and had to reset my laptop HOWEVER this done it for me:

https://ubuntu.com/tutorials/install-ubuntu-on-wsl2-on-windows-11-with-gui-support#1-overview

You’ll have to turn a few windows features on - several times in my case so if you keep getting errors after restart just make sure they are activated. The ones you need to activate are:

  • Virtual Machine Platform
  • Windows Hypervisor Platform
  • Windows Subsystem for Linux

Hopefully this helps! If you do get errors in the Ubuntu download, check for the error code in the troubleshoot section of the WSL documentation:

https://docs.microsoft.com/en-us/windows/wsl/troubleshooting

Hope this helps!

@craigloewen-msft I’m sorry, but that response is at the entirely infuriating level of what the hell?

Several years ago, in a developer release, Windows went from working perfectly with this brand new WSL2 to all of the sudden not working. When it happened, I and several others put in feedback on the Feedback Hub. Exactly how many responses have we gotten to those initial reports over the years? You guessed it, zero!

Then, not only did the next dev release not fix it, Microsoft went on to eventually cut a GA release of Windows that still had the broken change in it. So, we all came to GitHub to try to get attention. Here we are several years later and a couple of GA releases of Windows later and MS says, “we didn’t do it! It’s your drivers that were working fine before we supposedly didn’t do it”.

“Update your drivers!” as if we haven’t been doing that for years and tilting at windmills to try to get someone at MS to just reach out to major manufacturers of hardware we are unfortunate enough to have bought because we can’t. Hell, we’ve asked, begged, pleaded with you to just buy a device we pointed out we know to no longer work to figure out what was changed that caused this breakage to then be able to guide the manufacturers on how to fix it.

Instead, we get “update your drivers”! pffft. Like we have control over what the manufacturers release. Of-freaking-course we have been doing this for YEARS now.

Hi @genio and everyone else on the thread! My apologies on the delay answering. We’re investigating this issue and trying to determine the root cause. This is definitely an issue that we take seriously as we do not wish to break any users. I’ll take ownership on failing to communicate that we’ve seen this issue and are working on it earlier. We’re grateful to have a positive community that helps identify any bugs, and our goal is to keep you all informed which we’ll aim to do earlier in the future. Thank you for pinging us on this!

Same issue here on an HP omen with the Ryzen 5 4600H. Windows will boot with either Virtual Machine Platform or virtualization in bios enabled, but having both on causes a blue screen. Unfortunately I can’t change the UMA buffer size since HP doesn’t provide that option in the bios.

I have an ASUS FX505DV and am running Windows 11. On the advice of this Reddit thread, I set SVM Mode to “Enabled” and UMA Frame buffer Size to “Auto.” This completely resolved the issue for me.

ASUS TUF FX505DT user here. You saved me! As many people have commented, no Hyper-V necessary for my case. wsl --install along with enabling virtual machine platform and windows subsystem for Linux features, all in one go, then stuck in black screen after vendor logo. After setting the UMA frame size to auto, Windows finally booted.

I have an ASUS FX505DV and am running Windows 11. On the advice of this Reddit thread, I set SVM Mode to “Enabled” and UMA Frame buffer Size to “Auto.” This completely resolved the issue for me.

Once you allow Virtual Machine Platform, boot fails and you end up having to boot in safe mode and set hypervisorlaunchtype off in ‘bcdedit’. It’s not an issue with the bios nor hardware. Attempted on both Windows 10 Pro and Win10 Home on 2 desktops both build 19041…

I’ve found something odd after a week of attempts. Let the boot fail 3 times, go into Troubleshoot, then choose to “Debugging Mode” under Advanced Startup Options. After this, it for some reason just finished the install of Hyper-V, Hypervisor, and Virtual Machine Platform. I can now run WSL2 etc but I guess it’s at the expense of some of my drivers not running? The quest for a proper solution continues…

Turns out having ESEA Client for csgo installed on my computer broke Hyper-V/VirtualMachinePlatform/Hypervisor etc…

If a lot of people report a problem they do get looked at.

Everyone, please upvote the Windows Feedback Hub Problem Report so this gets addressed, thanks!

Upvote == Add similar feedback in app

image

I have a Dell XPS 15 and am running Win 11 in the Insiders Program, build 22623.1020.

Whenever I enabled Virtual Machine Platform in the Windows Features I got INACCESSIBLE_BOOT_DEVICE GSOD after the boot.

I took the advice above and disabled VT Direct I/O in UEFI, and now applying the Feature has worked fine. As did running WSL and installing Ubuntu.

DELL XPS 15 7590

EDIT: After disabling VT for I/O boots again

Same issue INACCESSIBLE_BOOT_DEVICES after WSL install. It was a fresh install with only vscode and wsl2 on top of it

I have used without any problem wsl2 so far, for some months now, so I can’t explain why now is not working, I just wanted to point out that the hardware theory looks unfeasible to me

These steps works for me:

  • Open PowerShell as Administrator.
  • To install WSL, run this command: dism.exe /online /enable-feature /featurename:Microsoft-Windows-Subsystem-Linux /all /norestart.
  • Enable the Virtual Machine Platform optional feature by running the following command: dism.exe /online /enable-feature /featurename:VirtualMachinePlatform /all /norestart
  • Restart Windows 10.
  • Download the latest Linux kernel update package and install it: WSL2 Linux kernel update package for x64 machines
  • Set WSL 2 as your default version. Open PowerShell as Administrator and run: wsl --set-default-version 2.
  • You can now install WSL 2 distros from the Microsoft Store (see the note).

Reference: https://winaero.com/update-from-wsl-to-wsl-2-in-windows-10/

I’ve come across this problem today with my ThinkPad P1 G3: i7-10750H, Quadro T2000 Max-Q, BIOS ver. 1.19, VT-x and VT-d enabled, drivers come from Lenovo website and fully upgraded.

The system worked before with a Windows 10 21H1 (probably since I’ve forgotten what I’ve got before, but I did know that one had some kind of virtualisation software installed) setup with WSL 2, but now it won’t work with my current 21H2 update. Have used Kaspersky and VirtualBox before, uninstalling won’t help

Tried possible solutions as follows:

  • sfc /scannow
  • dism repairs
  • repair install of Windows 10
  • UEFI setting reset

All solutions won’t work, and the symptom is a bootloop and startup repair after three reboots when trying to enable Hyper-V or Virtual Machine Platform (which some say are the same thing). Going to the safe mode gives “We couldn’t complete the features” warning and reboots to the normal mode system, gives the same message, and boots successfully into the system.

===================== Updates on the Issue ======================== I have since then did a little experiment with my UEFI setup after the post, and here are the configs there:

  • Kernel DMA Protection
  • Intel VT-x
  • Intel VT-d
  • Enhanced Fingerprint Security (Windows 10 2004 and before not supported)

What I have tried:

  • Go to the UEFI and turn Kernel DMA Protection off, then turn VT-d off
  • Install Virtual Machine Platform and reboots
  • The system went on flawlessly
  • Go back to UEFI, turn VT-d on, and reboot
  • It still booted flawlessly, so reboot to UEFI and turn Kernel DMA Protection on
  • Reboots and still boots like a charm So I suppose there should be something wrong with that “Enhanced Security” thing, but I don’t know who has the fault, since Lenovo claimed in the BIOS it should work with 21H1 and newer. I do hope anyone who is responsible of that can fix the issue.

@ultraalkaline there’s no need for that 😉 Most of the time it’s a hardware problem. Not much Microsoft can do about that than suggest upgrading your hardware. Besides just because something is new doesn’t mean it’s good enough to handle WSL2. I suspect old BIOS, old or integrated graphics (common in laptops) are the cause of these problems…

Microsoft is aware.

As to whether this sits at the top of their development “Backlog” is the question. What’s remarkable is this isn’t some minor cosmetic glitch, it actually prevents the OS from booting, yet still, no answers from either the manufacturers or Microsoft!

Jumping off the venting bandwagon as that is not helping either. I wish I could offer some advice, but I’ve tried everything, as did many others here, after countless hours of frustration. Hopefully we’ll get some answers at some point, but not holding my breath.

And thanks @ilyassezah, but that doesn’t appear to be an option either on the Dell XPS 15 9575 2-in-1; seems to just ignore whatever I enter in the reserved memory text box, or default to some other value (at least on Windows 11).

With hundreds of people reporting this problem I almost feel like we should send a laptop to Microsoft for them to be able to replicate the issue (I’m willing to pitch $5). It’s kind of ridiculous, it’s a constant problem on specific hardware, Microsoft should be able to replicate the problem without begging us for kernel crash reports.

Hey Microsoft, please spend $700 on a laptop and try this issue yourselves: http://amazon.com/HP-17-3-Premium-Laptop-Bluetooth/dp/B08RCTFS6V

Again, disabling the Realtek ethernet driver solved the problem, but that’s not a “solution” for everybody and this needs to be fixed either by Microsoft, BIOS makers (no, I don’t have any of the options listed here), and driver makers. Even if this is not Microsoft’s problem, somebody should take charge of the problem, it’s ridiculous to expect customers to be passed around between Microsoft, HP (or Dell), Realtek support, each of the providing little help because they either don’t have the knowledge, don’t care about WSL, or they consider a problem of the other vendors. So, who should take charge if not Microsoft?

@Tigls Did you already find a solution?

I have the same issue with my ASUS-VivoBook-S15-M533IA Ryzen 4700u. Virtual Machine Platform feature was working fine on Windows 10 1909 until I decided to update first to 2004 and 20H2 in October. I have the BSOD error since then and the only way to boot the machine is to turn off SVM(AMD virtualization) in BIOS.

@Cryptokkie There is no real solution at the moment. Currently, I had to completely reinstall Windows to the 1909 version with which the virtualization works. Before I had a dual boot with Ubuntu and Windows 20H2, because under Linux the virtualization works fine, but the laptop doesn’t work well with Linux in terms of hardware (Bluetooth problems, not working sleep mode, etc.) so I am tied to Windows. Then at some point under the dual boot, I couldn’t boot into Windows anymore and I had to install Windows 1909, which I mentioned in the first sentence.

I am also in communication with Asus Support regarding this issue. I sent them the steps to reproduce. They asked to record a video, which I also did (https://www.youtube.com/watch?v=ij9u2q1K-lI&t=2s), and now they keep asking me related and unrelated questions. I hope they realize that this problem exists and that they will fix this with a bios update, there is nothing else left for us.

Please leave this issue open as we still see others with the same problem, I’ll close the issue in the future once it seems generally resolved 😃.

Update: ASRock tech support gave me a link to a private BIOS update and it fixed the issue for me.

Before I got this fix, me and others at Microsoft debugged into the kernel to see if we could figure out what was going wrong. Unfortunately we couldn’t find anything suspicious on the windows side, it would just reboot when initializing the hypervisor. The kernel debugger would not see any errors, the machine would just reboot. So whatever went wrong is outside the control of even the OS kernel. It was also failing too early in the boot process to generate a crash dump even if the kernel could see the error.

There is indeed lots of confusion going on around drivers, yet that doesn’t seem to be it; maybe just not the whole of it.

In my case, the machine was performing as expected on WSL2 with a developer preview install. Then when the next developer release came along, the boot issue came up. At that point, nothing had changed but the next developer release of the OS.

Not yet knowing what caused my problems, I opted to install fresh from the Windows media I had at the time. The machine functioned as expected yet again. I again upgraded the OS using the developer release to see if things would behave without any software other than the OS and it again failed. Also of note is that when running Windows 10 from that release forward, rebooting was broken in Windows. When rebooting in Windows, the machine just shuts down; it doesn’t do an actual reboot. Rebooting in Linux still behaves as an actual reboot.

Every single OS release since that point has had the reboot problem as well as the inability to turn on virtualization in the BIOS.

Some using AMD Ryzen have posted some things to try or changes in BIOS to make to get things rolling again. I am, however, on Intel and cannot change anything in BIOS that makes any difference with the issue. I have looked into every driver change suggested as well and there are no changes to make that make any difference on my hardware.

The problem is therefore on both AMD and Intel and can clearly be pointed back to the dev releases that happened and could be regression tested against those releases should Microsoft just get a machine that exhibits the behavior. That would provide them the best way to know what changes that were made have caused the problem and see if it’s fixable. It’s fairly frustrating to have to keep on and on about this.

We might want to hold this open until we get an actual release that fixes the problem (not just a beta). Since this is the ONLY place we have been able to get through to them it wouldn’t make since to cut off that communication line before we’re sure we are good.

“Virtual Machine Platform” is the only component required for WSL2. The various Hyper-V features include subsets or supersets of the required functionality.

I’ve been able to use Windows Restore Points to fix not being able to boot so I’m happy to run the WSL 2 install again and collect the necessary info (though I can’t boot into windows so how does one do that? 🤔).

It works, thank you. After I disable VT for Direct I/O in BIOS, my device boot successfully.

My Systemspecs: CPU: Intel 9750H OS: Win11 22H2 22621.521

I’m also on a Samsung Galaxy Book and that method I mentioned worked for me

I’m keeping an eye on this thread and trying to run down this error internally. It certainly has affected many devices over a long period of time, and we’re trying to get a repro of this internally so that we can identify a fix. Thank you all for posting your specs and devices!

Hello, I am using the hp pro book x360 11 G1 EE, I have the same problem as you by installing wsl and rebooting, no problem but by activating the “virtual machine platform” the computer launches the automatic repair and I am forced to reboot in safe mode to remove the option. Would you have a solution for me? Thank you in advance.

Unfortunately, there is no fix. Microsoft and the machine manufacturers continue to ignore us and play the blame game; we’re just the unfortunate ones who paid for their stuff with zero opportunity for communication with either entities in order to get help. They’d rather force us to purchase their own hardware through sheer frustration rather than actually look into the problem.

Experiencing the same issue since upgrading to Windows 10 in April 2020. I posted my feedback in the hub with a kernel dump. https://aka.ms/AAawyxm

IT IS WORKING!! OH MY GOD IT IS!!

EVERYBODY, GO TO SETTINGS AND INSTALL ALL OPTIONAL UPDATES IT FIXES THE PROBLEM ON 20H2

@shrvtv As per the instructions in this repo’s readme and in the contributing guidelines:

Please direct all Windows crashes and security issues to secure@microsoft.com

Hi @shrvtv 👋

I’ve collected a dump for you, but Github doesn’t let me upload it

per Craig’s comment here, you’ll want to attach the dump via a Feedback hub issue

and thanks for collecting the dump file! 🤝

Just jumping in here quickly in case some of the WSL team are on Thanksgiving vacation:

⚠ As per the opening paragraph in this repo’s README, please DO NOT ATTACH DUMPS OR TRACES TO GITHUB ISSUES:

Reporting of issues found within and when using Windows Subsystem for Linux. Please read CONTRIBUTING.md before making an issue submission

  • Do not open Github issues for Windows crashes (BSODs) or security issues. Please direct all Windows crashes and security issues to secure@microsoft.com. Issues with security vulnerabilities may be edited to hide the vulnerability details.

I’ve collected a dump for you, but Github doesn’t let me upload it. Please pm me at shrvtv@protonmail.com, I’ll send it to you.

Here’s what I did:

Enabled windows subsystem for linux

Restarted

Enabled Virtual Machine feature

Restarted to BSOD with “System thread exception not handled”

Entered safe mode and saw “We couldn’t complete updates”

Copied MEMORY.DMP as MEMORY1.DMP

Opened PowerShell as administrator

Disabled virtualization that is required for WSL2

Restarted with no BSOD

Copied MEMORY.DMP as MEMORY2.DMP

Date of both dumps is 10:05 AM, so I guess it’s the same file

Here you go!

My specs:

Ryzen 7 4800H Geforce 1660ti 16GB RAM

Actually I was now just able to manually enable all the features needed to run WSLv2 on latest insiders build (10.0.19541)!

I had enabled each of the following features separately restarting after each:

  • Hyper-V
  • Windows Hypervisor Platform
  • Windows Subsystem for Linux

Then I installed Ubuntu from the Windows Store which gave me a WSLv1 distro working normally. I followed by running the command in powershell: Enable-WindowsOptionalFeature -Online -FeatureName VirtualMachinePlatform and finally before rebooting I ran wsl --set-version Ubuntu 2 which converted my disto to WSLv2 running on Virtual Machine Platform.

After reboot, Windows was able to configure the new optional features correctly however interestingly, the new WSLv2 distro is having networking issues, likely something to do with Hyper-V or Virtual Machine Platform…

Annotation 2020-01-15 182236

Duplicate of #4780

Actually - I had to turn Memory Integrity ON. Can’t believe there’s no other mentions of this because it was the one piece I was missing.

This just fixed it for me too!

For anyone stuck in repair screen after WSL installation, here is how you can rescue your Windows installation. Boot to an Windows installer iso, select command prompt from the repair options instead of “install now”.

Now enter the following:

mkdir d:\tmp
dism /scratchdir:d:\tmp /image:d: /disable-feature /featurename:virtualmachineplatform

in this case “d:” is your windows partition where the windows directory is located. Now your installation should boot again.

btw “BCDedit /set hypervisorlaunchtype Off” wasn’t working in my case.

For those complaining about Thinkpads, I’ve gotten the INACCESSIBLE_BOOT_DEVICE BSOD after trying to turn on “Core Isolation” on a Dell XPS 15 7590. The fix for me was to disable VT-d support in the UEFI/BIOS. (VT-x could stay enabled though.)

Now I’m trying to get WSL2 going, we’ll see if that will work…

I had the same problem and was able to find a workaround. For me, it was probably due to the network driver. Windows 11 uses the 1.0.2.14 for my Intel Ethernet Controller I225-V by default. With version 2.0.1.3 and 2.1.1.7 Windows refused to boot after i installed WSL2. It might also work with other Intel Ethernet I2XX Controller.

This is how i managed to boot into Windows again:

  1. Boot into safe mode without network driver
  2. Uninstall/remove VM-Platform and Windows-Subsystem for Linux
  3. Restart - Windows should now be able to boot again
  4. Uninstall Ubuntu, Docker and Windows Subsystem for Linux Update + GUI
  5. restart

How to get WSL2 up and running like it should:

  1. Uninstall your network adapter driver and let Windows install the default one
  2. Open a command prompt or Powershell with admin privileges
  3. Type in “wsl --install” and wait until it finishes and asks you to restart
  4. Restart and wait until Windows updated everything

You should be welcomed with a command prompt of ubuntu on your desktop now. Enter a username and password, if necessary, and close the session with “exit” in the command prompt. If you dont see an ubuntu shell, open up cmd, type in “wsl -s ubuntu” followed by “wsl” and you should now be in an ubuntu shell. Create a user and password if necessary, otherwise close it with “exit” and close the cmd afterwards.

The vmmem process should now still run in the background for a few more seconds. I opened the task manager and waited until the process terminated itself. Then I restarted the PC and WSL2 including Docker were running fine.

Here are my Systemspecs:

  • OS: Windows 11 Pro 21H2 22000.778 (completly fresh installation with just the drivers installed)
  • CPU: Intel 12900K
  • Mainboard: ASUS Maximus Hero Z690
  • RAM: 2x16 GB DDR5 Corsair Vengance 5200
  • GPU: ASUS TUF 3090 OC (Driver 512.95)

I came here on January 2021 to report that my laptop was not able to run WSL2.

Now I’m happy to report that somehow I have successfully enabled Virtual Machine Platform and converted an existing WSL (Ubuntu 20.04) version from 1 to 2! 🎉

image

I must add that I don’t know exactly what has helped me to get here over an year after all those failing attempts. I’m using the same hardware as before (HP Pavilion laptop with AMD Ryzen 7 4700U) except that the OS is now Windows 10 Home 21H2 (19044.1682).

In case anyone’s curious, here’s a link to my original comment: https://github.com/microsoft/WSL/issues/4784#issuecomment-757403946

Hi @craigloewen-msft . I have a new finding regarding this annoying problem.

I have the same problem: After turn on the feature of Hyper-V on a Windows 10 machine and reboot, the computer wouldn’t get past the three dot wheel(windows logo) before going to a black screen.

My new finding is: The windows is actually booted, the problem may be that the monitor cannot receive any output video signal. The fan of the computer is running, which enlightens me. (Sometimes the big noise of the fan is not that bad.) I can use the remote desktop to successfully login to the system. In remote desktop, everything works fine, including the network and the virtual machine.

Hope this will help to find out the root cause of the problem.

@SharakPL Stop. READ THE THREAD.

If you’d read the thread, you’d notice that I have already listed my hardware multiple times, as have many others. It happens across machine manufacturers and CPU manufacturers. There is NO solution for us yet. It works for you? Great! It doesn’t work for many, many others.

Has anyone tried installing driver updates suggested by Microsoft first?

Settings > Windows Update > Advanced options and here enable first one: Receive updates for other Microsoft products when you update Windows. Then check for updates and install whatever is suggested that involves chipset, processor, etc. It’s probably good idea to install everything suggested.

Also make sure you have latest WSL kernel installed

No, it really doesn’t. This happened a few years ago now and we can’t get MS to fix it or work with manufacturers to fix it.

WSL2 worked fine for a few dev releases then broke on a dev release. We posted about it in the feedback hub, Microsoft didn’t care or even bother to respond. They kept on keeping on, pissing all of us off here. There is NO solution yet and we can’t get help, hence the annoyed nature of many on this thread.

@SharakPL a “hardware problem” that didn’t exist in the dev releases prior to a change they made just before the GA release. They changed something about how they expect drivers to behave and haven’t told anyone (like hardware manufacturers that make drivers).

Confirmed I have this issue on an Asus TUF Gaming laptop 10/31/21.

What first clued me into this I could not convert a VM from wsl version 1 to version 2.

When attempting to enable Virtual Machine Platform feature and restarting the system will go into recovery mode after several failed boot attempts to a black screen with the laptop fans running high. Eventually system repair will fix it.

Edition Windows 10 Home Version 21H1 Installed on ‎9/‎11/‎2020 OS build 19043.1288 Experience Windows Feature Experience Pack 120.2212.3920.0

Processor AMD Ryzen 5 3550H with Radeon Vega Mobile Gfx 2.10 GHz Installed RAM 32.0 GB (31.4 GB usable) System type 64-bit operating system, x64-based processor

PS C:\Users\x> wsl --set-version kali-linux 2 Conversion in progress, this may take a few minutes… For information on key differences with WSL 2 please visit https://aka.ms/wsl2 Please enable the Virtual Machine Platform Windows feature and ensure virtualization is enabled in the BIOS. For information please visit https://aka.ms/wsl2-install

PS C:\Users\x> wsl --list --v NAME STATE VERSION * kali-linux Running 1

PS C:\Users\x> wsl --status Default Distribution: kali-linux Default Version: 2 Please enable the Virtual Machine Platform Windows feature and ensure virtualization is enabled in the BIOS. For information please visit https://aka.ms/wsl2-install

Edit: I solved this by setting UMA mode to Auto in the BIOS.

@craigloewen-msft I have the same bootloop issue on the HP Pavilion 15 with Ryzen 4500u APU. Enabling the Hyper V or Virtual Machine Platform causes bootloop when CPU Virtualization is enabled in BIOS. Unfortunately this PC does not have any configuration options in the BIOS/UEFI beside the simple on/off switch… I had the same outcome on the Windows 10 20H1/20H2/21H1 and currently also on the Windows 11 21H2 (build 22000.282) From what I’ve gathered this seems to be happening often on the AMD Ryzen platform with integrated GPU and disabling the IOMMU seems to help for those who have such option in their BIOS. Such a shame that it’s still a problem after almost 2 years…

EDIT: I’ve been able to solve it with installation of the updated driver for the Realtek card reader (10.0.22000.21351 Rev.C). Again Realtek seems to be the culprit here, but lack of any useful information in the event viewer didn’t help either.

@genio We’ve been trying to run this down internally but it seems to be a myriad of issues that originate in the drivers of 3rd parties, and doesn’t yet to be something that was changed in the Hypervisor stack. Our current recommendation is please to upgrade to the latest versions of your drivers.

@tigls @genio I contacted ASUS, this is the result:

First mail: It is not their problem because:

  • we don’t have information on using WSL2 on their products and therefore they don’t test it
  • we only provide support for OS’s the install on the system (ok, I installed pro instead of the home they installed)
  • I should contact the company that publishes WSL2 (microsoft)

second mail:

  • apart from enabling virtualization (SVM for AMD) in the BIOS they didn’t configure anything for this
  • they checked and they don’t have any problem with VMware and such (and such? - why not check WSL2 since I am asking about that)
  • If I wish the problem can be investigated - but that requires me to send my laptop to ASUS, and they will reset it to factory settings (wtf)

third mail:

  • VMWare (I don’t care about about VMWare but ok) demands like WSL2 that virtualization is enabled (duh)
  • apart from this the support person says he doesn’t have information on use and installation because it is not a standard part of windows 10
  • WSL2 is not a standard part of windows 10 and I need to install the insider version (not true)
  • And (thanks but no thanks) the guy provides a link on how to install WSL2 (ehhh… what?)

fourth mail:

  • after internal consultation at ASUS: ASUS doesn’t claim anywhere that every form of virtualisation or Linux (?) works on the product.
  • ASUS does not provide support because virtualization and WSL2 are not part of the product

The support person did not even bother to check the information I provided (the video on youtube and a link to this thread)

So I guess I should contact Microsoft ergh…

I have the same issue with my ASUS-VivoBook-S15-M533IA Ryzen 4700u. Virtual Machine Platform feature was working fine on Windows 10 1909 until I decided to update first to 2004 and 20H2 in October. I have the BSOD error since then and the only way to boot the machine is to turn off SVM(AMD virtualization) in BIOS.

Also, since someone here has pointed out to the Realtek network driver. When I turned off the Realtek Wireless adapter everything worked, but I don’t have the internet connection and once I enable the wireless adapter back then BSOD happens immediately.

So definitely the windows update broke the compatibility with some drivers because on Windows 10 1909 everything works fine.

I see no hope that Microsoft will fix this. Now I am trying to reach Asus support if they will help with the driver or BIOS update…

@craigloewen-msft suggests submitting the kernel memory dump to the Feedback hub, but the BSOD happens so early that the kernel is just not able to generate the kernel dump, it just reboots instantly. The folder is always empty, I tweaked the settings for memory dump generation back and force but no memory dump or any other appears.

We are still fully investigating this issue, and any further logs will help us. Please see this comment: https://github.com/microsoft/WSL/issues/4784#issuecomment-730727598 for instructions on how to attach and generate a kernel dump to a Feedback Hub item, and link the Feedback Hub item to this thread.

Please remember to only attach kernel dumps to the Feedback Hub items and do not post them directly in this thread. If the kernel dumps are too large (like what you mentioned @shrvtv ) please try and zip them and then attach them, they should compress well.

@urfinj, I am absolutely sure it works on the latest Dev build because I updated to it on my Omen 15 2020 AMD. It looks like someone fixed it accidentally

One whole year later and the answer is “it works on MY machine”, classic 🤣

P.S. I’m sorry, I know you folks work hard, but I couldn’t hold that one in…

Same issue with HP Omen 15 (Ryzen 4600h) and fresh Windows 10 Pro. I tried various tweaks found on the Web like disabling wifi card, installed different AMD drivers, removing AMD Ryzen SDK. Nothing helped. Windows just won’t boot when I enabled “Virtual Machine Platform”.

still broken even after 20H2

and our goal is to keep you all informed which we’ll aim to do earlier in the future

Hi @craigloewen-msft - friendly nudge, any updates?

Thanks everyone for contributing this thread. I am hounding Intel for a solution from their end too. I think I’ve managed to convince them there is actually a problem, but I could use some bumps to break the radio silence.

Please help me out by bumping the thread here, especially if you have the same problem with an Intel computer. If we get enough attention hopefully they will fix it 😄

What in the world do we have to do to get MS to recognize/fix this problem. Y’all have been completely silent in every single method we have of reporting the issue. Not even an “oops”. Crickets. Your feedback hub has this issue listed all over the place… not one single response. Not. One. Twitter, nothing. Here, nothing. Come on, man. Rolling out an update that breaks this many machines is senseless

@hanhwi @kyeongsoo I had the same issue with my AMD ryzen APU laptop (Thinkpad T495) but solved by changing “UMA Frame buffer size” value to “1G” or “2G” in BIOS.

This worked for me too! I have an ASUS laptop with AMD Ryzen 5 3550H. I went to my BIOS settings, and changed my UMA Buffer Size from ‘128M’ to ‘Auto’ (those were the only 2 options. 1G, 2G weren’t there for me). Restarted. Enabled Virtual Machine Platform. Restarted.

It reboots! After that, successfully installed WSL 2 and updated my WSL Ubuntu to version 2 as well.

Thanks @gasuketsu

Still convinced the original stated issue exists though, my comment above was just a strange no-reboot workaround. A clean install of latest insider’s build still does fail to boot after enabling both Windows Subsystem for Linux & Virtual Machine Platform as per the WSL2 install docs.

Fixed my above network issue via https://github.com/microsoft/WSL/issues/4285#issuecomment-522201021 in case anyone else runs into same problem

Very probably a recent(ish) regress because there’d be more screeching when WSL2 was released to Insiders last Spring, and these two (w/ #4780) came in back-to-back.

Windows Feedback Hub link, My blog post w/ some additional details

Windows feedback hub was the right thing to do (thanks!). The feedback hub isn’t as black a hole as some might imagine it to be. If a lot of people report a problem they do get looked at.

Technet hyper-v forum not a bad place to post too.

I feel like I should close this issue

Open, closed; not a big difference in this instance. It was constructive to post here so folks doing a search know they’re not alone.

Was wondering if anyone on this thread has tried to disable Kernel DMA protection? Two ways to do it. Either you disable it in bios or in my case had to disable Memory Integrity protection directly in Windows Security settings. How to: Settings -> Update and Security -> Windows Security -> Open Windows Security -> Device Security -> Core Isolation -> Memory Integrity -> Turn Off. Just an idea worth pursuing…

Actually - I had to turn Memory Integrity ON. Can’t believe there’s no other mentions of this because it was the one piece I was missing.

I had incompatible drivers which prevented me from turning on Memory Integrity. I’m guessing that Windows tried to turn the setting on when it enabled the “Virtual Machine Platform” feature, and that’s what caused the boot failure. I tried boot logging and noticed that I had many “BOOTLOG_NOT_LOADED” lines. After resolving the driver issues, I enabled Memory Integrity and everything worked!

Issue https://github.com/microsoft/WSL/issues/11384 is what got me to the solution, and this Microsoft forum answer had some good guidance on uninstalling drivers.

Image

I have an ASUS FX505DV and am running Windows 11. On the advice of this Reddit thread, I set SVM Mode to “Enabled” and UMA Frame buffer Size to “Auto.” This completely resolved the issue for me.

ASUS TUF FX505DT user here. You saved me! As many people have commented, no Hyper-V necessary for my case. wsl --install along with enabling virtual machine platform and windows subsystem for Linux features, all in one go, then stuck in black screen after vendor logo. After setting the UMA frame size to auto, Windows finally booted.

Changed UMA to AUTO fixed my Asus TUF FX505DT.

I have an ASUS FX505DV and am running Windows 11. On the advice of this Reddit thread, I set SVM Mode to “Enabled” and UMA Frame buffer Size to “Auto.” This completely resolved the issue for me.

ASUS TUF FX505DT user here. You saved me! As many people have commented, no Hyper-V necessary for my case. wsl --install along with enabling virtual machine platform and windows subsystem for Linux features, all in one go, then stuck in black screen after vendor logo. After setting the UMA frame size to auto, Windows finally booted.

This also saved my life.

I experienced exactly the same issue.

Windows 11 Pro, OS build: 22621.1702 Lenovo P53

I had exactly the same issue (well, at least symptoms) on Win 11 / Dell XPS 15” (Intel).

  1. After getting stuck in the boot loop, I disabled both virtualization and “Virtualization for Direct-IO” in the BIOS to boot normally
  2. I rebooted in to Windows and enabled Virtual Machine Platform again in Turn On/Of Windows Features
  3. I had to re-enter the BitLocker passcode for some reason to boot, but the computer booted normally
  4. After booting up, WSL2 finished its installation automatically. It had clearly got stuck in the middle of the process during my previous attempts.

I am not certain was the “Virtualization for Direct-IO” the real culprit or did I just got lucky…

This issue is discussed in https://www.dell.com/community/XPS/XPS-15-7590-Memory-Integrity-on-causes-an-inaccessible-boot/td-p/8273941. Note that in spite of the “Solved” label, the issue is not solved (apparently they are waiting for someone with an in-warranty XPS to send it in for study in exchange for an equivalent system).

Same issue yet on another Lenovo. I have encountered countless issues that I suspect to be firmware related on this ThinkPad. Will never buy a Lenovo again 🙄

I have been using WSL1 and WSL2 for years with no problem before I encountered this issue. Several days before I loaded the default BIOS setting (for stupid reasons) and got the INACCESSIBLE BOOT DEVICE. At that time I didn’t know it is virtualization related. I followed a bunch of YouTube videos and the only thing that worked was resetting the Windows. The next day I was setting up my dev environment and installed WSL and the same issue occurred, which lead me to this thread.

After I disable VT for Direct I/O in BIOS my device boots again. My question is: does this not need to be enabled? I might be wrong, but it seems like I can’t go forward with WSL, WSLg, docker, etc. with this setting disabled?

I disabled DMA and VT for Direct I/O in BIOS and can boot again. I am actually able to use WSL with those disabled. Things seem to work as before except that Windows Defender is giving me a warning for disabling DMA. Haven’t tried docker though.

Edition	Windows 11 Home
Version	22H2
Installed on	‎10/‎20/‎22
OS build	22621.675
Serial number	R90S3C36
Experience	Windows Feature Experience Pack 1000.22634.1000.0

System Manufacturer	LENOVO
System Model	20MF000BUS
System Type	x64-based PC
System SKU	LENOVO_MT_20MF_BU_Think_FM_ThinkPad X1 Extreme
Processor	Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz, 2208 Mhz, 6 Core(s), 12 Logical Processor(s)
BIOS Version/Date	LENOVO N2EET59W (1.41 ), 8/2/22
SMBIOS Version	3.1
Embedded Controller Version	1.15
BIOS Mode	UEFI
BaseBoard Manufacturer	LENOVO
BaseBoard Product	20MF000BUS
BaseBoard Version	SDK0R32862 WIN
Platform Role	Mobile
Secure Boot State	On
PCR7 Configuration	Elevation Required to View
Windows Directory	C:\WINDOWS
System Directory	C:\WINDOWS\system32
Boot Device	\Device\HarddiskVolume1
Hardware Abstraction Layer	Version = "10.0.22621.1"
Installed Physical Memory (RAM)	16.0 GB
Total Physical Memory	15.6 GB
Available Physical Memory	9.78 GB
Total Virtual Memory	18.4 GB
Available Virtual Memory	11.1 GB
Page File Space	2.88 GB
Page File	C:\pagefile.sys
Kernel DMA Protection	Off
Virtualization-based security	Running
Virtualization-based security Required Security Properties	
Virtualization-based security Available Security Properties	Base Virtualization Support, Secure Boot, UEFI Code Readonly, SMM Security Mitigations 1.0, Mode Based Execution Control
Virtualization-based security Services Configured	
Virtualization-based security Services Running	
Windows Defender Application Control policy	Enforced
Windows Defender Application Control user mode policy	Audit
Device Encryption Support	Elevation Required to View
A hypervisor has been detected. Features required for Hyper-V will not be displayed.

Was stuck in a boot loop as well. Got the BSOD with INACCESSIBLE_BOOT_DEVICE. After I disable VT for Direct I/O in BIOS my device boots again. My question is: does this not need to be enabled? I might be wrong, but it seems like I can’t go forward with WSL, WSLg, docker, etc. with this setting disabled?

Please correct me if I’m wrong and what should/could I do if this has to be enabled? At the moment I am working on a fresh install of Windows 11 Pro

Version	22H2
Installed on	‎18/‎10/‎2022
OS build	22621.525
Experience	Windows Feature Experience Pack 1000.22634.1000.0

My hardware specs are the following:

Processor	Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz   2.59 GHz
Installed RAM	32,0 GB (31,7 GB usable)
System type	64-bit operating system, x64-based processor

I was able to install WSL2 without any errors after disable IOMMU in the BIOS. Before that I couldn’t boot into Windows with VSM Mode Enabled.

My Systemspecs:

  • CPU: AMD Ryzen 5 3400G
  • RAM:16,0GB Dual-Channel DDR4
  • Motherboard: ASRock A320M-HD
  • OS: Windows 10 20H2 (19042.2006)

I hope this helps someone!

The history here leaves little doubt this bug is specific to certain CPU and/or BIOS particularities. However, the earliest history also makes clear that the bug is a regression – there were early builds of WSL2 that did not have this issue, there was a specific point it broke, and the affected systems have been broke ever since. It would be nice if Microsoft would unbrick these systems. It would also be nice if Microsoft would extend its various partner certification programs like WHQL and whatever allows laptop manufacturers to affix the Windows sticker to include compatibility with WSL2, so that developers did not have to worry that an expensive purchase might turn out to be useless for their work.

TL;DR I believe this to be a limitation of your CPU if you have this problem and it can likely be solved by upgrading – not something you always want to hear.

So I have an update that may be of some value to you all. This is a continuation of my year-long journey with this particular topic. Since I require WSL2 for part of my work, I have been working off of my laptop much of the time for the past 6 months, which works fine (it is the DELL XPS 17 Core i9).

In an effort to get my desktop working up to par, I decided to buy a new motherboard since my old motherboard wouldn’t allow me to flash it and I had thought at the time that it was part of my issue. So about a week ago, I upgraded my motherboard and it seemed like things were working okay at first, got WSL2 installed, got Hypervisor and what not going, all things that didn’t seem to work before. But then I rebooted a couple of times, and wouldn’t you know it, it decided to hang at startup again. Interestingly, the first time, after waiting 10 minutes, it loaded up. But subsequent times, it didn’t and required me to disable VMX in my new BIOS settings.

At the same time, I noticed that my M.2_1 slot worked, but my M.2_2 and M.2_3 slots did not work. After researching this, I found that the Core i7 pre 9000 series does not have enough channels to support additional M.2 lots (I guess it jumped from 24 to 48 channels in the 9000 series). At this point, I decided to upgrade my CPU as well and got a Core i9, 10000 series. Now, everything works fine with no hanging at startup – and I have my other M.2 slots working.

My theory is that the number of channels on your CPU is the base culprit for this problem – it just doesn’t have enough juice to power virtualization. Maybe a bigger hardware junkie can confirm or deny the possibility of this theory, but I can tell you that upgrading the motherboard didn’t solve the problem, but upgrading the CPU did. So I finally have WSL2 on my desktop with no hang at startup.

I have a dual boot system. When I enable hardware assisted virtualization in the bios, linux has no problem booting, windows 10 home fails to boot. If I disable virtualization in bios , linux no problem, windows boots, docker cannot run.

Device name amdr Processor AMD Ryzen 5 2500U with Radeon Vega Mobile Gfx 2.00 GHz Installed RAM 8.00 GB (7.71 GB usable) Device ID 459AFC33-63C7-4BFD-96B2-D94C90287A9C Product ID 00325-95827-58729-AAOEM System type 64-bit operating system, x64-based processor Pen and touch Pen and touch support with 10 touch points

Hope this is useful, let me know if additional info needed.

I have the same problem: After turn on the feature of Hyper-V on a Windows 10 machine and reboot, the computer wouldn’t get past the three dot wheel(windows logo) before going to a black screen.

You don’t need Hyper-V for WSL2 to work. Tried again on my old machine at work, but this time I enabled everything manually from “Turn windows features on/off” window. Enabled only Virtual machine platform and Windows subsystem for linux (everything from Hyper-V tree is disabled) and of course installed new kernel. No problems with boot this time. Everything seems to work fine: Ubuntu on WSL2, docker, etc.

@brucek2 @mike3e @genio @Manguil Are you able to try the remote desktop to login to the black screen system? @samduanx 你可以试试用远程桌面登录那个黑屏了的系统么?

No, mine doesn’t even go into the system before. 我之前是进系统前直接就重启了

P.S. Mine’s working now after I turned that enhanced security off. 注:我把BIOS里那个选项关了然后就好使了

Seems more obviously that this problem is heavily dependent on the hardware.

@brucek2 @mike3e @genio @Manguil Are you able to try the remote desktop to login to the black screen system? @samduanx 你可以试试用远程桌面登录那个黑屏了的系统么?

Hi folks, I’m temporarily locking this issue to reduce spam. The update here is we’re still trying to reliably reproduce this on any machines, so posting any hardware sets or repro steps for us to try are helpful. Thank you all for your patience!

Have you actually read the thread? Of freaking course we’ve been updating drivers for over 2 years. Seriously, you’re unhelpful. Stop

Can it be related to GPU? I have old GT630 at work. Fermi so can’t even install drivers newer than 391.35 😢 Tried to enable WSL2 there (CPU is Phenom II X4 965 - no support for SSE4.2, but it worked fine with WSL1). Enabling all required Windows features and installing new kernel made system unusable after restart. Now it freezes and changes endlessly from black to login screen.

👉 Quick tip 👈 No need to use safe mode or revert windows to previous working configuration and such. Just disabling Virtualization in BIOS should allow clean boot.

I’m hesitant to put this here as I doubt anyone can follow my recent journey, but I FINALLY was successful with this on my problematic machine.

First, in the process of searching for some BIOS setting that would resolve this, I discovered my BIOS had PTT (Trusted Module) available, so I was able to enable it. It caused a full motherboard crash and CMOS reset and I went back to factory defaults [Note, my motherboard is a GIGABYTE X299 AORUS Gaming 7 Pro LGA 2066 Intel X299 SATA 6Gb/s USB 3.1 ATX Intel Motherboard]. After that, I was able to install Windows 11.

After a successful upgrade to Windows 11, I tried many different avenues to get things to work and many, many reboots. The typical cycle was:

  1. Attempt to turn on a Windows Optional Feature such as Hyper-V or Virtual Machine Platform
  2. Reboot machine
  3. Watch the machine update to 30% and then restart
  4. Machine POSTs and then tries to load windows and circular spinner runs forever
  5. Reset the computer
  6. Advanced repair and recovery begins
  7. Once at the recovery window, go to advanced, additional options, startup options and reboot
  8. Start in Safe mode with Networking (option 5)
  9. Machine loads into Safe Mode and either resets before fully loading, undoing changes, which allows you to fully get into Windows OR it lets you fully into Safe Mode, in which case a reboot still won’t let you start up, so you have to go into an Administrative command prompt and run bcdedit /set hypervisorlaunchtype Off as can be found in various StackOverflows as well as here: https://www-thewindowsclub-com.cdn.ampproject.org/v/s/www.thewindowsclub.com/windows-does-not-boot-after-hypervisor-platform-or-svm-mode-is-enabled?amp_js_v=a6&amp_gsa=1&amp&usqp=mq331AQKKAFQArABIIACAw%3D%3D#aoh=16361644399924&csi=1&referrer=https%3A%2F%2Fwww.google.com&amp_tf=From %251%24s&ampshare=https%3A%2F%2Fwww.thewindowsclub.com%2Fwindows-does-not-boot-after-hypervisor-platform-or-svm-mode-is-enabled

I repeated many different attempts an amalgamations of this to no avail. I also attempted setting bcdedit /set hypervisorlaunchtype Auto at the same time I tried to install Hyper-V and that made it so I couldn’t get into safe mode, at which point I disabled VT-d in BIOS and was able to get back into Windows.

What I did different to get things to work (not necessarily repeatable by others): With VT-d disabled in BIOS, I did the following:

  1. opened an administrative command prompt
  2. run command for enabling WSL: dism.exe /online /enable-feature /featurename:Microsoft-Windows-Subsystem-Linux /all /norestart
  3. run command for enabling ‘Virtual Machine Platform’: dism.exe /online /enable-feature /featurename:VirtualMachinePlatform /all /norestart
  4. reboot

The usual 30% update and reboot happened, followed by the machine failing to boot into Windows. But then I went into UEFI/BIOS settings and turned VT-d back on and for some reason, it booted into Windows AND installed the remaining “70%” of stuff that it never installed before – so somehow I tricked the system into installing what I needed. After getting into Windows, I was able to run Powershell as administrator and: 5. run wsl --set-default-version 2 6. upgrade my distro with wsl --set-version Ubuntu-20.04 2

So now, despite all odds, I somehow have Windows 11 with WSL2 successfully running on this machine. I don’t know if this will help anyone else, but I guess perseverance eventually pays off. If Microsoft insists we use a type of Hyper-V to run WSL2, then they need to seriously fix this issue as I have been battling it for many months now along with the rest of you.

UPDATE: System seems still a bit unstable on reboots and being able to keep it on may be a challenge. Not sure what the hangup is, but it definitely revolves around the bcdedit /set hypervisorlaunchtype Auto flag

UPDATE 2: I was able to set hypervisorlaunchtype to Off, then reboot and get my windows updates, then turn it back on and reboot successfully. So not perfect, but I can live with it since I reboot about once a month.

even with the latest realtek driver, it still doesn’t work for me *

Same issue here on Windows 11 Home Ryzen 3200G machine

The workaround disabling SVM then adding in Virtual Machine Platform doesn’t ultimately work for me as although the add feature step works, I’m back to the reboot loop when I re-enable SVM and have to rollback.

EDIT: ok I seem to have ultimately solved the problem by updating the BIOS to the latest version that appears to have something to do with SVM support, but it’s not clear. WSL 2 now fully operational!

I can’t reboot after wsl --install. Get stuck forever in a “please wait while we install a system update” loop. HP Envy 21H2 Windows 11 21H2 (OS build 22000.258)

I solved it by switching to Linux. Wrote about my pains and huge deception on LinkedIn. If specially you need it for work or some urgent matter, please consider Linux. Mint is very beginner friendly. Choose Rufus btw.

I have got this issue recently after updating my new Hp laptop to windows 11. whenever I try to install the wsl2, the system doesn’t boot. In hp bios, there is no option for buffer size. Not being able to install WSL2 on a new laptop is so much annoying. And it is an issue for almost 2 years why isn’t Microsoft solving this issue.

I don’t think the original issue was about QEMU, but that was were my problem came from as well. Managed to fix it by doing this: https://docs.fedoraproject.org/en-US/quick-docs/using-nested-virtualization-in-kvm/

More specifically info-icon->CPUs, I unchecked Copy host CPU configuration and selected host-passthrough in the Model field. Managed to follow the rest of the WSL2 instructions and get it running!

Same problem with qemu (Proxmox).

  • Windows 20H2 (OS Build 19042.1110)
  • QEMU emulator version 5.2.0 (pve-qemu-kvm_5.2.0)
Proxmox# cat /sys/module/kvm_intel/parameters/nested
Y
Proxmox# cat /sys/module/kvm_intel/parameters/ept
Y

This is causing an issue now since I wanted to use Docker for Windows but that relies on WSL2 being installed and working. Hopefully, we can contribute to helping solve this issue.

I have the same issue with my ASUS-VivoBook-S15-M533IA Ryzen 4700u. Virtual Machine Platform feature was working fine on Windows 10 1909 until I decided to update first to 2004 and 20H2 in October. I have the BSOD error since then and the only way to boot the machine is to turn off SVM(AMD virtualization) in BIOS.

Also, since someone here has pointed out to the Realtek network driver. When I turned off the Realtek Wireless adapter everything worked, but I don’t have the internet connection and once I enable the wireless adapter back then BSOD happens immediately.

So definitely the windows update broke the compatibility with some drivers because on Windows 10 1909 everything works fine.

I see no hope that Microsoft will fix this. Now I am trying to reach Asus support if they will help with the driver or BIOS update…

@craigloewen-msft suggests submitting the kernel memory dump to the Feedback hub, but the BSOD happens so early that the kernel is just not able to generate the kernel dump, it just reboots instantly. The folder is always empty, I tweaked the settings for memory dump generation back and force but no memory dump or any other appears.

I have the same machine and exactly the same problem

set UMA frame buffer size to AUTO and ENABLE SVM mode this worked for me in my ASUS TUF Gaming FX705 x64-based windows OS PC WhatsApp Image 2021-02-26 at 8 02 49 PM

Yes, but available RAM is reduced by 3 GB. VirtualBox and VMware work pretty fine with UMA 512 MB.

set UMA frame buffer size to AUTO and ENABLE SVM mode this worked for me in my ASUS TUF Gaming FX705 x64-based windows OS PC WhatsApp Image 2021-02-26 at 8 02 49 PM

@RyanUnderhill generating a kernel dump per the instructions here https://github.com/microsoft/WSL/issues/4784#issuecomment-730727598 would be the most helpful! I’ll follow up with you via email to see if we can do some more advanced debugging 😃

@FelixTUD is right, it’s because of the newer Realtek WLAN driver.

@urfinj Yea, it was broken over a year ago in a developer program release. At that time it was reported to the Feedback Hub (worst tool ever) many, many times. We also reported it everywhere else we could think of, including this issue.

This issue kind of got Microsoft to notice it in a round-about way. This team isn’t responsible for the breakage, but they’ve been listening to our gripes and punting it off to the right people to finally get us heard. Apparently a few people here have been able to give dumps of the failure to Microsoft now on the Feedback Hub and the people in charge of this project have pointed the others to those entries. We might see this fixed this year now. \o/

I’ve tried a completely fresh system on my HP Omen (4600H), haven’t installed any 3rd party utils, and even didn’t connect to the Internet. But still, once I enabled “Virtual Machine Platform” it couldn’t boot.

I might also add the helpful reports in this issue may ultimately be covering more than just one bug. I too would request we keep it open until we can see which of the reported reproducible cases are in fact no longer reproducible.

Hello again. I tried submitting kernel memory dump using Feedback Hub, but it says the file is too large. I have uploaded it to Google Drive, please message me at shrvtv@gmail.com from your microsoft work email, so I can give you access to the memory dump

Hi @craigloewen-msft , how can we contribute? Do we need to submit logs etc? If yes, please let us know, we also want this issue to be resolved.

@craigloewen-msft Were you able to find out anything more from the relevant teams? It would be awesome to get a status update on this issue.

@HJBDev ESEA Support won’t help, they added an article to the FAQ after I asked support claiming that Hyper-V enables cheats and blah blah blah, they are firm that they will not support Hyper-V. I wrote a quick powershell script to enable Hyper-V and disable their always-on anti-cheat, and another one to do the reverse. esea.zip

Same issue here on an HP omen with the Ryzen 5 4600H. Windows will boot with either Virtual Machine Platform or virtualization in bios enabled, but having both on causes a blue screen. Unfortunately I can’t change the UMA buffer since HP doesn’t provide that option in the bios.

I have a similar issue on a Lenovo Flex 5 on Ryzen 5 4500U. The computer is able to work fine and use virtual machines and WSL 2, but on restarting (by clicking restart, not shutdown and turn back on), it gets stuck on a boot menu (Windows Boot Manager listed but selecting does nothing), which can only be escaped by pressing the power button. Then it continues restarting fine. This only happens when I have Hyper-V, WSL 2, or Windows Sandbox enabled.

I also have no option to change UMA buffer in BIOS.

I had the same issue with my AMD ryzen APU laptop (Thinkpad T495) but solved by changing “UMA Frame buffer size” value to “1G” or “2G” in BIOS.

I just tried this and it worked!

With SVM off, my BIOS had Auto, 256MB, and 512MB options. With SVM on, it removed 256MB from the list.

I previously had 512MB selected. After changing it to Auto, I turned SVM on and Windows booted successfully! Thank you so much!

I will let you all know if WSL 2 works correctly in a moment.

EDIT: It works great!

Thanks, this worked for me too. I just changed UMA buffer size value to AUTO and it worked.

PC model :- Asus TUF

I had the same issue with my AMD ryzen APU laptop (Thinkpad T495) but solved by changing “UMA Frame buffer size” value to “1G” or “2G” in BIOS.

I just tried this and it worked!

With SVM off, my BIOS had Auto, 256MB, and 512MB options. With SVM on, it removed 256MB from the list.

I previously had 512MB selected. After changing it to Auto, I turned SVM on and Windows booted successfully! Thank you so much!

I will let you all know if WSL 2 works correctly in a moment.

EDIT: It works great!

Same issue here, SVM on AMD = black screen after installing virtualization platform, turning off fastboot did not help, I went back to Manjaro on this machine until this gets sorted out.

The BIOS on my Gigabyte Aero 15 does not offer a Fast Boot option one way or another.

The Fast Boot option in Windows is located in Control Panel > Power Options > Choose what the power buttons do (on the left side).

Side note: the Gigabyte Aero 15 doesn’t have an AMD processor, so that rules out the exact same root cause as mine, driver-wise.

I’d also appreciate any tips if there are shortcuts that would speed up my testing cycle

Try turning off virtualization/VT-x/d in the BIOS. That let me boot when I installed VirtualMachinePlatform.

You could try the driver bisection method I mentioned in my earlier comment to diagnose if it’s a driver thing, but it’s very annoying and requires manual registry editing. Let me know if you’re open to that and I can give you more details!

Try disabling fast boot and see if that helps.

By typing BCDedit /set hypervisorlaunchtype Off I no longer have a problem with the black screen not booting and my wsl works.

It is not work for me

After some continued troubleshooting, the root problem appears to be I can’t enable Hyper-V on Version 10.0.19536.1000 of Windows. Enabling/installing it prevents my PC from booting.

I formatted and started over to get back to build 1909 and I can install Hyper-V and therefore run WSL (v1 of course).

Windows Feedback Hub link, My blog post w/ some additional details


I feel like I should close this issue as it doesn’t appear to be a WSL 2 issue but a Hyper-V/Windows 10 issue. 🤔