Domain client's OpenSSH Server install is stuck and then fails

Question

Machine is on a domain. WSUS is on DC.
Doesn't that imply that it knows where the WSUS is?

Is there another reason?

Theres a workaround on github that I'd rather not use. Does anyway know how to make this go?

Answer 1

Hi @kaylabar ,

Could we check the OpenSSH Server is updated via WSUS? If so, there might be some troubles during the installation. Microsoft delivers features on demand bypassing WSUS, so we do not get them via the internal update server. We could allow Windows to load optional features directly from Microsoft Update via group policy. Kindly find it under Computer Configuration > Policies > Administrative Templates > System.

At the same time, We could ensure that neither the setting "Do not connect to Windows Update Internet locations" nor "Remove access to use all Windows Update features" is in effect.

Here is the article we could refer to:
https://4sysops.com/archives/installing-openssh-on-windows-10-1803-and-higher-and-server-2019/#problems-with-wsus
Note: the above links are not from MS, and just for your reference.

---

If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.