Microsoft has acknowledged WSUS synchronization issues, and some clients are showing no status or failing to pull approved updates. Is anyone else seeing this, and have the documented fixes helped?
Anyone else seeing WSUS clients stop reporting or pulling approved updates?
Asked by
8d~sparehinge_417
Answers
One reported fix was to complete all three steps in Microsoft's article, reindex SUSDB, run the Server Cleanup Wizard, and reset IIS. After that, reboot a test client and check for updates again to see whether it can scan successfully.
There is also an older documented fix specifically for error 0x80244007, so the error code may help narrow down which guidance to check.
Reply to this answer
For WSUS using Windows Internal Database, one reported implementation used the SQLServer PowerShell module to run the database work without installing SQL Server Management Studio on every server. That approach was reported to help, though it may not resolve every case.
Reply to this answer
Another thing to check is the WSUS web.config. Increasing maxCachedUpdates and maxInstalledPrerequisites was reported to help get updates into WSUS where Windows 11 clients were hitting 0x80244007. That is a different reported change from the database cleanup steps, so check the applicable guidance before changing those settings.
Reply to this answer
Add your answer
Answers are reviewed before publication.
u720+coaster_5:
The steps haven't worked in every report. Some clients were still returning errors ending in 007 and 010 after scripts were run.