Newsletter Archives

  • Yet another reason why you should avoid Automatic Update – KB 4039396

    If you’re running Win10 Anniversary Update, Microsoft released a fix yesterday that’ll clean everything up — as long as you didn’t install the original cumulative update, which was released on August 8.

    Computerworld Woody on Windows.

  • New cumulative update for Win10 1607 fixes bugs in the old one

    I think.

    MS released KB 4039396 a few hours ago, bringing Win10 Anniversary Update (version 1607) up to Build 14393.1670.

    According to the KB entry:

    • Addressed issue where Update History and hidden updates are lost and a full scan for updates happens after installing OS Updates 14393.1532 through 14393.1613, including KB4034658. Installing this update will not restore past update history or hidden updates for users who have already installed the listed updates. However, this current update will address this issue for users who have not yet installed them.
    • Addressed issue with WSUS update metadata processing that can cause some clients to time out with a 0x8024401c error.

    Those are two important bugs in the old cumulative updates for 1607.

    I hope you’ve been following along here and haven’t installed the August update for 1607 as yet. Can anybody out there confirm that installing this cumulative update, and not the earlier ones, will maintain Update History? I’m away from my test machine and would appreciate any confirmation…

  • Microsoft offers solution to the KB 4034658 Update Server red-lining problem

    On August 11, in Computerworld, I mentioned a disturbing phenomenon: the problem-plagued August cumulative update for Windows 10 Anniversary Update (version 1607), KB 4034658, was causing WSUS servers to redline.

    On August 16, I posted a short article about the bug, pointing to an analysis by Scott Williams.

    Microsoft has finally fessed up to the problem – and posted a complex workaround. Jarrett Renshaw, on the Technet blog, now says:

    Recently, we’ve seen an increase in the number of high CPU/High Memory usage problems with WSUS, including WSUS in a System Center Configuration Manager environment – these have mostly corresponded with Update Tuesdays.

    Microsoft support has determined that the issue is driven primarily by the Windows 10 1607 updates, for example KB4022723, KB4022715, KB4025339, etc. See here for the list of Windows 10 1607 updates.

    Microsoft is also aware of a known issue with KB4034658 that will cause Windows 10 1607 clients to run a full scan after install – Microsoft is investigating and the latest information is available here.

    These updates have large metadata payloads for the dependent (child) packages because they roll up a large number of binaries. Windows 10, versions 1507 (Windows 10 RTM) and 1511 updates can also cause this, though to a lesser extent.  Windows 10, version 1703 is still recent enough that the metadata is not that large yet (but will continue to grow).

    For those of you trying to push cumulative updates for 1607 through an Update Server, you’ve seen the problem. It’s refreshing for Microsoft to admit the problem exists — ten days after the patch went out.

    Renshaw offers a complex solution. Definitely something you want to keep in your back pocket, if you’re trying to run WSUS or SCCM with Win10 machines.

  • Another fallout from the wiped out Update History

    Scott Williams has a detailed view of another Update History wipeout due to this month’s Win10 1607 cumulative update.

    There is a new issue from the August 2017 updates that “clears” the update history on a computer that will trigger a full client scan again. This will also cause high load on your WSUS server, although for slightly different reasons, however the suggestions here and the coming updates will help to resolve the load issue from that problem as well.

    If your Windows Update/WSUS servers are red-lining, it’s a good place to start.

  • Windows 10 1607 cumulative update KB 4034658 wipes out Update History

    It’s a minor bug, but a pain in the neck. As best I can tell, it only affects Win10 Anniversary Update, version 1607.

    Computerworld Woody on Windows.

    UPDATE on this bug and two more, in Computerworld Woody on Windows