WSL does not work in 27823, and rollback to 27818 will keep this problem

[realcwj]

Windows Version

Microsoft Windows [Version 10.0.27823.1000]

WSL Version

2.4.13.0

Are you using WSL 1 or WSL 2?

• [x] WSL 2
• [ ] WSL 1

Kernel Version

no response

Distro Version

1. Ubuntu 2. Ubuntu 20.04 LTS

Other Software

No response

Repro Steps

1. Install Windows 27818
2. Setup WSL and Ubuntu, and make sure they work normally
3. Update to 27823
4. Open Ubuntu

Expected Behavior

work normally

Actual Behavior

got no response

After maybe 30 minutes, ubuntu reports an error: Wsl/Service/CreateInstance/CreateVm/HCS/HCS_E_SERVICE_NOT_AVAILABLE

Diagnostic Logs

Windows Insider Feedback Hub: https://aka.ms/AAv9urw

WSL Logs: WslLogs-2025-03-31_09-29-26.zip

Similar problem: #12735

[github-actions[bot]]

Diagnostic information

Detected appx version: 2.4.13.0

[luqiuzhi]

same here

[furopi]

I'm experiencing the same issue. When I open a shell and wait a long time I get the error code below. Please fix! Wsl/Service/CreateInstance/CreateVm/HCS/HCS_E_SERVICE_NOT_AVAILABLE

[zackmuc]

Same here in the german version of Windows 11 canary insider. In the past a return to the previous version worked but this time also not working.

[realcwj]

UPDATE:

I finally find a method to [TEMPORARILY] fix this problem: turn off the Hyper-V option, and it works.

Thoughts: Turn off this option will turn on Hyper-V, and turn on this option will turn off Hyper-V?? WTF

NOTE: This is only tested in the 27823 version.

And for anyone who meets this problem in the future: this is not a right solution.

@zackmuc @furopi @luqiuzhi

[zackmuc]

yeah it turns back to WSL1 i think @realcwj can you check the services list and make a screenshot of Hyper-V Services and their running status?

[OneBlue]

I finally find a method to [TEMPORARILY] fix this problem: turn off the Hyper-V option, and it works.

Interesting. I wonder if your machine got into a weird state. Do you get any error if you run: sfc /scannow ?

[realcwj]

yeah it turns back to WSL1 i think @realcwj can you check the services list and make a screenshot of Hyper-V Services and their running status?

[realcwj]

I finally find a method to [TEMPORARILY] fix this problem: turn off the Hyper-V option, and it works.

Interesting. I wonder if your machine got into a weird state. Do you get any error if you run: sfc /scannow ?

Nothing...

[rucomcode]

Thoughts: Turn off this option will turn on Hyper-V, and turn on this option will turn off Hyper-V?? WTF

Thanks so much for sharing this workaround! It’s really frustrating when the system behaves so counterintuitively — turning off Hyper-V to actually enable it feels like a paradox. Your discovery is super helpful for those stuck with this issue right now. Hopefully Microsoft will fix this soon, but until then, your solution is a lifesaver. Appreciate you taking the time to dig into this and share it with the community!

[damnkiwi6120]

I found that Hyper-V related services are disabled. Simply re-enable them might recover the functionality. ("might" because there are too many of them. I have no idea which is the right one to enable, and I don't want to simply enable them all. I instead go to the route disable the Hyper-V in optional features and re-enable it.)

[OneBlue]

I finally find a method to [TEMPORARILY] fix this problem: turn off the Hyper-V option, and it works.

Interesting. I wonder if your machine got into a weird state. Do you get any error if you run: sfc /scannow ?

Nothing...

Interesting. Could you share /dumps of WSL processes when things are "stuck" while Hyper-V is enabled ?

[microsoft-github-policy-service[bot]]

Hello! Could you please provide logs and process dumps to help us better diagnose your issue?

To collect WSL logs and dumps, 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 -Dump

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

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

Click here for more info on logging

Thank you!

[microsoft-github-policy-service[bot]]

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

Thank you!