starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

The term 'ssh' is not recognized even though openSSH is installed #12546

New Issue
Closed
opened 2026-01-31 03:18:27 +00:00 by claunia · 4 comments
claunia commented 2026-01-31 03:18:27 +00:00
Owner
Copy Link

Originally created by @zaidajani on GitHub (Feb 13, 2021).

Environment

ssh : The term 'ssh' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the
spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ ssh
+ ~~~
    + CategoryInfo          : ObjectNotFound: (ssh:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

Steps to reproduce

  1. Open windows terminal or PowerShell
  2. run ssh

Expected behavior

As I have OpenSSH installed, The behavior should happen to be like this.

usage: ssh [-46AaCfGgKkMNnqsTtVvXxYy] [-B bind_interface]
           [-b bind_address] [-c cipher_spec] [-D [bind_address:]port]
           [-E log_file] [-e escape_char] [-F configfile] [-I pkcs11]
           [-i identity_file] [-J [user@]host[:port]] [-L address]
           [-l login_name] [-m mac_spec] [-O ctl_cmd] [-o option] [-p port]
           [-Q query_option] [-R address] [-S ctl_path] [-W host:port]
           [-w local_tun[:remote_tun]] destination [command]

Actual behavior

Even though I have OpenSSH installed on my pc, It shows this error which is unexpected. In my windows terminal ( PowerShell ) This annoying error comes not allowing me to connect to my server on the cloud.

Originally created by @zaidajani on GitHub (Feb 13, 2021). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- This bug tracker is monitored by the Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```powershell ssh : The term 'ssh' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. At line:1 char:1 + ssh + ~~~ + CategoryInfo : ObjectNotFound: (ssh:String) [], CommandNotFoundException + FullyQualifiedErrorId : CommandNotFoundException ``` # Steps to reproduce 1. Open windows terminal or PowerShell 2. run `ssh` # Expected behavior As I have OpenSSH installed, The behavior should happen to be like this. ```powershell usage: ssh [-46AaCfGgKkMNnqsTtVvXxYy] [-B bind_interface] [-b bind_address] [-c cipher_spec] [-D [bind_address:]port] [-E log_file] [-e escape_char] [-F configfile] [-I pkcs11] [-i identity_file] [-J [user@]host[:port]] [-L address] [-l login_name] [-m mac_spec] [-O ctl_cmd] [-o option] [-p port] [-Q query_option] [-R address] [-S ctl_path] [-W host:port] [-w local_tun[:remote_tun]] destination [command] ``` # Actual behavior Even though I have OpenSSH installed on my pc, It shows this error which is unexpected. In my windows terminal ( `PowerShell` ) This annoying error comes not allowing me to connect to my server on the cloud.
claunia added the Resolution-ExternalNeeds-Tag-Fix labels 2026-01-31 03:18:28 +00:00
claunia commented 2026-01-31 03:18:30 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Feb 13, 2021):

I suspect you're using 32-bit (x86) PowerShell. Can you run gci env:/PROCESSOR*?

@DHowett commented on GitHub (Feb 13, 2021): I suspect you're using 32-bit (x86) PowerShell. Can you run `gci env:/PROCESSOR*`?
claunia commented 2026-01-31 03:18:30 +00:00
Author
Owner
Copy Link

@zaidajani commented on GitHub (Feb 14, 2021):

It says I use x86 PROCESSOR_ARCHITECTURE

PS C:\Users\Admin> gci env:/PROCESSOR*

Name                           Value
----                           -----
PROCESSOR_ARCHITEW6432         AMD64
PROCESSOR_REVISION             1801
PROCESSOR_LEVEL                23
PROCESSOR_IDENTIFIER           AMD64 Family 23 Model 24 Stepping 1, AuthenticAMD
PROCESSOR_ARCHITECTURE         x86


PS C:\Users\Admin>
@zaidajani commented on GitHub (Feb 14, 2021): It says I use x86 `PROCESSOR_ARCHITECTURE` ```powershell PS C:\Users\Admin> gci env:/PROCESSOR* Name Value ---- ----- PROCESSOR_ARCHITEW6432 AMD64 PROCESSOR_REVISION 1801 PROCESSOR_LEVEL 23 PROCESSOR_IDENTIFIER AMD64 Family 23 Model 24 Stepping 1, AuthenticAMD PROCESSOR_ARCHITECTURE x86 PS C:\Users\Admin> ```
claunia commented 2026-01-31 03:18:30 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Feb 14, 2021):

This is a bug with how Windows automatically registers OpenSSH. Because it lives in “system32”, a folder which 32-bit processes redirect, it cannot be found by looking in the PATH. You should prefer to use a native/64-bit shell unless you have a specific reason not to, or use the full redirected path to OpenSSH, c:\windows\sysnative\openssh\ssh.exe.

@DHowett commented on GitHub (Feb 14, 2021): This is a bug with how Windows automatically registers OpenSSH. Because it lives in “system32”, a folder which 32-bit processes _redirect_, it cannot be found by looking in the PATH. You should prefer to use a native/64-bit shell unless you have a specific reason not to, or use the full _redirected_ path to OpenSSH, `c:\windows\sysnative\openssh\ssh.exe`.
claunia commented 2026-01-31 03:18:31 +00:00
Author
Owner
Copy Link

@mehmetakifaksoy commented on GitHub (Sep 9, 2023):

If you are using openssh for windows you can go to this path and after run on the cmd on administrator It works!

@mehmetakifaksoy commented on GitHub (Sep 9, 2023): If you are using openssh for windows you can go to this path and after run on the cmd on administrator It works!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Needs-Tag-Fix Resolution-External
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#12546
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?