Forum Discussion
Problems with WSUS and recent Windows 10 CU updates
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 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?
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..