Microsoft: High CPU/High Memory in WSUS following Update Tuesdays
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).
Read the entire article here, High CPU/High Memory in WSUS following Update Tuesdays
via the fine folks at Microsoft.