Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WSL does not work after updating Windows 10 Home to Windows 11 Home #8468

Closed
1 of 2 tasks
nikusknx opened this issue Jun 2, 2022 · 1 comment
Closed
1 of 2 tasks

Comments

@nikusknx
Copy link

nikusknx commented Jun 2, 2022

Version

Microsoft Windows [version 10.0.22000.708]

WSL Version

  • WSL 2
  • WSL 1

Kernel Version

No response

Distro Version

Ubuntu

Other Software

Docker Desktop 4.0.1.0
Visual Studio Code 1.6.7.2 with Remote WSL v0.0.15

Repro Steps

Just update from Windows 10 Home edition (with a working well WSL2 Ubuntu 20.04 distrib), to Windows 11 by Windows update process.
When I try to restart WSL, nothing is working, the command WSL work only one time and after never respond (no error, just nothing append in the power shell ).
I updated the kernel too, updated wsl, disable WSL subsystem functionality and the virtual platform, restart windows and enable it again, nothing append.
I try this too #7505
but the Windows security connot start, I repair it and finally when I start the 'net start vmcompute' an error 5 append.

Expected Behavior

After an update from Windows 10 Home to Windows 11 Home WSL still working

Actual Behavior

After an update from Windows 10 Home to Windows 11 Home WSL does not work

Diagnostic Logs

WslLogs-2022-06-02_17-04-15.zip

@nikusknx
Copy link
Author

nikusknx commented Jun 3, 2022

I finally found a solution :

  • install hyper V ( with batch file)
  • turn on Hyper V in the Windows component
  • In the Windows Security :
    • Go to the App and Browser Control section.
    • Click Exploit Protection Settings.
    • Navigate to the Program Settings tab.
    • Find the Hyper-V Host Compute service by going to this path: C:\WINDOWS\System32\vmcompute.exe.
    • Select the service and click on the Edit button.
    • Find the Code Flow Guard (CFG) section and tick the Override System Settings option and activate it. (totally the opposite I found on internet)
    • Next, open Windows PowerShell with administrator privilege.
    • Execute this command: net start vmcompute : Hyper-V is working well now! No error 5 any more.
  • Reboot Windows
  • Re-Enjoy WSL ...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant