Remote SSH Version 1.0.25 unable to connect to Rmote server

Describe the Bug

Over the last two days, the Remote-SSH extension was updated from version 1.0.23 to 1.0.25. I am unable to connect to my Linux remote host. I am getting an error “Connection to Cursor server failed: spawn UNKNOWN”. If I downgrade to 1.0.23 everything works fine.

Steps to Reproduce

  1. Make sure there is an entry for Linux server in .ssh/config
  2. Try connecting to the entry using the Remote Explorer

Expected Behavior

Cursor should connect to the remote host.

Screenshots / Screen Recordings

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.4.5 (user setup)
VSCode Version: 1.99.3
Commit: af58d92614edb1f72bdd756615d131bf8dfa5290
Date: 2025-08-13T02:08:56.371Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.19045

Additional Information

Logs:
[info] Resolving ssh remote authority ‘fw’ (Unparsed ‘ssh-remote+7b22686f73744e616d65223a226677227d’) (attempt #1)
[info] SSH askpass server listening on port 52749
[debug] hostname: fw, remote platform map: {“Dev”:“linux”,“rhels”:“linux”,“fw”:“linux”}
[info] Using configured platform linux for remote host fw
[debug] hostname: fw, remote server install map: {}
[info] Using askpass script: c:\Users\Swarup.Sengupta.cursor\extensions\anysphere.remote-ssh-1.0.25\dist\scripts\launchSSHAskpass.bat with javascript file c:\Users\Swarup.Sengupta.cursor\extensions\anysphere.remote-ssh-1.0.25\dist\scripts\sshAskClient.js. Askpass handle: 52749
[info] Launching SSH server via shell with command: Get-Content -Raw “C:\Users\SWARUP~1.SEN\AppData\Local\Temp\cursor_remote_install_b6308918-4031-4061-9643-315decd6a7d6.sh” | ssh -T -D 52750 fw bash --login -c bash
[info] Establishing SSH connection: Get-Content -Raw “C:\Users\SWARUP~1.SEN\AppData\Local\Temp\cursor_remote_install_b6308918-4031-4061-9643-315decd6a7d6.sh” | ssh -T -D 52750 fw bash --login -c bash
[error] Error installing server: [Error: spawn UNKNOWN
at ChildProcess.spawn (node:internal/child_process:420:11)
at Object.spawn (node:child_process:777:9)
at t.SSHConnectionFactory.execHandler (c:\Users\Swarup.Sengupta.cursor\extensions\anysphere.remote-ssh-1.0.25\dist\main.js:1:28095)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async t.installCodeServer (c:\Users\Swarup.Sengupta.cursor\extensions\anysphere.remote-ssh-1.0.25\dist\main.js:1:91366)
at async c:\Users\Swarup.Sengupta.cursor\extensions\anysphere.remote-ssh-1.0.25\dist\main.js:1:146441] {
errno: -4094,
code: ‘UNKNOWN’,
syscall: ‘spawn’
}
[info] Deleting local script C:\Users\SWARUP~1.SEN\AppData\Local\Temp\cursor_remote_install_b6308918-4031-4061-9643-315decd6a7d6.sh
[error] Error resolving SSH authority [Error: spawn UNKNOWN
at ChildProcess.spawn (node:internal/child_process:420:11)
at Object.spawn (node:child_process:777:9)
at t.SSHConnectionFactory.execHandler (c:\Users\Swarup.Sengupta.cursor\extensions\anysphere.remote-ssh-1.0.25\dist\main.js:1:28095)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async t.installCodeServer (c:\Users\Swarup.Sengupta.cursor\extensions\anysphere.remote-ssh-1.0.25\dist\main.js:1:91366)
at async c:\Users\Swarup.Sengupta.cursor\extensions\anysphere.remote-ssh-1.0.25\dist\main.js:1:146441] {
errno: -4094,
code: ‘UNKNOWN’,
syscall: ‘spawn’
}

Does this stop you from using Cursor

Yes - Cursor is unusable

Ok, I tried 1.0.24 too, but same issue, 1.0.23 was the last version that could connect to the remote SSH.

Ok, A little digging on my part looks like this is a PowerShell issue. I am using a machine, on which powershell is administratively disabled, so the command “Get-Content -Raw “C:\Users\SWARUP~1.SEN\AppData\Local\Temp\cursor_remote_install_b6308918-4031-4061-9643-315decd6a7d6.sh” | ssh -T -D 52750 fw bash --login -c bash” fails as powershell cannot be invoked. I guess earlier version either used cmd or a way to fallback to cmd if powershell isn’t available. Can you please look into the same, if powershell is not available, then fallback to using cmd?

I have temporarily downloaded the pwsh from github and changed the powershell invocation in the remote-ssh dist.js from powershell to pwsh to get it to work. But it would be nice it can use cmd instead of powershell, or at least have a fallback path to cmd. Since may laptops specially those centrally administered have their powershell turned off.

Hey team, any update on this?

Hi @swarupsengupta2007, thanks for the big report. We are looking at switching to cmd or trying that as a fallback.

Hi @swarupsengupta2007, we just released version 1.0.27 of the extension which restored the cmd shell behavior. Could you try upgrading to the latest version of the extension?

Hey, Thanks @ravirahman. Just updated to the latest version of remote ssh extension, and everything looks good.

1 Like

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.