Can't boot after WSL 2 Install

[spottedmahn]

• Your Windows build number: Version 10.0.19536.1000

• What you're doing and what's happening: After, Enable the 'Virtual Machine Platform' optional component and make sure WSL is enabled, I can't boot into Windows.

• What's wrong / what should be happening instead: I should be able to boot into Windows

• Strace of the failing command, if applicable: N/A

• For WSL launch issues, please collect detailed logs.

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).

[spottedmahn]

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? 🤔).

[emersonclaireiaquinto]

Having the same issue, it also occurs while enabling the virtual machine platform through the windows features GUI, though it at least got to 15% updating before it hung

[ev-dev]

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.

[ev-dev]

Duplicate of #4780

[spottedmahn]

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. 🤔

[therealkenc]

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.

[spottedmahn]

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

[ev-dev]

The issue is coming from one of the last few insider builds, I had no trouble getting WSL2 going on a clean install last month.

I'm not sure exactly how Hyper-V is involved though, I'm currently running 19541 build with the Hyper-V and Windows Hypervisor Platform features enabled without boot issues. The specific cause for my own failure to boot is when enabling the Virtual Machine Platform feature, is that the case for you @therealkenc or are you not able to boot with Hyper-V feature alone?

My understanding is that the Virtual Machine Platform is a thinner version of Hyper-V that is used for specific features like WSL2 (maybe exclusively for WSL2?). If that is the case, than this issue may not be coming from Hyper-V itself, hopefully those more knowledge will chime in though

[ev-dev]

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...

[ev-dev]

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 #4285 (comment) in case anyone else runs into same problem

[therealkenc]

is that the case for you @therealkenc or are you not able to boot with Hyper-V feature alone?

I'm personally able to boot no problem. Haven't touched the Windows features since I can remember.

[spottedmahn]

Still convinced the originally stated issue exists though, my comment above was just a strange no-reboot workaround

So I'm not crazy! I thought I had WSL 2 working too! I know I was running wsl -l -v and saw v1 labels. Until I rebooted (or did something else).

---

Haven't touched the Windows features since I can remember

Fresh install of Windows for me.

---

I don't know what this means but I suspect it is related to the underlying issue:

Notice the "partial checked state" but both sub-items are checked? 🤔

[therealkenc]

I don't know what this means

Me either. Mine looks like this FWIW.

[benhillis]

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

[NikolasTzimoulis]

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

