Tag Archives: WSUS
Just a short addendum: Microsoft has released some more updates on August 29, and September 5, 2017 for some software products. Here is a short overview.
[German]It’s a strange error behavior, I found recently within a German administrator website. A user reported, that all his Windows 10 V1703 clients trigger error code 0x8024000d when searching for an update. The clients are receiving updates from WSUS on … Continue reading
[German]Microsoft has released on August 25, 2017 Update KB4039871 for Windows 8.1 and Windows Server 2012 R2. But no description has been published about the purpose of this update. Now it’s clear, why this update was released.
[German]Cumulative Updates for Windows 10 Anniversary Update (V1607) and Windows Server 2016 are causing a connection error 0x8024401c in WSUS environments after install. Microsoft has now published an explanation, why this occurs and how to workaround.
[German]Microsoft has released two cumulative Updates KB4034658 and KB4034661 for Windows 10 Anniversary Update (Version 1607) in August 2017. Both updates are causing issues with WSUS, the clients are reporting error 0x8024401c during update search.
[German]It seems that Updates KB4025336 for Windows Server 2012 R2 and KB4025331 for Windows Server 2012 are breaking WSUS and SCCM. Here are a few details.
Microsoft has released on July 11, 2017 two botched updates KB4025252 and KB4025336 for Internet Explorer and Windows 8.1. Here’s what’s wrong with these updates. Addendum: It seems that an update revision fixed some install issues.
[German]Some users of my German blog informed me, that Update KB4012864 has been offered in WSUS. Here are a few details about that update.
Some strange thing happens since yesterday. A blog reader pointed it out to me in a private message. His Windows Services Update Server (WSUS) received ‘an update KB4013868’ for Windows 10, but it wasn’t available for WU. Here are a … Continue reading
Just an addendum for administrators who are not aware of WSUS issues under Windows 10 Version 1607 clients. There are issues ending in error 0xc1800118, and error 0x8024500c. But workarounds are known since months.