"Organizations might experience increased synchronization times or sync operation timeouts on WSUS servers. This issue began in recent days, with heightened impact observed starting July 13, 2026," Microsoft said in a Windows health dashboard update.
Microsoft health dashboard: what happened and when
Microsoft confirmed a known issue that has disrupted Windows Server Update Services (WSUS) synchronization for more than a week. The company says the problem began "in recent days" and that the impact notably increased beginning July 13, 2026. According to the update, affected WSUS servers have seen broken synchronization processes that prevent administrators from deploying the latest Windows updates through WSUS or Configuration Manager.
How WSUS sync failures affect deployments and Configuration Manager
WSUS is designed to let IT administrators schedule and distribute updates from a single local server instead of having every endpoint contact Microsoft's update servers directly. By default, WSUS syncs with Microsoft Update servers once a day to download metadata for available Windows updates. On affected servers, that synchronization is broken: operations can time out or take much longer, and administrators "will not be able to deploy the latest Windows updates via WSUS or Configuration Manager," Microsoft said.
Platforms explicitly identified as affected
Microsoft's advisory specifies the impact spans both client and server platforms. The company named Windows 10, version 1607 and later, and Windows Server 2012 and later, as being within the scope of the issue. That means organizations using those versions—and relying on WSUS as their update distribution mechanism—may see delayed or failed update deliveries until synchronization is restored.
Mitigations deployed and the work that remains
Microsoft rolled out mitigation measures on Saturday to stop the sync-time and operation issues from affecting newly installed or rebuilt WSUS servers. The company reports that "Synchronization times and sync operations on WSUS servers have been restored and are operating normally for new WSUS installations and rebuilds." For servers that were previously affected, Microsoft is "working on mitigation steps to help customers safely remove the affected metadata from their environments."
The advisory does not specify a timeline for those mitigation steps or the precise procedures customers should follow; it does confirm an active effort to remove problematic metadata from already deployed WSUS instances so those installations can resume normal operations.
Recent history of WSUS incidents
Microsoft's statement places this disruption in a string of WSUS-related incidents over the prior year. One year ago, in May, Microsoft fixed a similar issue after enterprise customers reported WSUS errors when updating Windows 11 22H2/23H2 systems. The company addressed another WSUS sync problem in July 2025 that prevented organizations from syncing with Microsoft Update. One month after that, Microsoft resolved a separate issue that blocked the August 2025 security update from being delivered via WSUS.
What this means for enterprise admins, technologists, and end users
- Enterprise administrators and procurement leaders: Organizations that depend on WSUS or Configuration Manager should verify whether their servers are new installs or rebuilds (which Microsoft's Saturday mitigations cover) and, for previously affected servers, expect and plan for metadata-removal steps once Microsoft publishes them.
- Technologists and security teams: Teams must account for delays in distributing critical updates where WSUS synchronization has failed. Where possible, remediation paths include using mitigated new builds or rebuilds of WSUS to restore normal sync behavior; Microsoft is working on safe metadata-removal mitigations for other installations.
- End users and the general public: Because affected WSUS servers "will not be able to deploy the latest Windows updates via WSUS or Configuration Manager," users in managed enterprise environments may experience delays receiving updates until their administrators apply rebuilds, new installations, or the forthcoming metadata-removal mitigations.
Microsoft's mitigations have restored sync operations for new WSUS installs and rebuilds, but the company continues to work on steps to cleanse affected metadata from previously impacted servers. For organizations that cannot rebuild immediately, the timing and content of those mitigation steps will determine how quickly normal update distribution can resume.
