vscode-remote-release icon indicating copy to clipboard operation
vscode-remote-release copied to clipboard

WSL: Unable to open a folder in VS Code

Open Menelion opened this issue 1 month ago • 1 comments

Is there an existing issue for this bug?

  • [x] I have searched the existing open issues and found none that apply.
  • [x] If I find any issue of interest that is related or closed, I will included a link to it in this issue.

Required Troubleshooting Steps

  • [x] I have read and performed the troubleshooting steps
  • [x] I have tried both values of the remote.SSH.useLocalServer setting
  • [x] My issue was not covered in the Tips and Tricks linked from the Troubleshooting Wiki.
  • [x] I will include a complete copy of my Remote - SSH logs by running Remote-SSH: Show Log in the command palette or from View > Output in the menu bar

[Optional] Diagnose with Copilot

I did not ask the @remote-ssh participant for help

In step 2 of the troubleshooting wiki, what was the result of running the generated SSH command verbatim outside of VS Code?

I did not try step 2 of the troubleshooting steps

Remote-SSH Log

Remote-SSH Log

menelion@andre-accessmind:~/accessmind/access-ally [unhide-export-to-excel≡]!  v                                        

node:internal/modules/cjs/loader:1393                                                                                   

  throw err;                                                                                                            

  ^                                                                                                                     

                                                                                                                        

Error: Cannot find module 'C:\Users\User\AppData\Local\Programs\Microsoft VS Code Insiders\resources\app\out\cli.js'    

    at Module._resolveFilename (node:internal/modules/cjs/loader:1390:15)                                               

    at defaultResolveImpl (node:internal/modules/cjs/loader:1032:19)                                                    

    at resolveForCJSWithHooks (node:internal/modules/cjs/loader:1037:22)                                                

    at Module._load (node:internal/modules/cjs/loader:1199:37)                                                          

    at c._load (node:electron/js2c/node_init:2:17993)                                                                   

    at TracingChannel.traceSync (node:diagnostics_channel:328:14)                                                       

    at wrapModuleLoad (node:internal/modules/cjs/loader:244:24)                                                         

    at Module.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:186:5)                                 

    at node:internal/main/run_main_module:36:49 {                                                                       

  code: 'MODULE_NOT_FOUND',                                                                                             

  requireStack: []                                                                                                      

}                                                                                                                       

                                                                                                                        

Node.js v22.21.1                                                                                                        
 

Expected Behavior

I expect to open my WSL folder in VS Code with code-insiders .. I don't know when it all started, after which update.

Actual Behavior

After some update (I didn't work in WSL for like three weeks) I cannot do my usual code-insiders . to open VS Code on host. What I get is the error message I showed in the log section.

Steps To Reproduce

  1. Install Remote Development pack.
  2. Make sure you have a working WSL distro, like Ubuntu.
  3. Clone a repo in WSL.
  4. Try to do code-insiders . from that folder.

Anything else?

It used to work absolutely fine before. I can connect from Windows to that folder with the remote WSL command, but I'd really like to bring back the ability to open folders from WSL as I'm very much used to do it.

Menelion avatar Nov 26 '25 01:11 Menelion

Please try with the latest insiders and please provide here the error message that you see.

aeschli avatar Dec 09 '25 13:12 aeschli

Seems to have fixed by itself in the latest build, closing for now. Thanks.

Menelion avatar Dec 11 '25 12:12 Menelion