Windows 10: Error code: Wsl/ERROR_NOT_FOUND

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?

:)

 

WSL is blocked by SAC ?

Hello,

I'm reaching out to the community for assistance with a persistent WSL issue. Upon attempting to launch WSL, I'm encountering the following error:

WslLaunchInteractive failed with error: 0x800711e6 - System Integrity policy has been violated. Explicit denied file.

Steps Taken:

1. I have reset the Ubuntu Linux distribution.
   
2. I have uninstalled and reinstalled WSL.
   

Despite these efforts, the issue persists. I am running Windows 11 build no: 22631.2715 with WSL 2.0.9.0, and the error occurs every time I try to start WSL.

Has anyone faced a similar issue? Specifically, I'm seeking guidance on navigating the System Integrity policy that's seemingly causing the block. Any insights into how Smart App Control impacts WSL's functionality and possible configurations to mitigate this would be greatly appreciated.

Thank you in advance for your time and help.

 

WSL Remote Connection Issue with VS Code

I am trying to use WSL on VS Code, but upon opening VS Code, I keep getting the following error messages:

Unable to detect if server is already installed: Error: Failed to probe if server is already installed: code: Failed to probe if server is already installed: code: 4294967295, , Logon failure: the user has not been granted the requested logon type at this computer.

[2023-09-26 21:23:29.110] Error code: Wsl/Service/CreateInstance/CreateVm/0x80070569

I have tried addressing both error codes individually, and seemed to have some temporary success with code 4294967295 by trying several options:

• uninstall and reinstall wsl ubuntu directly from microsoft store (rather than command line)
  
• make sure my user is admin and has access
  
• disable/reenable wsl by running powershell as admin and using the lines
  
  • DISM /online /disable-feature /featurename:VirtualMachinePlatform /norestart
    
  • DISM /online /disable-feature /featurename:Microsoft-Windows-Subsystem-Linux /norestart
    
  • and then enable-feature after restarting
    
• reset winsock with netsh winsock reset
  
• set hypervisor to start automatically with bcdedit /set hypervisorlaunchtype auto
  

All of these fixes worked for about 24 hours or less, before returning to the same issue where I once again have to do one of those prompts and restart my computer. I really need a permanent solution so that I do not have to constantly restart my computer (I am using a Dell PC). Would greatly appreciate any help.

 

Error code: Wsl/Service/CreateInstance/MountVhd/ERROR FILE NOT FOUND

Hey there, Muthu Raman,

Welcome to Microsoft community.

It seems like you're having trouble with WSL and mounting your old C drive files after reinstalling OpenSUSE Tumbleweed. Here's a step-by-step guide to help you troubleshoot the issue:

1. First, ensure that WSL is enabled on your system. You can do this by running the following command in an elevated (administrator) PowerShell:
   
   
2. Make sure the OpenSUSE Tumbleweed distribution is set as the default WSL distribution. You can do this by running:
   
   
3. Check the list of installed WSL distributions using the following command:
   
   
   Look for the OpenSUSE Tumbleweed distribution in the list and make a note of its name.
   
4. If the distribution is not set to use WSL 2, update its version by running:
   
   
   Replace <DistroName> with the name of your OpenSUSE Tumbleweed distribution from the list.
   
5. Since you've reinstalled the OpenSUSE Tumbleweed distribution, your old mount point might have been removed. To remount your C drive, you can use the following command in your WSL terminal:
   
   

Unfortunately WSL is not supported on the Microsoft Answers forum. If the steps above do not solve your problem, it is more suitable for publishing on Microsoft Learn, you can click on "Ask a question", there are experts who can provide more professional solutions in that place.

Here is a link: Windows 10 - Microsoft Q&A to the forum where you can raise specific scenarios and share your idea to help solve the problem.





I'll leave that question open in case one of our amazing volunteers has ideas for you.

Thanks for your great understanding and support!

Have a nice day and stay safe!

Best regards,

Olivia | Microsoft Community Support Specialist