PowerShell / PowerShell/Win32-OpenSSH

OpenSSH refusing to work on Local Account; works fine on Admin Account

Open
#2,352 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Area-Setup
Dominant language
No language data
Stars
8.3k
Forks
819
PR merge metrics
No merged PRs in 30d

Description

Prerequisites
  • Write a descriptive title.
  • Make sure you are able to repro it on the latest version
  • Search the existing issues.
Steps to reproduce

I'm experiencing trouble in getting SSH to work on my local user account. OpenSSH has been installed on the admin side both via the Optional Features and following the instructions on the repo here for the msi file installation. Get-Service -Name *ssh does return that the sshd and ssh-agent are running, but I'm still unable to call ssh on **BOTH **** Powershells in either local or elevated modes. I've never had issues with SSH Keygen before, and I can sure use some advice on how to get this to work.

System Specs: Windows 10 Pro, Intel Core i7 11th Gen.

Expected behavior
ssh keygen asks to create file for rsa_id
Actual behavior
ssh does not exist
Error details
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
Environment data
Name                           Value
----                           -----
PSVersion                      5.1.19041.5737
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.19041.5737
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
Version

5.1

Visuals

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the missing ssh command in Windows PowerShell 5.1 under both the local and admin accounts. Check the installation methods described in the issue and compare the Get-Service -Name *ssh results and command availability; done means the local account can invoke ssh and reach the expected key-generation prompt.

Written by the indexing model from the issue text.

Assessment

Tech stack
powershell
Domain
cli, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.