Microsoft shares manual fix for WSUS sync delays and timeouts

· Original article ↗

Summary

Microsoft shared manual cleanup steps for existing WSUS servers affected by metadata buildup that caused sync delays and Windows Update scan failures or timeouts, disrupting update deployment through WSUS and Configuration Manager.

Key points

  • The issue affects Windows 10 version 1607 and later, and Windows Server 2012 and later.
  • A buildup of publishing metadata caused long synchronization times or timeouts, preventing update deployment through WSUS and Configuration Manager.
  • Microsoft's service-side mitigation restored normal synchronization for newly installed or rebuilt WSUS servers.
  • For existing affected servers, Microsoft recommends backing up each SUSDB database, running a cleanup query against all SUSDB databases, and restoring MaxXMLPerRequest to its default.
  • After cleanup, the first Windows Update scan may take longer; subsequent scans should return to normal timing.
  • Microsoft also recommends reindexing SUSDB, running the WSUS Server Cleanup Wizard, and restarting IIS or recycling the WsusPool application pool.

Article Details

Event Type
Microsoft disclosed a WSUS synchronization issue and provided manual mitigation steps.
Impact
Affected WSUS servers may experience failed or timed-out Windows Update scans, preventing organizations from deploying updates through WSUS or Configuration Manager. The issue affects Windows 10 version 1607 and later and Windows Server 2012 and later. Microsoft said manual metadata cleanup can restore normal synchronization; the first scan afterward may take longer.

Vendors

Products

Related Articles