Wsl/ERROR_NOT_FOUND after installing Windows updates

[target-san]

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

WslLogs-2023-11-17_09-50-38.zip

[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!

Open similar issues:

• WSL failed to start after update Windows (#4939), similarity score: 0.89
• WSL not working after windows update (#10185), similarity score: 0.89
• Latest Windows update uninstalled WSL (#9355), similarity score: 0.87
• WSL doesnt start after Windows Update (#5722), similarity score: 0.87
• WSL Not working after windows 11 updates (#7379), similarity score: 0.86

Closed similar issues:

• WSL stopped working after latest windows update (#8133), similarity score: 0.87
• Windows Update Destroys WSL System (#1195), similarity score: 0.86
• Windows updates disabled - Can't upgrade to WSL 2 (#6132), similarity score: 0.85
• Can't update WSL2 (#10527), similarity score: 0.85
• Unable to update to WSL2 (#5309), similarity score: 0.85

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

[CHADT10]

Try this #10764 (comment)

[target-san]

Didn't work. I erased service record, uninstalled WSL components from installer. Now I cannot even install it, installer simply closes immediately. WSL CLI returns same error.

[target-san]

wsl --install ends with 0x80070490
Is there some proper way to clean WSL completely and then reinstall from scratch?
Or some comprehensive registry of WSL errors?

[target-san]

After wsl --update and installing required kernel update MSI, I'm down to square one, Wsl/ERROR_NOT_FOUND

[OneBlue]

@target-san: I'm not seeing anything in the logs you shared.

Can you try to manually install the latest release and see if that helps ?

Please share /logs again if a failed startup if that doesn't help

[target-san]

@OneBlue
wsl.2.0.9.0.x64.log.zip
Well, according to log installation succeeded 🤷
As of logs, I'm getting issue with importing AppX module . Was present before reinstall, just didn't notice. Need to solve before I get real logs. Honestly it's extremely frustrating how MS products tend to hide error information at all cost.

[target-san]

Finally logs:
WslLogs-2023-11-18_07-54-11.zip

[osavoskin]

@target-san

I have just run into this issue myself. Spent half a day trying to fix it. Nothing has worked except for:

• reinstall of the windows components: virtual machines support & wsl support
• uninstall all the wsl updates
• wsl --install --no-distribution
• now wsl --status at least produces the report, but requires an update
• run wsl --update --inbox (only the kernel)

Now you should be able to run your containers, at least. But any update to wsl (up to 2.0.9) will break it again, unfortunately.

** I guess the windows components reinstallation step is excessive and can be skipped. Try to just uninstall all the wsl updates and update the kernel (--inbox) to make it work.

[pahar0]

Launching WSL from a terminal with administrator privileges works for me. #10788 (comment)

[target-san]

@pahar0 Yup, thanks. Works for me too. At least for now.
Though it's interesting what causes this requirement out of thin air.

[osavoskin]

Launching WSL from a terminal with administrator privileges works for me. #10788 (comment)

Hm, does not work for me, for some reason..