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

system commands not working #13244

New Issue
Closed
opened 2026-01-31 03:37:38 +00:00 by claunia · 5 comments
claunia commented 2026-01-31 03:37:38 +00:00
Owner
Copy Link

Originally created by @pauliee99 on GitHub (Mar 30, 2021).

Hello, am having issues running commands in the Windows Terminal app located in C:\Windows\System32 with cmd and powershell (ssh, ipconfig, e.t.c.) and i get the following error:

ssh : The term 'ssh' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the s
pelling 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

The directory C:\Windows\System32 is located in the environment variables and they are working properly in powershell and cmd applications.

Originally created by @pauliee99 on GitHub (Mar 30, 2021). Hello, am having issues running commands in the Windows Terminal app located in ```C:\Windows\System32``` with cmd and powershell (ssh, ipconfig, e.t.c.) and i get the following error: ``` ssh : The term 'ssh' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the s pelling 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 ``` The directory ```C:\Windows\System32``` is located in the environment variables and they are working properly in powershell and cmd applications.
claunia added the Needs-TriageNeeds-Tag-FixNeeds-Attention labels 2026-01-31 03:37:38 +00:00
claunia commented 2026-01-31 03:37:39 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Mar 30, 2021):

I suspect you are using a 32-bit powershell or 32-bit cmd. Can you run...

powershell

gci env:/PROCESSOR_*

cmd

set | findstr PROCESSOR_

Thanks

@DHowett commented on GitHub (Mar 30, 2021): I suspect you are using a 32-bit powershell or 32-bit cmd. Can you run... ### powershell ```powershell gci env:/PROCESSOR_* ``` ### cmd ```cmd set | findstr PROCESSOR_ ``` Thanks
claunia commented 2026-01-31 03:37:39 +00:00
Author
Owner
Copy Link

@pauliee99 commented on GitHub (Mar 30, 2021):

Thank you for your response @DHowett,
the result i got was:

Name                           Value
----                           -----
PROCESSOR_IDENTIFIER           AMD64 Family 21 Model 2 Stepping 0, AuthenticAMD
PROCESSOR_ARCHITECTURE         AMD64
PROCESSOR_REVISION             0200
PROCESSOR_LEVEL                21
@pauliee99 commented on GitHub (Mar 30, 2021): Thank you for your response @DHowett, the result i got was: ``` Name Value ---- ----- PROCESSOR_IDENTIFIER AMD64 Family 21 Model 2 Stepping 0, AuthenticAMD PROCESSOR_ARCHITECTURE AMD64 PROCESSOR_REVISION 0200 PROCESSOR_LEVEL 21 ```
claunia commented 2026-01-31 03:37:40 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Mar 30, 2021):

Very curious indeed. Do you have C:\Windows\System32\OpenSSH on your PATH?

@DHowett commented on GitHub (Mar 30, 2021): Very curious indeed. Do you have `C:\Windows\System32\OpenSSH` on your `PATH`?
claunia commented 2026-01-31 03:37:40 +00:00
Author
Owner
Copy Link

@pauliee99 commented on GitHub (Mar 30, 2021):

I just did and it looks like it fixed everything, thank you very much i appreciate your answer, i was looking for an answer for quite some time!

@pauliee99 commented on GitHub (Mar 30, 2021): I just did and it looks like it fixed everything, thank you very much i appreciate your answer, i was looking for an answer for quite some time!
claunia commented 2026-01-31 03:37:40 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Mar 30, 2021):

You're welcome! Sometimes we see systems where it never got updated -- usually when the system was running a much older version of Windows 10.

I'm glad it's fixed.

@DHowett commented on GitHub (Mar 30, 2021): You're welcome! Sometimes we see systems where it never got updated -- usually when the system was running a much older version of Windows 10. I'm glad it's fixed.
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-Attention Needs-Tag-Fix Needs-Triage
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#13244
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?