• 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.