Can't use WSL2 after last update

[Cyterafle]

Windows Version

Microsoft Windows [version 10.0.19045.3693]

WSL Version

2.0.9.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

No response

Distro Version

Ubuntu 22.04.2

Other Software

No response

Repro Steps

wsl --update from an elevated terminal

Expected Behavior

Working as intended

Actual Behavior

I can't use WSL anymore

And when I try to open Ubuntu I have this error

Diagnostic Logs

No response

[github-actions]

Hi I'm an AI powered bot that finds similar issues based off the issue title.

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. Thank you!

Closed similar issues:

• Unable to update to WSL2 (#5309), similarity score: 0.92
• Can't update WSL2 (#10527), similarity score: 0.92
• Upgrade to WSL2 did not work properly (#5428), similarity score: 0.92
• WSL 2 can't update (#4576), similarity score: 0.91
• Can't launch wsl after the update (#8859), similarity score: 0.90
• Can't upgrade to WSL2 (#4717), similarity score: 0.90
• Unable to get upgraded to WSL2 (#4664), similarity score: 0.90
• cant't upgrade to WSL2 (#6376), similarity score: 0.90
• Cannot run WSL after update to 2.0.0 (#10530), similarity score: 0.90
• WSL throws error after upgrade to WSL2 (#10001), similarity score: 0.90

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

[Cyterafle]

I found a temporary fix here : #10764 (comment)
And the same issue here :
#10764

[cnjawi]

Go to the "Turn Windows features on or off" and check whether "Virtual Machine Platform" is enabled. It seemed that the latest Windows update has turned off this option. I faced similar issue and solved it this way.

[pahar0]

Accessing to WSL through a PowerShell with administrator privileges seems to fix the issue.
I used wsl.exe and not wsl, once you run WSL this way seems that you can access WSL again normally.

It worked for me, can somebody else confirm?

EDIT: I can only access to WSL through a terminal with administrator privileges.

[Cyterafle]

Accessing to WSL through a PowerShell with administrator privileges seems to fix the issue. I used wsl.exe and not wsl, once you run WSL this way seems that you can access WSL again normally.

It worked for me, can somebody else confirm?

EDIT: I can only access to WSL through a terminal with administrator privileges.

Same with me but since update GUI is laggy

[Cyterafle]

Go to the "Turn Windows features on or off" and check whether "Virtual Machine Platform" is enabled. It seemed that the latest Windows update has turned off this option. I faced similar issue and solved it this way.

I launch as an admin It works

[baiciluigi]

Same issue, can only run wsl with admin rights, everything else fails. Have to manually run it on admin.
Docker Desktop fails, but when launched with admin rights, succeeds aswell.
For now I can work like this but it needs to be fixed..

[OneBlue]

Thanks everyone for reporting this. If you hit the "element not found / ERROR_NOT_FOUND" issue, please follow this post to collect logs to help us root cause it.

[OneBlue]

Fixed in 2.0.14