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.
In case someone runs into same problem with WSUS 4 on WS2012R2: i have opened IIS Manager and right-clicked Sites > WSUS Administration site. Went into Advanced settings, expanded Limits section and increased Connection Time-out from 180 to 320. Rebooted the server. When doing updates check from Win10 machine it was faster than before and the load on the server was very brief. Win10 reported status and found updates on WSUS correctly. I suspect i might need to bump that limit even more in the future once more updates for Windows 10 come out and the total size of download files increases.
Was too quick to rejoice. After enabling Critical Updates and Update Rollups and synchronizing again it shows the same error and increasing timeout value not helping anymore.
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.
C:\Program Files\Update Services\WebServices\ReportingWebService\Web.config
or
C:\Program Files\Update Services\WebServices\ServerSyncWebService\Web.configor
C:\Program Files\Update Services\WebServices\ClientWebService\Web.config
?
- ClientWebService
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?
I have similar issues on 2016