@ev-dev I tried this and it didn't work for me. I rolled back my Windows to version 19541. Then installed Hyper-V through dism and restarted. I tried to do the same for Windows Hypervisor Platform and Windows Subsystem for Linux but they were already installed. Next I ran wsl --set-version Ubuntu 2 which didn't work; it said Please enable the Virtual Machine Platform Windows feature and ensure virtualization is enabled in the BIOS. (which I've done). Then I enabled VirtualMachinePlatform like you said and after that I attempted a restart and got stuck on the Windows logo screen during reboot. (I got out of that by running BCDedit /set hypervisorlaunchtype Off but obviously now I have no virtualization features.)

Any advice?

---

EDIT: Everything seems to be working now after I updated to the just-released Windows build 19551. I converted from WSL1 to WSL2 with no issues using the normal procedure.

[kevinfaveri]

It is happening with me in a Windows 10 Pro Version 19041.21. Just after enabling WSL2 with Docker Desktop Edge and installing a VM using WSL2 from Windows Store i could not boot anymore...
My "solution" was to restore a point in time through windows recovery, but I still havent found a solution for using WSL 2 without bricking the boot.

[jbooth-sr]

Also have Win 10 Pro V19041.21, WSL2, and Docker Desktop Community and getting the black screen on boot periodically -- have to hold the power down and hope the next boot comes up normal which is about half the time.

[makenum]

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

[kunzig940]

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...

[brucek2]

Reproducible for me:

1. Do fresh install of build 19041 from USB
2. Accept all updates from Windows Update, which required a reboot.
3. Open explorer, follow prompts to download the new Edge browser (*probably not necessary to reproduce, but it's what I did all 3 times this happened to me.)
4. Open powershell (admin)
5. dism.exe /online /enable-feature /featurename:Microsoft-Windows-Subsystem-Linux /all /norestart
6. dism.exe /online /enable-feature /featurename:VirtualMachinePlatform /all /norestart
7. Restart.

Result:
Boot hangs at vendor splash screen.
Will keep hanging at splash screen until safe mode is entered, which reverts the dism command(s).

Fixes/Workarounds:

1. Adding step 4.5 "BCDedit /set hypervisorlaunchtype Off" worked for me as far as fixing the hang on boot (although it meant I could not use WSL)
2. I did not have this issue when I installed 2004 via the Update process. (UPDATE: I have since spent many hours trying to reproduce this brief initial success but did not find any way to do it.)

[NoelTautges]

I have been encountering a problem like this since September 2019 both on stable and Insider versions of Windows and have only just found this issue. I am not 100% sure it is the same problem, but on the off chance it is, I would like document my experience.

Booting Windows results in it hanging on a black screen after the progress circle when virtualization (AMD SVM) is enabled in the BIOS. The fan runs at full blast and the shell never starts.

I did some bisection with system drivers and found that when I disabled atikmpag.sys, the AMD integrated graphics display driver, the system booted fine with virtualization enabled. Since my system did not work well without the driver, I decided to live with the issue and not use WSL 2.

Today, after reinstalling Windows 1909 in another attempt to fix the issue, I found that it was fixed and I could boot with virtualization enabled. However, after installing the Virtual Machine Platform feature, as required by WSL 2, my machine stopped booting again. I updated to the Fast ring, build 19631.1, and the issue continued to appear.

My uneducated guess is that having SVM and the Virtual Machine Platform enabled means something is triggered in atikmpag.sys to make the system hang during bootup. I will attempt to debug the issue once my cable arrives in 2 days' time.

[jbooth-sr]

Try disabling fast boot and see if that helps.

[NoelTautges]

Try disabling fast boot and see if that helps.

Regretfully, it did not.

[brucek2]

(@jbooth-sr: The BIOS on my Gigabyte Aero 15 does not offer a Fast Boot option one way or another.)

I've spent many hours since my last post trying to find a successful combination of build version, updates taken or skipped, updating or not updating drivers on my own, and previously installing WSL 1 or not. They all failed. In every combination I tried, I was left with a binary choice of enabling Virtual Machine Platform and not being able to boot, or not enabling it and not being able to use WSL.

Clearly many other users are in fact using WSL 2 successfully, leading me to wonder whether the issue is about a specific incompatible driver or other quirk on my machine; or is about a subsequent patch to Windows or WSL that has made it impossible for new WSL 2 users to get past the initialization stage.

My initial, one brief success may have hinged on either something I installed/configured during my regular use of the machine that was lost once I did a fresh install; or perhaps was enabled by being prior to some system firmware update being applied (do the Intel microcode updates work that way?)

I am not savvy on debugging windows boot issues so do not know how to proceed further. I'm open to suggestions. I'd also appreciate any tips if there are shortcuts that would speed up my testing cycle: right now each try is very painful, requiring multiple failed reboots to access safe mode, having to say "I forgot my PIN" because that process locks out the normal log in mechanism, and not being able to access the recovery command console because it will not take my password.

I've also filed this as a new issue via the feedback hub. Given it is reproducible on at least my machine I feel like someone in QA should confirm whether the documented install procedure works on a fresh install of build 19041 with the current applicable updates on at least some machines.

[NoelTautges]

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!

[brucek2]

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

Oh! Thank you. I tried it, but no difference.

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

Interesting. That hack lets me survive the reboot following enabling VirtualMachinePlatform, which lets Windows complete its setup, and gets me access to the wsl console command. This lets me enter the third command from the setup instructions (set wsl default version to 2). But when I go to the Store after that and go to the Ubuntu page, it hangs on a spinning circle. I rebooted, re-enabled VT-X, but was right back at the hang on boot problem.

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!

Thank you for the offer! Having spent my weekend on this issue as it is, it's past due for me to return to current work, and that process does not sound quick. Maybe I'll try again next weekend.

[chanyut]

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

Oh! Thank you. I tried it, but no difference.

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

Interesting. That hack lets me survive the reboot following enabling VirtualMachinePlatform, which lets Windows complete its setup, and gets me access to the wsl console command. This lets me enter the third command from the setup instructions (set wsl default version to 2). But when I go to the Store after that and go to the Ubuntu page, it hangs on a spinning circle. I rebooted, re-enabled VT-X, but was right back at the hang on boot problem.

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!

Thank you for the offer! Having spent my weekend on this issue as it is, it's past due for me to return to current work, and that process does not sound quick. Maybe I'll try again next weekend.

Thanks, you save my day. I got the same issue in my T495 (AMD). After enter bios and disable AMD virtualization. I can boot into windows.

[dlford]

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.

[alanlal]

I'm running Windows 10 Home Version 10.0.19631.1 with AMD Ryzen 5 3550H. I used to have the same issue after turning Virtual Machine Platform on.

But, I was able to boot normally after doing the following steps.

1. Turn off virtualization in your BIOS.
2. Go to "Turn windows features on or off " and turn on :
   • Virtual Machine Platform
   • HyperVisor Platform (I understand there's no HyperVisor in Home Edition,but it's still showing)
3. Restart the machine
4. Turn on "Windows Subsytem for Linux"
5. Install your favourite distro
6. Go to BIOS and turn virtualization on
7. Restart windows

Although, I should mention that I have received blue screen of death a couple times after doing this. But I'm attributing that to my OS being in the fast track insider edition.

I even installed wsl2 version of docker later.Its working fine.

[albuquerquejp]

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!

[HappyDingning]

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

[thangamani-arun]

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/

[thangamani-arun]

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 had ubuntu 20.04 before installing

git clone https://github.com/DamionGans/ubuntu-wsl2-systemd-script.git
cd ubuntu-wsl2-systemd-script/
bash ubuntu-wsl2-systemd-script.sh

after restarting LxssManager, my WSL was in infinite loop. above steps really worked to come out of it.

[ducmthai]

I got the same issue with a BSOD: UNMOUNTABLE_BOOT_VOLUME. I went to BIOS and disable DMA, VT-x and VT-d are on and I can boot normally. Initially, the Virtual Machine Platform prevented me from upgrading to 22H2. I removed it and I can upgrade but ended up with the BSOD. Hope this help someone but definitely it's a bug.

• OS: Microsoft Windows 11 Pro, 10.0.22621 N/A Build 22621 (22H2)
• System Model: 20MFCTO1WW - Thinkpad X1 Extreme 1st gen
• Processor(s): Intel(R) Core(TM) i7-8850H
• BIOS Version: LENOVO N2EET59W (1.41 ), 8/2/2022

All drivers and firmware are at their latest per Lenovo Vantage + Lenovo Laptop support page.

[mich2k]

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

[TacticsJan]

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

[Ruminateer]

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.

[TacticsJan]

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.

@owned139 , How did you know which network driver your Windows 11 uses by default? This is the last workaround I can try on this thread but am kind of confused how you got this information?

When I uninstall my network driver and let windows look for drivers it just installs exactly the same. Does "let Windows install the default one" mean you just click "scan for hardware changes" after uninstalling your current driver?

EDIT: Important notice for anyone facing these problems. You don't need vt-d for wsl, wsl2 and/or wslg. So just disable vt-d in your BIOS and reboot. Install wsl like you normally would and everything should be working fine.

[ZPrimed]

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...

[Akbari300]

@ZPrimed I face the same problem with the Error message. have you been able to solve it?

[JasonBSteele]

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.

[jvert]

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)

[nojb]

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).

