-
Notifications
You must be signed in to change notification settings - Fork 783
v9.4.0.0p1-Beta installation hangs #2161
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Same situation, happens through install on Winget too. Windows 11 Pro 10.0.22621 |
I tried running manually the PowerShell script here (https://github.com/PowerShell/openssh-portable/blob/latestw_all/contrib/win32/openssh/install-sshd.ps1) and it fixed the situation somehow, even though I still have an error at the end of the install process.
Here is the install log from Winget
|
Thanks for confirming that running the install script works, @Murazaki. @user8446, can you confirm the |
Yes just SYSTEM & admin have write access |
Ok, thanks. What's the error number when trying to start sshd? |
v9.4.0 doesn't even start at all:
v9.2.0 does start:
Debug info isn't a help here as neither version starts with v9.4.0:
v9.2.0:
|
Try running https://github.com/PowerShell/Win32-OpenSSH/wiki/Troubleshooting-Steps |
|
Ok, that's what I'd expect to see. Could you try running the I'd also try starting directly with |
Ok I put |
It should permit read access for authenticated users - were those types of accounts removed? |
I ran the script again and it stripped permissions again. I just manually add read permissions back to have access to the logs. I haven't had time to look at the PS code in the script. Also just adding that when My sshd server is up and running as expected but happy to help test anything like re-running the MSI installer before closing? |
Ok, I think this can be opened as a separate issue to fine tune the permissions of the install script.
Yeah, that's the expected behavior unfortunately. I didn't expect it to hang though - I'm not sure if that's due to using
Great! If you feel like retrying the MSI installer with the current folder permissions, that would confirm it installs as expected. If you don't want to mess with your current setup, that's fine, too - I think we're good to close. |
I just ran the installer and all is well, the permissions persisted. Thank you very much helping out @tgauth ! |
@Uj947nXmRqV2nRaWshKtHzTvckUUpD can you confirm that only the Administrators group and the SYSTEM account have owner/write permissions on the |
i must mention that in the past i used this commands as admin: and later: |
Thanks for confirming - I just deleted the comment so the previous edits of the screenshot aren't accessible. Does running install-sshd.ps1 ask to remove permissions on any other files within |
could you please give me some more detailed instructions to do so ? where do i get that script and how do i run it? |
The script can be downloaded with a .zip release - https://github.com/PowerShell/Win32-OpenSSH/releases/download/v9.4.0.0p1-Beta/OpenSSH-Win64.zip or from https://github.com/PowerShell/openssh-portable/blob/latestw_all/contrib/win32/openssh/install-sshd.ps1. Put the script in the same directory as the SSHD install - Invoke the script from PowerShell - |
after running the script as admin i was able to update openssh via winget. thank you ! shouldn't this fix be added during install/update time? |
agreed - any chance you can pinpoint what permissions were changed by the script that ultimately permitted SSHD to start? |
I replaced with <USER> in the install log. looks like moduli and logs folders |
I still had the same error on v9.5.0.0p1-Beta, and I can confirm that running |
Uh oh!
There was an error while loading. Please reload this page.
Hi,
Just reporting that the v9.4.0.0p1-Beta that was just released hangs on installation.
The issue is
sshd.exe
which fails to start.Rolling back to v9.2.2.0p1-Beta or if I roll back just
sshd.exe
to v9.2.0 works as expected andsshd.exe
starts.Version
v9.4.0.0p1-Beta
The text was updated successfully, but these errors were encountered: