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

Question

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

Islada Vies 0

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

0 comments

1 answer

Your answer

Answer 1

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!