Vscode-remote-release: Access is denied. But can connect if change client computer

[yuan-commits]

• VSCode Version: 1.43.2
• Local OS Version: win10
• Remote OS Version: Ubuntu 14.04
• Remote Extension/Connection Type: SSH

The log is as belows:
[15:32:47.842] Log Level: 2
[15:32:47.849] [email protected]
[15:32:47.849] win32 x64
[15:32:47.851] SSH Resolver called for "ssh-remote+stcgpu-19", attempt 1
[15:32:47.851] SSH Resolver called for host: stcgpu-19
[15:32:47.851] Setting up SSH remote "stcgpu-19"
[15:32:47.875] Using commit id "0ba0ca52957102ca3527cf479571617f0de6ed50" and quality "stable" for server
[15:32:47.875] Install and start server if needed
[15:32:49.797] Checking ssh with "ssh -V"
[15:32:49.849] > OpenSSH_for_Windows_7.7p1, LibreSSL 2.6.5
[15:32:49.851] Running script with connection command: ssh -T -D 60197 stcgpu-19 bash
[15:32:49.853] Terminal shell path: C:\windows\System32\cmd.exe
[15:32:49.932] >

]0;C:\windows\System32\cmd.exe
[15:32:49.932] Got some output, clearing connection timeout
[15:32:49.939] >

[15:32:49.948] > Access is denied.

[15:32:50.855] "install" terminal command done
[15:32:50.857] Install terminal quit with output: Access is denied.
[15:32:50.857] Received install output: Access is denied.
[15:32:50.858] Stopped parsing output early. Remaining text: Access is denied.
[15:32:50.859] Failed to parse remote port from server output
[15:32:50.860] Resolver error:
[15:32:50.867] ------

• Debug *
• I can ssh via cmd command: ssh stcgpu-19
• "echo uname | ssh stcgpu-19 bash":
  C:\Users\yuanz>echo uname | ssh stcgpu-19 bash
  uname: extra operand ‘\r’
  Try 'uname --help' for more information.

[yuan-commits]

The problem occured after a recent windows 10 update. I removed the c:\users\username.ssh folder and regenerate ssh key. It works now.

[divanikus]

Facing the same problem after upgrade to 2004:

[18:25:26.085] SSH Resolver called for host: [email protected]
[18:25:26.085] Setting up SSH remote "192.168.0.2"
[18:25:26.126] Using commit id "5763d909d5f12fe19f215cbfdd29a91c0fa9208a" and quality "stable" for server
[18:25:26.127] Install and start server if needed
[18:25:26.137] Checking ssh with "C:\Windows\System32\OpenSSH\ssh.exe -V"
[18:25:26.165] > OpenSSH_for_Windows_7.7p1, LibreSSL 2.6.5
[18:25:26.167] Running script with connection command: "C:\Windows\System32\OpenSSH\ssh.exe" -T -D 65047 [email protected] bash
[18:25:26.169] Terminal shell path: C:\WINDOWS\System32\cmd.exe
[18:25:26.343] > Access is denied.
> ]0;C:\WINDOWS\System32\cmd.exe
[18:25:26.343] Got some output, clearing connection timeout
[18:25:26.897] "install" terminal command done
[18:25:26.897] Install terminal quit with output: ]0;C:\WINDOWS\System32\cmd.exe
[18:25:26.897] Received install output: ]0;C:\WINDOWS\System32\cmd.exe
[18:25:26.898] Stopped parsing output early. Remaining text: ]0;C:\WINDOWS\System32\cmd.exe
[18:25:26.898] Failed to parse remote port from server output
[18:25:26.898] Resolver error: 
[18:25:26.900] ------

Tryed to remove .ssh folder, no luck. I can ssh to the host via cmd without any problem.

[divanikus]

Seems to be a some kind of permission problem. I can connect to remote hosts if I run VSCode as Admin. To be clear, I'm using 1.45.1, system-wide setup. Remote SSH is 0.51.0.
I have also tryed to reinstall VSCode from scratch, but it didn't helped. Everything was working as a mere user on Windows 1909

UPD. So, it was my fault, my $TEMP variable was poiting to a location where a mere user cannot write.

[SoyYoRafa]

I experienced this as well in 10 year old Windows profile (currently running Win 10 though). My user was missing TEMP and Visual Studio Code was getting the system TEMP (C:\WINDOWS\TEMP).

[joltcan]

I experienced this as well in 10 year old Windows profile (currently running Win 10 though). My user was missing TEMP and Visual Studio Code was getting the system TEMP (C:\WINDOWS\TEMP).

Thanks for saving me! I changed it to a tmp dir in the user profile and that worked! \o/

[Xtigyro]

Changing the $TEMP Windows env var saved me as well - thank you, @divanikus and @SoyYoRafa!

[bamurtaugh]

Thanks for the discussion here! Since it looks like the issue was resolved, going to close the thread. But if folks have any other questions or feedback, please feel free to let us know. Thank you!