I absolutely hate this day. As usual, I booted up my laptop, opened VSCode and WSL, only to be greeted by the strange Wsl/ERROR_FILE_NOT_FOUND error today.

The Windows Subsystem for Linux (WSL) would always mysteriously stop working, though it could be easily recovered with some reconfiguration, but not this time.

I had both a Debian based WSL1 for native file operations and an Ubuntu 22 based WSL2 for running services in Modular installed, but when I tried to launch them directly with the commands ubuntu and debian, they both started throwing 0x80070002 errors. I attempted fixes from Google and Github to no avail.

Almost every command in wsl.exe was throwing Wsl/ERROR_FILE_NOT_FOUND exceptions, WSL services kept stopping, and all the reset methods were practically useless.

I tried:

• Using netsh winsock reset
• Uninstalling the WSL kernel and reinstalling it
• Using wsl --unregister
• Clicking "Repair" or "Reset" for WSL in Settings
• Handling the .wslconfig file
• Enabling/Disabling Hyper-V
• And every other thing I could find
  None of them worked, it was so frustrating. The previous day, Microsoft had pushed me a patch on the Beta channel, KB5032283, I installed it and shut down. And then this happened after booting up today.

Finally, just uninstalling the two Windows Subsystem for Linux apps from the app list, and reinstalling them from the Microsoft Store got my WSL working again.

The endless stream of terrible bugs from Microsoft keeps amazing me, last time a major error happened, I even had to convert a WSL2 instance to WSL1 and back to WSL2 to fix it. It's unbearable.

🙏🙏🙏

Since you've made it this far, sharing this article on your favorite social media network would be highly appreciated 💖! For feedback, please ping me on Github.