Problems with WSUS and recent Windows 10 CU updates

It seems realted to SCOM crashesreported here https://blogs.technet.microsoft.com/germanageability/2016/10/17/october-2016-windows-patch-kb3192392-might-cause-scom-2012r2-console-to-crash/ But re...

wroot
Dec 16, 2016
Have made additional changes: WsusPool, made Private Memory Limit (KB) to zero (not limited) and edited web.config for WSUS
changed: <httpRuntime maxRequestLength="4096" />
to <httpRuntime maxRequestLength="204800" executionTimeout="7200"/>

This helps for the already updated from Internet machines. But fresh 1607 build still shows the same problem. Will see how it goes.

Andrew Baker

Copper Contributor

Jan 19, 2018

wroot wrote:

Have made additional changes: WsusPool, made Private Memory Limit (KB) to zero (not limited) and edited web.config for WSUS

changed: <httpRuntime maxRequestLength="4096" />

to <httpRuntime maxRequestLength="204800" executionTimeout="7200"/>

This helps for the already updated from Internet machines. But fresh 1607 build still shows the same problem. Will see how it goes.

Was this happening on a 2016 WSUS server?

Deleted

Nov 27, 2018

I have similar issues on 2016

wroot
Silver Contributor
Nov 27, 2018
Do you mean with 1607 version of Windows 10 or newer?

Forum Discussion

Problems with WSUS and recent Windows 10 CU updates