[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.
In business environments Windows Server may be used to distribute updates within a company’s network using WSUS (Windows Server Update Services). But Microsoft failed 2017 several times and released updates, that broke WSUS (see my blog post July 2017 Updates KB4025336/KB4025331 breaks WSUS).
Windows 10 Version 1607: KB4034658 & KB4034661
In August 2017 Microsoft released two cumulative Updates KB4034658 (August 8, 2017) and KB4034661 (August am 16, 2017) for Windows 10 Anniversary Update (Version 1607). Both updates are causing WSUS issues, the clients are reporting error 0x8024401c during update search.
I received some reader comments and has mentioned this issue within my blog posts Issues after Microsoft’s August Updates and Windows 10 V1607: Update KB4034661 (August 16, 2017).
After installing the updates mentioned above on Windows 10 clients, and restarting the system, the clients are reporting error 0x8024401c during update search. I found on August 13, 2017 a blog post WSUS SUP causes high CPU and clients fail updates scan mentions a high CPU and RAM load and posts some hint to fix this issue.
Robert Wray has published on August 15, 2017 an article 2017-08 update for Windows 10 Anniversary Update („1607“) breaks WSUS addressing this issue and mentions update KB4034658 a how to uninstall this package.
Microsoft has confirmed this bug
Writing the blog post Windows 10 V1607: Update KB4034661 (August 16, 2017) I noticed, that Microsoft is aware of this WSUS issue. The known issue section of KB4034658 and KB4034661 for Windows 10 Anniversary Update (Version 1607) says.
WSUS servers will exhibit increased CPU, memory, and network utilization when Windows Update clients perform their first scan after installing KB4034658.
Microsoft investigates the issue and will publish details as soon as possible. Until a fix is available, the only workaround is blocking these updates in WSUS.
Microsoft explains the behavior
Just a short addendum. Microsoft has posted an article High CPU/High Memory in WSUS following Update Tuesdays, explaining, what’s going on under the hood.