WSL Install results with stop code: HYPERVISOR_ERROR

[ColAlexsanders]

Whenever I try to install Ubuntu through both powershell and the microsoft store, I get a BSOD error with stop code HYPERVISOR_ERROR when I try to run Ubuntu after install.

What I have done:

• enabled and disabled virtual machine platform, windows subsystem for linux, and windows hypervisor platform (my system doesn't show 'Hyper-V') features
• run 'DISM.exe /Online /Cleanup-image /Restorehealth'
• bios updated
• drivers updated
• ran windows memory diagnostic
• enable virtualization in bios

I do have hyper virtualization installed and enabled because in virtualbox, I can still run VMs using Hyper-V acceleration. I had both ubuntu and docker installed through wsl, and they were working fine. The error came after I edited some folder permissions and ownership while configuring emacs, and I changed ownership to my user account instead of trusted installer for powershell.

Sidenote: The same BSOD would appear when I start docker desktop. I've tried uninstalling that, but my computer still thinks it's on the system for some reason. I tried running the uninstall command in the terminal as well (start /w "" "Docker Desktop Installer.exe" uninstall), but that didn't work.

I've browsed all over the internet for a solution and nothing has helped me which is why I'm writing this. I've attached my memdump file from my most recent crash. I can still use my computer just fine, I just can't use WSL currently. I have attached my minidump files.

edit: removed dump links

[github-actions]

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The script will output the path of the log file once done.

If this is a networking issue, please use collect-networking-logs.ps1, following the instructions here

Once completed please upload the output files to this Github issue.

Click here for more info on logging
If you choose to email these logs instead of attaching to the bug, please send them to [email protected] with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

View similar issues

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it!

Open similar issues:

• WSL2 gives HYPERVISOR_ERROR BSOD but WSL1 works okay (#11508), similarity score: 0.72
• Blue Screen of Death (#8459), similarity score: 0.72
• Getting BSOD saying dxgkrnl.sys failed after upgrade to wsl 2.0.9.0 (#10750), similarity score: 0.72

Closed similar issues:

• Windows BSOD / hangs on boot when using WSL2 (#5783), similarity score: 0.73
• WSL2 causing "bluescreen" on W11 (#7168), similarity score: 0.72

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

[ColAlexsanders]

acl.txt
bcdedit.txt
HKCU.txt
HKLM.txt
optional-components.txt
P9NP.txt
windows-version.txt
Winsock2.txt
wpr.txt
wslservice.txt
wslsupport-impl.txt

(I can't run the install ubuntu command and have it get saved because the BSOD forces me to turn my PC off, making me unable to use any other apps while it's open)

[ColAlexsanders]

UPDATE: I switch to WSL 1 and it installed fine, but when I tried to open "WSL2 gives HYPERVISOR_ERROR BSOD but WSL1 works okay (#11508), similarity score: 0.72", it took me to a deleted issue

[OneBlue]

Thank you for reporting this @ColAlexsanders. Could you follow the Important: Reporting BSODs and Security issues
section to report the BSOD ?

When you do that, please specify that the dumps are for the 'WSL team'

[ColAlexsanders]

Hey @OneBlue , thank you for responding! I just sent my dump file up to address [email protected].