Skip to content

Cannot use OpenSSH in Windows 11 #6414

@p7th0n

Description

@p7th0n

Pre-submit Checks

Describe the bug

ssh doesn't work from my Windows 11 machine

To reproduce

When run from Warp PowerShell

ssh user@host

ssh: The term 'ssh' is not recognized as a name of a cmdlet, function, script file, or executable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

Get-ChildItem c:\Windows\System32\OpenSSH\

Get-ChildItem: Cannot find path 'C:\Windows\System32\OpenSSH\' because it does not exist.

run from Windows terminal PowerShell


which ssh

CommandType     Name                                               Version    Source
-----------     ----                                               -------    ------
Application     ssh.exe                                            9.5.4.1    C:\WINDOWS\System32\OpenSSH\ssh.exe

Get-ChildItem C:\Windows\System32\OpenSSH\

    Directory: C:\Windows\System32\OpenSSH

Mode                 LastWriteTime         Length Name
----                 -------------         ------ ----
-a---           3/31/2024 12:08 PM          18934 LICENSE.txt
-a---           3/31/2024 12:08 PM          36008 NOTICE.txt
-a---            4/8/2025  3:32 PM         430080 scp.exe
-a---            4/8/2025  3:32 PM         457728 sftp.exe
-a---            4/8/2025  3:32 PM         602624 ssh-add.exe
-a---            4/8/2025  3:32 PM         553984 ssh-agent.exe
-a---            4/8/2025  3:32 PM         861184 ssh-keygen.exe
-a---            4/8/2025  3:32 PM         661504 ssh-keyscan.exe
-a---            4/8/2025  3:32 PM         514048 ssh-pkcs11-helper.exe
-a---            4/8/2025  3:32 PM         653312 ssh-sk-helper.exe
-a---            4/8/2025  3:32 PM        1246208 ssh.exe

Expected behavior

ssh to remote hosts

Screenshots, videos, and logs

No response

Operating system (OS)

Windows

Operating system and version

Windows 11

Shell Version

No response

Current Warp version

v0.2025.04.30.08.11.stable_01

Regression

No, this bug or issue has existed throughout my experience using Warp

Recent working Warp date

No response

Additional context

No response

Does this block you from using Warp daily?

No

Is this an issue only in Warp?

Yes, I confirmed that this only happens in Warp, not other terminals.

Warp Internal (ignore): linear-label:b9d78064-c89e-4973-b153-5178a31ee54e

None

Metadata

Metadata

Assignees

No one assigned

    Labels

    BUGBugs, Hangs, Crash, and Freezes

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions