{"id":38610,"date":"2025-07-09T13:26:26","date_gmt":"2025-07-09T11:26:26","guid":{"rendered":"http:\/\/159.69.82.204\/win\/?p=38610"},"modified":"2025-07-10T10:41:36","modified_gmt":"2025-07-10T08:41:36","slug":"wsus-has-synchronization-problems-july-9-2025","status":"publish","type":"post","link":"https:\/\/borncity.com\/win\/2025\/07\/09\/wsus-has-synchronization-problems-july-9-2025\/","title":{"rendered":"WSUS has synchronization problems (July 9, 2025)"},"content":{"rendered":"

\"Update\"[German<\/a>]Since July 9, 2025 (C.E.T.) German blog readers reporting, that their Windows Server Update Services (WSUS) are failing to sync with Microsoft's update servers. The endpoint from Microsoft isn't reachable and WSUS can't download the July 2025 security updates from Microsofts update server. Addendum<\/strong>: It's fixed.<\/p>\n

<\/p>\n

A first reader report via email<\/h2>\n

\"\"German blog reader Frank M. contacted me this morning (July 9, 2025 around 9:00 a.m.\u00a0 C.E.T) by e-mail at and asked whether it was just him or whether other Windows users or administrators had contacted me. He couldn't find anything on the Internet yet.<\/p>\n

Frank writes that \"since this morning it seems\" that the WSUS (Windows Server Update Services) in the company can no longer connect to the Microsoft servers. In the file:<\/p>\n

C:\\Program Files\\Update Services\\LogFiles\\SoftwareDistribution.log<\/pre>\n
he found the following error entries:<\/p>\n
Warning\r\nWsusService.40\r\nWebServiceCommunicationHelper.ProcessWebServiceProxyException\r\nProcessWebServiceProxyException found Exception was WebException. \r\nAction: Retry. \r\nException Details: System.Net.WebException: \r\nThe connection to the remote server cannot be established.\r\n ---> System.Net.Sockets.SocketException: \r\nA connection attempt failed because the remote station did not respond correctly after a certain period of time, or the established connection was faulty because the connected host did not respond 135.236.118.2<\/pre>\n
The IP address stated in the log may vary depending on which Microsoft server is contacted. In this German comment<\/a>, the IP 52.165.164.33:443 is mentioned. Due to the error, the WSUS can no longer pull any pending July 2025 updates from the Microsoft servers – administrators would at most have to try whether it is possible to import downloaded update packages.<\/p>\n
More reports from blog readers<\/h2>\n
Up to this point, I had not received any further messages. However, this does not seem to be an isolated case, as I have seen numerous reports when sharing the reader comments on the Patchday posts. On the article Patchday: Windows 10\/11 Updates (8. Juli 2025)<\/a>, German blog reader Tobi confirmed the same observation in the following comment<\/a> (translated).<\/p>\n
Are there any current problems with the WSUS sync? I have the problem with two companies, one of which was still synchronizing successfully at 00:15 today, but no longer. The other server of company #2 had the first fail at 7:03 this morning according to the log and has been stuck at 0% ever since.<\/p>\n
A colleague from another (third) company just got back to me and confirmed the problem. So I can almost turn the question into a statement: currently there is no WSUS sync …<\/p><\/blockquote>\n
This observation is confirmed in further follow-up comments – administrators write that they have had sync problems since July 9, 2025, 6:00 am. According to this comment,<\/a> a WSUS was still able to synchronize as of July 8, 2025 around 09:14 p.m. C.E.T.<\/p>\n
There are also some comments on the blog post Patchday: Windows Server-Updates (8. Juli 2025)<\/a> about WSUS synchronization problems. In the comment here<\/a>, a reader writes that the WSUS sync problems already occurred around 2:00 a.m. that night (July 9, 2025).<\/p>\n
I got also this comment<\/a> in my English blog, mention the same observation.\u00a0Is there anyone in the readership who can confirm that their WSUS was able to synchronize with the Windows servers between 4:00 am and 9:30 am on July 9, 2025 and who also has no error entries in the log file mentioned above?<\/p>\n
Microsoft released update KB5062557<\/a> for Windows Server 2019 on July 8, 2025, and writes something about an RPC fix. This update includes a security hardening change to the Microsoft RPC Netlogon protocol. This change improves security by tightening access checks for a set of remote procedure call (RPC) requests. After this update is installed, Active Directory domain controllers will no longer allow anonymous clients to invoke some RPC requests through the Netlogon RPC server. These requests are typically related to domain controller location. Certain file and print service software can be affected, including Samba. But I'm not sure, how this can affect WSUS sync.<\/p><\/blockquote>\n
Further analysis from readers<\/h2>\n
German blog reader Martin Feuerstein has contacted us by e-mail because he is also affected and also wrote that \"since this morning the WSUS synchronization from the Microsoft servers no longer seems to work\". A manual synchronization hangs forever at 0%. Martin has so far checked four servers in different environments (3x Server 2025, 1x Server 2016) and receives the same error everywhere..<\/p>\n
\"WSUS<\/p>\n
On the Server 2016 without an upstream web proxy (NAT routing only), he receives this message:<\/p>\n
WebException: Timeout for process exceeded\r\n\r\nat System.Web.Services.Protocols.WebClientProtocol.GetWebResponse(WebRequest request)\r\n\r\nat Microsoft.UpdateServices.ServerSync.ServerSyncCompressionProxy.GetWebResponse(WebRequest webRequest)\r\n\r\nat System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)\r\n\r\nat Microsoft.UpdateServices.ServerSyncWebServices.ServerSync.ServerSyncProxy.GetRevisionIdList(Cookie cookie, ServerSyncFilter filter)\r\n\r\nat Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.WebserviceGetRevisionIdList(ServerSyncFilter filter, Boolean isConfigData)\r\n\r\nat Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.ExecuteSyncProtocol(Boolean allowRedirect)<\/pre>\n
With a Windows Server 2025 without an upstream web proxy (NAT routing only), the reader receives this message:<\/p>\n
WebException: The connection to the remote server cannot be established. ---> System.Net.Sockets.SocketException: A connection attempt has failed because the remote station did not respond correctly after a certain period of time, or the established connection was faulty because the connected host did not respond 20.10.149.151:443\r\n\r\nat System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)\r\n\r\nat System.Net.HttpWebRequest.GetRequestStream()\r\n\r\nat System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)\r\n\r\nat Microsoft.UpdateServices.ServerSyncWebServices.ServerSync.ServerSyncProxy.GetRevisionIdList(Cookie cookie, ServerSyncFilter filter)\r\n\r\nat Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.WebserviceGetRevisionIdList(ServerSyncFilter filter, Boolean isConfigData)\r\n\r\nat Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.ExecuteSyncProtocol(Boolean allowRedirect)<\/pre>\n
If a web proxy is connected upstream, this message is returned (only the first line is different):<\/p>\n
WebException: The underlying connection was closed: The connection was disconnected unexpectedly.\r\nat System.Web.Services.Protocols.WebClientProtocol.GetWebResponse(WebRequest request)\r\n\r\nat Microsoft.UpdateServices.ServerSync.ServerSyncCompressionProxy.GetWebResponse(WebRequest webRequest)\r\n\r\nat System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)\r\n\r\nat Microsoft.UpdateServices.ServerSyncWebServices.ServerSync.ServerSyncProxy.GetRevisionIdList(Cookie cookie, ServerSyncFilter filter)\r\n\r\nat Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.WebserviceGetRevisionIdList(ServerSyncFilter filter, Boolean isConfigData)\r\n\r\nat Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.ExecuteSyncProtocol(Boolean allowRedirect)<\/pre>\n
Martin Feuerstein commented: \"Perhaps even more admins are affected by the problem\", which is confirmed by the above reports.<\/p>\n
An anonymous reader pointed out in a subsequent comment<\/a> that the Microsoft servers are currently unavailable for the delivery of updates.<\/p>\n
\"Website<\/p>\n
It says the sw.update.microsoft.com wasn't found, an explanation, why the endpoints are not reachable from WSUS isn't given.<\/p>\n
Microsoft is investigation the issue<\/h2>\n
Addendum:<\/strong> The last information I got was, that Microsoft is aware of the issue and they are working on a fix. In this German comment<\/a> a user wrote that he opened a ticket at Microsoft and MS is investigating. On X I saw this post<\/a> of a MS Beta engineering guy:<\/p>\n
WSUS sync issues. Teams still investigating the cause. Preliminary findings likely point towards some bad revisions might have caused the delta sync to fail triggering full sync and making catalog servers unresponsive.<\/p><\/blockquote>\n
And there is an official answer, which I have from Patchmanagement.org and which I am posting here (I haven't linked the WIxxxx IDs, because I can't access the support article due to a missing MS account:<\/p>\n
Affected platforms
\nClient Versions Message ID Originating KB Resolved KB
\nWindows 11, version 24H2 WI1112355 – –
\nWindows 11, version 23H2 WI1112356 – –
\nWindows 11, version 22H2 WI1112357 – –
\nWindows 10, version 22H2 WI1112358 – –
\nWindows 10, version 21H2 WI1112359 – –
\nWindows 10 Enterprise LTSC 2019 WI1112362 – –
\nWindows 10, version 1607 WI1112363 – –
\nWindows 10 Enterprise 2015 LTSB WI1112364 – –<\/p>\n
Server Versions Message ID Originating KB Resolved KB
\nWindows Server 2025 WI1112360 – –
\nWindows Server 2022 WI1112361 – –
\nWindows Server, version 1809 WI1112362 – –
\nWindows Server 2019 WI1112362 – –
\nWindows Server 2016 WI1112363 – –
\nWindows Server 2012 R2 WI1112365 – –
\nWindows Server 2012 WI1112366 – –<\/p>\n
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.<\/p>\n
WSUS synchronization tasks are frequently configured to occur automatically in business and enterprise environments, although manual tasks are also possible. Error logs for WSUS are usually found in the SoftwareDistribution.log file under C:\\Program Files\\Update Services\\LogFiles\\. Common messages may include text similar to \"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\"<\/p>\n
There is no workaround at this time. A problematic update revision in the storage layer has been identified as potentially causing this issue, and repairs are in progress.<\/p>\n
Next steps: We are working on a resolution and will provide more information when it is available.<\/p>\n
Addendum<\/strong>: It's fixed, see WSUS sync should work again – July 2025 issue fixed<\/a>.<\/p>\n
Similar articles:
\n<\/strong>Microsoft Security Update Summary (July 8, 2025)<\/a>
\nPatchday: Windows 10\/11 Updates (July 8,\u00a0 2025)<\/a>
\nPatchday: Windows Server-Updates (July 8,\u00a0 2025)<\/a><\/p>\n
Windows 10\/11: Preview Updates June 2025<\/a>
\n<\/a>Windows 11 24H2: Azure Virtual Desktop (AVD) App Attach fails<\/a>
\nWindows 11 24H2 June 2025 update issues: KB5060842 with wrong timestamp and Print to PDF<\/a>
\nWindows 11 24H2: June 2025 Preview Update KB5060829 triggers Firewall Events<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"
[German]Since July 9, 2025 (C.E.T.) German blog readers reporting, that their Windows Server Update Services (WSUS) are failing to sync with Microsoft's update servers. The endpoint from Microsoft isn't reachable and WSUS can't download the July 2025 security updates from … Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[463,1547,22,2],"tags":[47,195,194,569],"class_list":["post-38610","post","type-post","status-publish","format-standard","hentry","category-issue","category-software","category-update","category-windows","tag-issue","tag-update","tag-windows","tag-wsus"],"_links":{"self":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/38610","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/comments?post=38610"}],"version-history":[{"count":5,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/38610\/revisions"}],"predecessor-version":[{"id":38624,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/38610\/revisions\/38624"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/media?parent=38610"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/categories?post=38610"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/tags?post=38610"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}