Microsoft explains WSUS error at 0x8024401c Windows 10 V1607 Published August 20, 2017 Primarily by guenni Windows Server 2016 Windows 10 Anniversary Update Cumulative Updates (V1607) Windows Server 2016 causes some connection errors under 0x8024401c WSUS circumstances after installation. Now Microsoft has posted a great explanation on why this is happening and how to get around it.
They actually got error 8024401c when we checked for updates (after updating WSUS). At first we thought it was related to the WSUS update, but found that most of our communities hadn’t been updated in a long time. So some of us moved on to defining the nature of the client.
04/05/2019 09:21:08.3073335 1364 1836 The WebServices web call service failed, hr is 8024401f. I also think the element is the key to the specific error, the issue is related to I IS issue with multiple domain bindings.
How to synchronize WSUS to another WSUS server?
If you chose to sync caused by another WSUS server, specify the remote computer name and port on that server that it will use to communicate with the upstream server. To use SSL, clear the Use SSL when syncing updated kitchen information check box. Computer systems use port 443 for synchronization.
Is the WSUS endpoint still providing status reports to WSUS?
Endpoints continue to report status to WSUS. The behavior persists across reboots, deleting the software distribution file, and uninstalling/reinstalling the last few months of Win10 Cumulative Updates. All post-creator computers, updated, have been working fine for months.
Do you need WSUS client to use WSUS server?
To set up your infrastructure, client workstations must have a compatible version installed for automatic updates. The updated programs, called WSUS clients, allow clients to download knowledge from a WSUS server instead of using all Windows updates.
Ermias is a tech writer with a passion for helping people solve Windows problems. He loves to write and share his knowledge with others in the hope that they can benefit from it. He’s been writing about technology and software since he was in college, and has been an avid Microsoft fan ever since he first used Windows 95.