10.07.2025 SOLVED/OK
Switzerland + Germany seem to work again around 10 customers we could just sync.
MS confirmed that there is a problem with a storage layer as they called it...
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
EUROPE: WSUS Server download failure – all customers since 09.07.2025 during the night
Many customers in Europe, from BSB to Enterprise, are facing an urgent problem with the Windows Update Server (WSUS).
The SYNC failed during the night of 09 July 2025, starting at different times. For example, 13 out of 15 WSUS servers at different customers within CH/DE failed to fetch the important 07-2025 0-day updates which we urgently need to roll out.
2 out of 15 servers did download the updates just fine, but we assume this happened before the problem appeared.
SRV2019 + SRV2022 German or English OS, VL, STD or ENT
There seems to be a flip-flop effect (described by some people in German forums....)
a) Either you can’t download from MS
or
b) your clients can’t connect to the WSUS
Error we see in WSUS under Sync:
WebException: Die Verbindung mit dem Remoteserver kann nicht hergestellt werden. ---> System.Net.Sockets.SocketException: Ein Verbindungsversuch ist fehlgeschlagen, da die Gegenstelle nach einer bestimmten Zeitspanne nicht richtig reagiert hat, oder die hergestellte Verbindung war fehlerhaft, da der verbundene Host nicht reagiert hat 20.10.149.151:443
bei System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)
bei System.Net.HttpWebRequest.GetRequestStream()
bei System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
bei Microsoft.UpdateServices.ServerSyncWebServices.ServerSync.ServerSyncProxy.GetRevisionIdList(Cookie cookie, ServerSyncFilter filter)
bei Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.WebserviceGetRevisionIdList(ServerSyncFilter filter, Boolean isConfigData)
bei Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.ExecuteSyncProtocol(Boolean allowRedirect)
10.07.2025 SOLVED/OK
Switzerland + Germany seem to work again around 10 customers we could just sync.
MS confirmed that there is a problem with a storage layer as they called it...
You're not the only one. Microsoft must be having issues.
One of mine is getting
InvalidOperationException: There is an error in XML document (1, 15193). ---> System.Net.WebException: The operation has timed out.
at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle, XmlDeserializationEvents events)
at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at Microsoft.UpdateServices.ServerSyncWebServices.ServerSync.ServerSyncProxy.GetUpdateData(Cookie cookie, UpdateIdentity[] updateIds)
at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.WebserviceGetUpdateData(UpdateIdentity[] updateIds, List`1 allMetadata, List`1 allFileUrls, List`1& updatesWithSecureFileData, Boolean isForConfig)
at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.GetUpdateDataInChunksAndImport(List`1 neededUpdates, List`1 allMetadata, List`1 allFileUrls, Boolean isConfigData)
at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.GetAnd