A widespread problem with Windows Server Update Services (WSUS) that stops businesses from delivering the most recent Windows updates and syncing with Microsoft Update has been confirmed by Microsoft.
A Microsoft product called Windows Server Update Services (WSUS) enables companies to control and distribute Windows updates to machines connected to their network.
When WSUS gets the most recent metadata for available Windows updates, it automatically synchronizes with Microsoft Update servers once daily. In the settings, administrators have the option to alter the frequency.
With event logs indicating "A connection attempt failed" or.NET errors stating "The operation has timed out," when syncs were attempted, Windows administrators have been reporting that WSUS synchronization is failing since last night.
Does anyone's WSUS server have synchronization problems? I started experiencing problems last night, and this morning I'm still having trouble getting it to sync. A Reddit article concerning the problem states, "There does seem to have been one sync that was successful in the middle of the night, but none since."
According to administrators, the synchronization started at around 12:30 am ET this morning.
Microsoft claimed to have found a "problematic update revision in the storage layer" that is the root of the synchronization issue in Windows Server Update System (WSUS).
Devices attempting to use Windows Server for Update Services (WSUS) to synchronize updates from Microsoft Updates may not be able to finish the synchronization procedure. Consequently, updates cannot be implemented through Configuration Manager or WSUS," a Microsoft advice obtained by BleepingComputer states.
In commercial and enterprise settings, WSUS synchronization tasks are often set up to run automatically, while manual tasks are also feasible. The SoftwareDistribution.log file located in C:\Program Files\Update Services\LogFiles\ is often where WSUS error logs may be discovered.
Text like "Unable to connect to the remote server" and "A connection attempt failed because the connected party did not correctly answer after a period of time" are examples of common notifications.
Microsoft claims that they are working on a solution and that there are currently no workarounds.