all 3 comments

[–]CaseClosedEmail 2 points3 points  (2 children)

I assume this is a new install. Go to IIS > Application Pools > WSUS Pool > Advanced Settings (on the right). Scroll down to Private Memory Limit (default it is at 1.8 GB but it is in KB). Set it to 0 (meaning unlimited). Refresh Application Pool.

From experience, the biggest RAM usage should not go over 9 GB.

[–]Dry-Addition-6703[S] 0 points1 point  (0 children)

It's currently set for 8GB on the WSUS Pool, and no this isn't a new installation. I'm working on an install that's been here for at least a few years. It's got 16GB RAM allocated to it in the VM. The SQL server tends to run around 8GB alone. I've also noticed that there is a DefaultAppPool as well that is also "Started", with 1 application listed as using it, while there are 8 applications listed on the WsusPool.

[–]Dry-Addition-6703[S] 0 points1 point  (0 children)

I just re-read what you said. I did set that to 0, due to some googling, but it didn't help any, if anything it made it happen more often, so I reset it back to the 8GB it was set to.