Forum Discussion
wroot
Dec 14, 2016Silver Contributor
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...
- 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.
wroot
Dec 16, 2016Silver Contributor
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
Jan 19, 2018Copper Contributor
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?
- DeletedNov 27, 2018
I have similar issues on 2016
- wrootNov 28, 2018Silver Contributor
Do you mean with 1607 version of Windows 10 or newer?
- wrootJan 19, 2018Silver Contributor
No, on Windows Server 2012 R2. Btw, i think this issue is probably only with fresh 1607 installs. We are currently installing 1703 on new machines (will switch to fresh 1709 or even 1803 this year). But i haven't reverted this changes on the WSUS server, so i can't say for sure. Have too many issues with Windows 10 and WSUS already to bring back this older issue..