[fenilli]

I have this problem with my PC but not my notebook, this only happens with W11 and with an installation that has secure boot disabled, it looks like if you have a installation that disabled secure boot, it will break the boot when installing WSl2.

[Daasin]

UMA Frame Buffer fix didn't work, it's set to 1G on Steamdeck by default and setting it to 4G didn't help either. There is no auto option. Same whether on IOMMU or not

[stedwick]

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.

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

[jontabiendo]

I’m encountering a similar issue here. After installing wsl2 and restarting to complete installation. It seems my pc fails to send a signal to my monitor.

The monitor and cable both work just fine on other computers, so it’s definitely with my pc. I’ve attempted to reset my BIOS by clearing the CMOS as well as formatting my drives from other computers. The issue still persists.

When booting the same HDD and SSD from a different build, it boots fine.

My GPU still functions but the only differences from the functioning vs non-functioning build is the motherboard, CPU and RAM. So the issue is most likely with those 3.

Using the same PSU on other builds still works but it’s still possible my PSU isn’t giving enough power, even though it was working prior to installing WSL.

I can’t enter any menus to troubleshoot or reset, however, because my monitor detects a connection but doesn’t receive a signal.

I’m afraid I might be forced to buy new components until it works but I don’t have the finances to afford it at the moment.

[Xqwer]

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.

