Microsoft has confirmed a comprehensive issue in Windows Server Update Services (WSUS) that prevents organizations from sinking with microsoft updates and deploying the latest Windows updates.
Windows Server Update Services (WSUS) is a Microsoft product that allows businesses to manage and distribute Windows updates to the computer within its network.
By default, Wsus synchronizes the Microsoft update server once a day, when it downloads the latest metadata on the available Windows update. If they want in settings, they can change frequency.
Since last night, Windows Admins has reported that the WSUS synchronization has broken, showing the “a connection effort fail” or .NET errors with the event logs said, “Operation has been time,” when the sync was attempted.
“Does anyone have synchronization issues with their WSUs servers? I have started having issues last night and still cannot get it to sink this morning. A sink appears that has been successful in the middle of the night, but no one,” one reads. , Redit topic About the issue.
Admins report that the synchronization started at ET at around 12:30 am today.
Microsoft has now confirmed the synchronization problem in the WSUs and said that he has identified the “problematic update modification in the storage layer” that is causing the problem.
The devices trying to synchronize the Microsoft update using the Windows Server for Update Services (WSUS) may fail to complete the synchronization process. As a result, the update cannot be deployed using the WSUS or configuration manager, “reads the Microsoft advisory shared with bleepingcomputer.
“WSUS synchronization work is often configured to be automatically in business and enterprise environment, although manual work is also possible. Error logs for WSUs are usually found under C: \ update services \ Logfiles \ Logfiles \.
“General messages may include the same text similar to” unable to connect to remote server “and” an attempt of a connection failed because the Connected party did not respond properly after the period of time “
Microsoft says that there are no workarounds at this time and they are working on a fix.