Microsoft has acknowledged a significant disruption affecting Windows Server Update Services (WSUS), which is hindering organizations from syncing with Microsoft Update and rolling out the latest Windows updates. This tool is essential for businesses, enabling them to efficiently manage and distribute updates across their networked computers.
Details of the Synchronization Issue
WSUS is designed to synchronize with Microsoft Update servers on a daily basis, downloading the most recent metadata regarding available updates. Administrators have the flexibility to adjust this frequency according to their operational needs. However, reports from Windows administrators indicate that synchronization has been compromised since last night. Many have encountered error messages in their event logs, including “A connection attempt failed” and .NET errors indicating that “The operation has timed out” during their sync attempts.
A thread on Reddit captures the frustration of users experiencing these issues: “Is anyone having synchronization issues with their WSUS server? I started having issues last night and still can’t get it to sync this morning. There does appear to be one sync that was successful in the middle of the night, but none since.”
Interestingly, some admins noted that synchronization resumed briefly around 12:30 am ET this morning, but the relief was short-lived.
Microsoft’s Response
In response to the growing concerns, Microsoft has confirmed the synchronization problem within WSUS, attributing it to a “problematic update revision in the storage layer.” This complication means that devices attempting to sync updates via WSUS may struggle to complete the process, resulting in an inability to deploy updates through WSUS or Configuration Manager. A Microsoft advisory shared with BleepingComputer elaborated on the issue, stating:
“Devices trying to synchronize updates from Microsoft Updates using Windows Server for Update Services (WSUS) might fail to complete the synchronization process. As a result, updates cannot be deployed using WSUS or Configuration Manager.”
For businesses relying on WSUS, synchronization tasks are typically set to occur automatically, although manual syncs are also an option. Administrators can find error logs in the SoftwareDistribution.log file located at C:Program FilesUpdate ServicesLogFiles. Common error messages include phrases like “Unable to connect to the remote server” and “A connection attempt failed because the connected party did not properly respond after a period of time.”
Currently, Microsoft has stated that there are no workarounds available and is actively working on a resolution to restore full functionality to WSUS.
