You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Make sure you are able to repro it on the latest version
Search the existing issues.
Steps to reproduce
Start-Service sshd not working.
Is it a bug or just me?
Expected behavior
PS>Start-Service sshd<operation success message>
Actual behavior
PS>Start-Service sshd
Error details
Start-Service : Service 'OpenSSH SSH Server (sshd)' cannot be started due to the following error: Caice on computer '.'.At line:1 char:14+ Start-Service <<<< sshd + CategoryInfo : OpenError: (System.ServiceProcess.ServiceController:ServiceController) ServiceCommandException + FullyQualifiedErrorId : CouldNotStartService,Microsoft.PowerShell.Commands.StartServiceCommand
Environment data
PS>$PSVersionTable
Name Value
---------
CLRVersion 2.0.50727.5420
BuildVersion 6.1.7601.17514
PSVersion 2.0
WSManStackVersion 2.0
PSCompatibleVersions {1.0,2.0}
SerializationVersion 1.1.0.1
PSRemotingProtocolVersion 2.1
Thanks for the report. This looks like a real Windows sshd service startup failure, but the current details are not enough to reproduce or route it confidently yet.
The server OS version and whether this is Windows 7 / Windows Server 2008 R2 or another Windows build.
The client OS version, if a client connection is involved.
The complete, untruncated Start-Service sshd error text. The current error appears cut off after Ca / ice on computer '.'.
Relevant sshd logs or Windows Event Viewer entries from the failed startup, plus any reproduction details such as how OpenSSH was installed and whether sshd.exe exists at the configured service path.
For maintainers
Windows-specific vs. upstream: This appears Windows-specific because it involves the Windows sshd service managed by Start-Service, so if confirmed the fix would likely belong in PowerShell/openssh-portable. Confidence: medium, pending full logs.
Reproducibility: Not reproducible from the report as written. It includes a service-start command and partial PowerShell environment output, but the service error is truncated, the OS is not stated explicitly, and there are no sshd/Event Viewer logs.
Copilot-fix suitability: Maybe, but only after logs identify a concrete failure path. A service startup/configuration bug could be localized; a platform support or installer/environment issue may not be.
Likely area:Area-sshd, because the failure is starting the Windows OpenSSH SSH Server service.
Related issues: Exact-message searches mainly found this issue. #1676 is closed and also mentions sshd as a Windows service, but it describes service behavior after startup rather than this service-start failure, so it does not look like a duplicate based on current evidence.
Activity
github-actions commentedon Oct 17, 2026
Thanks for the report. This looks like a real Windows
sshdservice startup failure, but the current details are not enough to reproduce or route it confidently yet.Information needed from the author
Please add the following details:
Start-Service sshderror text. The current error appears cut off afterCa/ice on computer '.'.sshdlogs or Windows Event Viewer entries from the failed startup, plus any reproduction details such as how OpenSSH was installed and whethersshd.exeexists at the configured service path.For maintainers
Windows-specific vs. upstream: This appears Windows-specific because it involves the Windows
sshdservice managed byStart-Service, so if confirmed the fix would likely belong inPowerShell/openssh-portable. Confidence: medium, pending full logs.Reproducibility: Not reproducible from the report as written. It includes a service-start command and partial PowerShell environment output, but the service error is truncated, the OS is not stated explicitly, and there are no
sshd/Event Viewer logs.Copilot-fix suitability: Maybe, but only after logs identify a concrete failure path. A service startup/configuration bug could be localized; a platform support or installer/environment issue may not be.
Likely area:
Area-sshd, because the failure is starting the Windows OpenSSH SSH Server service.Related issues: Exact-message searches mainly found this issue. #1676 is closed and also mentions
sshdas a Windows service, but it describes service behavior after startup rather than this service-start failure, so it does not look like a duplicate based on current evidence.Add this agentic workflows to your repo
To install this agentic workflow, run