[jarppiko]

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…

[anielii]

I experienced exactly the same issue.

Windows 11 Pro,
OS build: 22621.1702
Lenovo P53

[MarkSteward2023]

We encountered this issue after failed attempts to install Ubuntu with WSL 2 and electing to uninstall WSL from the Windows Features GUI. The uninstall appeared to complete normally and prompted for the customary system restart. After the system restart, the Windows Recovery screen was displayed (see screenshot).

The OS build was completed on 11/18/2023 and was built from the Windows 11 22H2 ISO (not as an upgrade to 22H2).

11/29/2023 - Addendum: While attempting to disable & test the various virtualization settings in the bios, we discovered that pressing the F1 key at the Recovery screen to enter the Recovery Environment appeared to start the Recovery Environment but only blanked the screen before returning us to the Recovery screen.

Hardware specifics listed below.

System: Dell XPS 15 9530
OS: Microsoft Windows 11 Pro 22H2
Storage: 1TB NVME
RAM: 64GB DDR5
Firmware: Latest

[gmipf]

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.

[FelipeEstevanatto]

I had the same problem with an I7 11800H, RTX 3060, and Windows 11 Pro 23H2 while trying to install WSL2, the system worked perfectly, but when I typed only wsl --install and rebooted the system, all I got were 3 failed boots and a Recovery Blue Screen with error 0x0000225
Starting in safe mode and reverting the installation fixes the issue, I tried installing the Hyper-V Resources one by one and got that the cause of the blue screen was the 'Hyper-V of Hypervisor' resource, the other boxes of the Hyper-V didn't produce any problem, disabling Hyper-V in the BIOS also solved the bluescreen problem

PS: trying all fixes to the blue screen I could find or the commands here didn't return anything, it's only a symptom of another problem caused by the hyper-V install that somehow halts the BCD being correctly loaded, I only wanted to use WSL2

[dsalomao]

Having the same issue here.

[AAS1214]

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.

[morwen44]

Things I've tried that haven't worked:
Resetting BIOS settings
Disabling Fast boot
Disabling IOMMU
Updating drivers
Deleting AMD SDK
Enabling and disabling WSL and VMP in different other every attempt through Powershell with /norestart
It is not an option to change the UMA buffer size for my model.
Please someone help :(

OS Name Microsoft Windows 11 Home
Version 10.0.22631 Build 22631
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name MSI
System Manufacturer Micro-Star International Co., Ltd.
System Model Alpha 15 A4DEK
System Type x64-based PC
System SKU 16UK.1
Processor AMD Ryzen 7 4800H with Radeon Graphics, 2900 Mhz, 8 Core(s), 16 Logical Processor(s)
BIOS Version/Date American Megatrends Inc. E16UKAMS.101, 28-Jul-20
SMBIOS Version 3.2
Embedded Controller Version 255.255
BIOS Mode UEFI
BaseBoard Manufacturer Micro-Star International Co., Ltd.
BaseBoard Product MS-16UK
BaseBoard Version REV:1.0
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.2506"
Installed Physical Memory (RAM) 16.0 GB
Total Physical Memory 15.4 GB
Available Physical Memory 10.3 GB
Total Virtual Memory 19.3 GB
Available Virtual Memory 11.5 GB
Page File Space 3.88 GB
Page File C:\pagefile.sys
Kernel DMA Protection Off
Virtualization-based security Not enabled
Windows Defender Application Control policy Enforced
Windows Defender Application Control user mode policy Off
Device Encryption Support Elevation Required to View
Hyper-V - VM Monitor Mode Extensions Yes
Hyper-V - Second Level Address Translation Extensions Yes
Hyper-V - Virtualization Enabled in Firmware No
Hyper-V - Data Execution Protection Yes

[kusalhasintha]

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!

I turned off fast boot option from both Bios and power options now it is working fine. Thanks