VSC in WSL crashing after WSL updates

MGX-CODING commented 7 months ago

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version (running code --version in WSL) :

1.87.0
019f4d1419fbc8219a181fab7892ebccf7ee29a2
x64

OS Version (Windows 11 with WSL, running hostnamectl & uname -r) :


Static hostname: alienware
   Icon name: computer-container
     Chassis: container
  Machine ID: def90f4983e8465484de427de287b635
     Boot ID: fe09981110ac48e3a5eb0dcbe10acefb
Virtualization: wsl
Operating System: Ubuntu 22.04.4 LTS
      Kernel: Linux 5.15.146.1-microsoft-standard-WSL2
Architecture: x86-64

5.15.146.1-microsoft-standard-WSL2

Steps to Reproduce:

1. Open Visual Studio Code in WSL mode (I do `code .` in my dev folder usually)
2. Wait for a WSL update to happen (or maybe shutdown the WSL, I did not try ?)
3. VSCode stops working

I tried closing VSCode, running `wsl --shutdown` then opening it back again, but it stops working until I restart my computer.

The error given is on every file that is opened, it reads

The editor could not be opened due to an unexpected error: ENOPRO: No file system provider found for resource 'vscode-remote://wsl%2Bubuntu/[path to my file in WSL]'

aeschli commented 7 months ago

Anything interesting in the WSL log (Command: WSL: Show Log...)?

yes, wsl --shutdown is worth a try. There haven't been any changes recently on the VS Code side.

vscodenpa commented 7 months ago

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.

Happy Coding!

microsoft / vscode

VSC in WSL crashing after WSL updates #207424