Microsoft admits Windows update server sync has been broken for over a week
WSUS synchronization failures have blocked enterprise Windows updates since July 13, 2026, with only new installations fully restored so far.

Key points
- Microsoft confirmed on its Windows health dashboard that Windows Server Update Services sync problems began around July 13, 2026.
- The fault affects Windows 10 version 1607 and later, plus Windows Server 2012 and later.
- A fix rolled out on Saturday restored sync for newly installed or rebuilt WSUS servers only.
- Servers already affected still can't sync, and Microsoft says a further fix is in progress.
- Microsoft has publicly acknowledged three other WSUS sync failures in roughly the past year.
Microsoft has confirmed that a core piece of plumbing used by corporate IT departments to push Windows updates has been broken for more than a week.
The tool is called Windows Server Update Services, or WSUS: a middleman that's been doing this job for nearly twenty years. Instead of every office laptop downloading updates directly from Microsoft, the company's local WSUS server fetches them once and distributes them internally.
Right now, that middleman is stuck.
What actually broke?
WSUS checks in with Microsoft's update servers once a day to grab the latest information about available patches. On affected servers, that check-in either takes far too long or times out completely. IT teams can't ship the newest Windows security fixes to staff machines through WSUS or through Microsoft's Configuration Manager tool.
Microsoft posted the acknowledgement on its Windows release health dashboard. "Organizations might experience increased synchronization times or sync operation timeouts on WSUS servers," the company wrote. "This issue began in recent days, with heightened impact observed starting July 13, 2026."
The problem hits both desktop and server Windows versions: Windows 10 version 1607 and everything newer on the desktop side, Windows Server 2012 and later on the server side.
Is there a fix yet?
Partly. Microsoft rolled out server-side changes on Saturday that stop the problem hitting fresh WSUS installations. Build a new update server today or wipe an existing one, and sync works normally.
Any WSUS server caught by the fault before Saturday is still broken. Microsoft says engineers are working on a way to strip the bad update information (the "metadata") out of those environments safely. There's no timeline for that fix.
"Synchronization times and sync operations on WSUS servers have been restored and are operating normally for new WSUS installations and rebuilds," the company added. "For WSUS servers that were previously affected, Microsoft is working on mitigation steps to help customers safely remove the affected metadata from their environments."
Why does this matter to ordinary users?
Most people never touch WSUS directly. But the machine you use at work almost certainly gets its Windows security patches through one. When WSUS stalls, those patches sit on Microsoft's servers instead of landing on your laptop, widening the window in which a known flaw can be exploited. Our 14 July report on active SharePoint attacks being exploited in the wild is a reminder of how quickly that window gets used.
For IT teams, it means a scramble. Some will switch affected devices to pull updates directly from Microsoft as a workaround. Others will rebuild their WSUS server from scratch, which the new fix does address.
A recurring pattern
As first reported by BleepingComputer, this isn't a one-off. Microsoft fixed a similar WSUS sync problem in May 2025 affecting Windows 11 22H2 and 23H2 systems, resolved another in July 2025 that blocked organisations from syncing entirely, then cleared a third in August 2025 that stopped that month's security update reaching machines through WSUS.
Three public breakages of the same pipeline before this one, all inside fourteen months. That's a pattern, not a streak of bad luck, and it's worth asking whether WSUS is receiving the maintenance attention an ageing but still-critical system needs.
What affected admins should do
If your WSUS server started misbehaving on or after July 13, check Microsoft's Windows release health dashboard for current mitigation guidance before rebuilding. Standing up a new WSUS server now? The fault shouldn't touch you. Either way, don't let patch delivery quietly slip: confirm that critical endpoints are receiving July's security updates by some route, even if that means a temporary detour around WSUS.



