2017-08 update for Windows 10 Anniversary Update ("1607") breaks WSUS

NOTE: Microsoft appear to have resolved this issue with a new update for Windows 10, see here for details.

We've discovered that (now listed as a known issue in the Windows 10 Update History) the most recent update to Windows 10 Anniversary Update (2017-08) causes machines that are connected to WSUS to fail to find subsequent updates, returning the error:

There were some problems installing updates, but we’ll try again later. If you keep seeing this and want to search the web or contact support for information, this may help: (0x8024401c)

The issue is called out as a Known Issue of "WSUS servers will exhibit increased CPU, memory, and network utilization when Windows Update clients perform their first scan after installing KB4034658 ("Microsoft is investigating this issue and will provide an update as soon as possible."). The only mitigation against this that we can see, at the moment is to:

  1. Revoke approval for the update in WSUS
  2. Go to Control Panel > Programs and Features > Installed Updates
  3. Uninstall the update described as "Security Update for Microoft Windows (KB4034658)" (yes - it says "Security Update", even though the Update History describes it as "This update includes quality improvements")
  4. Reboot (this took 10 minutes here)

Windows should once again be able to check-in with WSUS; hopefully Microsoft will be able to push out a change to WSUS to resolve this as having to remove the update on PCs to get them talking to WSUS again would be quite an unpleasant solution!

There are two other issues listed for this update, both of them around Updates / Update History, so it definitely looks like something in the Windows Update area went a big wrong in this cumulative update!

Update: After doing this you may see Windows Update fail with an error of 0x80244010, according to a post on the WSUS support team blog, re-trying should resolve this though multiple re-tries may be needed. I only needed one! Also, after rolling back, I was back to 14393.0 (i.e. the initial release of Windows 10 Anniversary Update) so do make sure that you re-update after rolling back!

About Rob

I've been interested in computing since the day my Dad purchased his first business PC (an Amstrad PC 1640 for anyone interested) which introduced me to MS-DOS batch programming and BASIC.

My skillset has matured somewhat since then, which you'll probably see from the posts here. You can read a bit more about me on the about page of the site, or check out some of the other posts on my areas of interest.

No Comments

Add a Comment