WSL: Wsl/ERROR_NOT_FOUND after installing Windows updates
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
N/A
Distro Version
N/A
Other Software
No response
Repro Steps
Install Windows updates (possibly KB5032189)
Expected Behavior
Wsl works
Actual Behavior
Error:
Element not found.
Error code: Wsl/ERROR_NOT_FOUND
Diagnostic Logs
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Reactions: 5
- Comments: 42 (3 by maintainers)
Thank you @pahar0. This confirms our theory: There is an old WSL installation that’s conflicting with the latest package.
Can you try to:
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\PackagedCom\ClassIndex\{A9B7A1B9-0671-405C-95F1-E0612CB4CE7E}(You can use the .reg you just captured as backup if needed)
Issue solved deleting
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\PackagedCom\ClassIndex\{A9B7A1B9-0671-405C-95F1-E0612CB4CE7E}in regedit. Thank you guys @OneBlue @benhillisI added a dash to the old keys. That worked for me.
Launching WSL from a terminal with administrator privileges works for me. https://github.com/microsoft/WSL/issues/10788#issuecomment-1817734924
Thank for confirming @pahar0. So this confirms that the issue is this registry key being left over by previous install. We’ll update our install logic to automatically remove it in the next update.
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!
Open similar issues:
Closed similar issues:
You can give me feedback by thumbs upping or thumbs downing this comment.
Can confirm installing version 2.0.11 (pre-release) works in resolving this issue of not being able to access WSL without elevated privileges.
I found a solution in: here. You can try it
wsl --updatewas unable to pick it up. Had to manually installmsifrom the release.Issue solved deleting
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\PackagedCom\ClassIndex\{A9B7A1B9-0671-405C-95F1-E0612CB4CE7E}Thanks 😃
Fixed with https://github.com/microsoft/WSL/releases/tag/2.0.11.
THANK YOUUUUUUU. Deleting the reg. key also solved all WSL update problems for me.
Thanks for the confirmation! @OneBlue is working on a fix now.
Deleting the key worked for me. Now to sort out the display issue on wslg which seems to have a weird overlay on top of GUI apps.
Thanks for all the help on this folks. This is a strange MSIX / packaged COM issue that we have not seen in internal testing. I know this issue is causing you all a lot of pain, and I’m hopeful we will have a fix to push out before turkey day.
Thank you @bsatts and @pahar0. We have a theory now. To validate it, could you please use regedit to export the content of
HKLM\Software\Classes\PackagedComand share the .reg file with us ?Thanks everyone for reporting this.
To give some clarity: there are two issues with WSL 2.0.9:
Wsl/CallMSI/E_ABORTWe’ve identified the issue and working on a fix. You can workaround it by enabling the WSL optional component and rebooting
Wsl/ERROR_NOT_FOUNDWe’ve not been able to reproduce the issue yet. We’re investigating but to root cause it we’d need COM logs.
If you can reproduce the issue, please follow these instructions to collect logs:
wpr -start ComTrace.wprp -filemodewsl.echo echo test)wpr -stop logs.etllogs.etlon this issueSame issue, but I have also noticed that wslg.exe is missing and I can’t seem to get it back no matter what I do