Error code: Wsl/ERROR_NOT_FOUND

Question

Windows installed the update KB5032339 and WSL 2.0.9.0, and since then, I can not access WSL.

The error was the one indicated in the title of the question. I cannot work, because all of my work depends on WSL and I need docker desktop, which also depends on WSL.

I searched everywhere; it seems that I am not the only one with this problem. I tried uninstalling WSL and installing an older version, but the problem remains.

How can I solve this, or is Microsoft going to release an update to fix this problem?

Answer 1

Hello, frcgoncalves

Welcome to Microsoft Community.

Windows installed the update KB5032339 and WSL 2.0.9.0, and since then, I can not access WSL.

So far there haven't been any known issues in this update, as stated here:

November 14, 2023-KB5032339 Cumulative Update for .NET Framework 3.5, 4.8 and 4.8.1 for Windows 10 Version 22H2 - Microsoft Support

.

Also, based on the official description, this update is mainly related to .NET Framework, but WSL doesn't need to use .NET Framework unless you're doing .NET development within WSL. So, in my opinion, this update shouldn't affect WSL. Of course, if you're not sure, you can uninstall this update and see if it makes a difference, then you can confirm whether or not this update is causing the problem.

I searched everywhere; it seems that I am not the only one with this problem.

I couldn't find a similar question in Microsoft Community, at least not recently in the English community. Maybe you saw similar problems out of Microsoft? Anyway, if you can't solve the problem, I suggest giving feedback on GitHub, where there is an official channel for feedback.

Issues · microsoft/WSL · GitHub

Microsoft Community isn't the best place for discussing WSL-related issues, and WSL developers don't usually pay attention to questions in Microsoft Community.

Yuhao Li

Microsoft Community Technical Support

Answer 2

This issue was already reported on Git Hub a few days ago, but there is still no response and no solution.

So, if the developers do not pay attention to questions in Microsoft Community but also do not solve them when they are posted in Git Hub, what should we do while waiting for someone to fix this problem? Isn't WSL part of Microsoft?

Answer 3

I have the same problem.

λ wsl

Element not found.

Error code: Wsl/ERROR_NOT_FOUND

λ wsl -v

WSL: 2.0.9.0

kernel: 5.15.133.1-1

WSLg: 1.0.59

MSRDC: 1.2.4677

Direct3D: 1.611.1-81528511

DXCore: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp

Windows: 10.0.19045.3693

Here's the github issue link: https://github.com/microsoft/WSL/issues/10767

Answer 4

Whether or not this issue will be fixed depends entirely on the developers. User opinions and my suggestions won't be the deciding factors.

Also, it's not guaranteed that the issue can be fixed immediately just because you want it fixed now. Developers receive numerous reports of various technical issues every day, and they have to prioritize and assess the urgency of each one. Even if they prioritize it, it may still take many days to resolve the problem because technical issues can vary in difficulty.

I saw that someone in this issue was able to solve the problem:

https://github.com/microsoft/WSL/issues/10767.

You can try their solution and see if it helps. It might solve the problem or serve as a worakround. However, it's important to note that this issue is indeed not something that Microsoft Community can resolve. Microsoft officially recommends discussing it on GitHub for further assistance:

Get started with Linux using WSL | Microsoft Learn

Answer 5

I have the same issue.

WSL version: 2.0.9.0

Kernel version: 5.15.133.1-1

WSLg version: 1.0.59

MSRDC version: 1.2.4677

Direct3D version: 1.611.1-81528511

DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp

Windows version: 10.0.19045.3693

No amount of uninstalling and reinstalling fix the issue.