WSUS console sync keeps failing what’s happening with IIS worker process recycling ?

Question

WSUS synchronization keeps failing because WsusPool is overloaded by client update requests, causing the IIS worker process to hit its memory limit and recycle during the sync. When that happens, the WSUS console disconnects and every sync attempt fails right away. I need help adjusting recycling settings, private memory limits, and optimizing WsusPool to prevent this issue. Thanks

Answer 1

WSUS requires a bunch of optimisations and ongoing maintenance. Are you performing the proper WSUS maintenance including but not limited to running the Server Cleanup Wizard (SCW), declining superseded updates, running the SQL Indexing script, etc.?

https://www.ajtek.ca/wsus/how-to-setup-manage-and-maintain-wsus-part-8-wsus-server-maintenance/

WAM (full disclosure: our product), runs through every single check to make sure your entire WSUS infrastructure is clean, and optimised with all of the appropriate changes in IIS and the SQL Database and if there are any recommendations, it provides very easy ways to adjust them through a command on the WAM Shell like:

Set-ApplicationPoolMemory -Name "WsusPool" -NewMemoryValue 4096
Set-WsusIISLimitInterval -Minutes 15

These are just 2 examples of over 14 different optimisations that need to happen to WSUS to keep it in top shape.

Answer 2

How is everything? Have you been able to solve the problem? If you have, it's really appreciated to "Accept the answer" as a way to share your experience with the community. Thank you!

Answer 3

Hi Islada Vies •

I think when WsusPool gets hammered by client update requests and IIS starts recycling because it hits the private memory cap. Once that recycle kicks in, WSUS loses its sync context and every new attempt fails instantly, so the behavior you’re describing lines up perfectly with an overloaded pool. The good news is that you can stabilize this pretty quickly by bumping the private memory limit, tightening the recycling schedule, and making sure WsusPool isn’t stuck with stale queued requests.

A practical starting point is increasing the private memory threshold to something more realistic for your load (2–4 GB is common in high‑density environments), then reviewing the regular time‑based recycling so it doesn’t collide with sync windows. You can also tune queue lengths and disable rapid‑fail protection to keep the pool from collapsing under peak traffic. Once these pieces are aligned, WSUS usually stops dropping sync sessions and behaves much more predictably.

If everything is okay, don't forget to share your experience with the issue by "Accept answer". If you need more information, feel free to leave a message. We are happy to help!