WSUSPool in IIS Stops Repeatedly Server 2016

Hi AJTek-Adam-J-Marshall :)
No, we don't have any maintenance procedure in our organisation related with WSUS Servers :)
Yes, all requirements met :)

Hi BruceSinger-6179 :)
Your experience with WSUS servers sounds promising and logical.
I was read a ton of posts and discussions about Private Memory Limit but with my team we didn't find the way to solve the problem, only colleagues successfully build scheduled Powershell script with smtp combination to alarm us if WSUS Pool crash again :)
Could you tell me exactly what actions you took to solve the problem in more details about increasing the default Timeout and memory, how GB RAM?

Hi RitaHu-MSFT :)
I didn't try to Disable recycling I will, thank you :)
I did try to configure memory limits but didn't help :)

Thanks a lot I appreciate your help :)

Hi 61990009，

Thanks for your posting on Q&A.

The WSUS role haven't the feature to monitor the Application Pool currently. In my opinion, the Application Pool will not stop normally. It is recommended to configure the IIS as this link Disable recycling and configure memory limits part first. It is helpful for WSUS Performance.

Then we could check whether this issue will be resolved or not. Please feedback for me if there are any updates.

Regards,
Rita

If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Windows 2016/2019 and Windows 10 Clients take a lot more resources from WSUS than previous clients do. It is important to increase the IIS default Timeout or the connection times out before WSUS creates the package is sent to the client. This creates a detection loop.

These dropped connections stays in the APP pool and eventually the App pool runs out of memory and stops. Depending on the number of Windows 2016 + clients in a detection loop and the memory assigned to the APP pool, this can happen quickly. The default Timeout needs to be increased and the default memory on the WSUS IIS instance needs to be increased to keep the detection loops from happening. There are posts on the old TechNet forums explaining how to do this.

Just restarting the APP pool does not resolve the detection loop issue. As more Windows 2016/Windows 10 clients were added to our WSUS server I had to increase the timeout and increase memory on the WSUS IIS instance to resolve this issue.

Sincerely
Bruce Singer

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/

The WsusPool shouldn't be stopping on a regular basis.

Do you have the requirements met?

https://www.ajtek.ca/wsus/wsus-system-requirements-what-should-i-plan-for/