I went ahead earlier today and approved the updates for deployment, however I noticed an issue on multiple Windows 10 machines, where the Windows Update client would get stuck on Downloading updates 0% status.I checked a bunch of things, but noticed that it simply couldn’t download the updates from my WSUS server.Assigning clients to different target WSUS groups is based on labels on the client itself (labels are set by a GPO or a direct registry modification).This kind of client association to the WSUS groups is called client side targeting.(Also make note that if this server was configured as a WSUS client of itself, you will need to reconfigure it to be an AU client again. S., MCITP: EA, MCDBA, MCSA Principal/CTO, Onsite Technology Solutions, Houston, Texas Microsoft MVP - Software Distribution (2005-2011) My MVP Profile: Garvin My Blog: If any of the above resources were still present, reboot the server again.
The registry error you encountered after the installation/uninstallaton of the console was likely there all along, and merely deleting the HKLM\Software\Microsoft\Update Services key (which I suspect was the registry error, and is described in the Sticky Post at the top of this forums listing, which was taken directly from this thread, in fact), may well have fixed it all. S., MCITP: EA, MCDBA, MCSA Principal/CTO, Onsite Technology Solutions, Houston, Texas Microsoft MVP - Software Distribution (2005-2011) My MVP Profile:
Garvin My Blog: And, in fact, from my observations, very few WSUS installation failures are actually attributed to WID corruption issues.
The WSUS uninstaller does not uninstall the Windows Internal Database feature, so a WSUS uninstallation issue is, by definition, related to some other cause.
Well, it’s October 18th 2017 and the Fall Creators update (Feature update to Windows 10, version 1709) is now available for download.
In my particular environment, I use WSUS to deploy and manage updates.