We have been implementing a WSUS Server on Windows Server 2016 several times and it works well in the beginning but stops working after all updates (~130.000) have been downloaded and approved. We are running it with MSSQL instead of the internal database.
When all updates have been downloaded I'm not abble to show and approve all updates at a time. When I try to do so the WSUS Server crashes. At that point a client talking to the server doesn't impact its functionality. I then wrote a script to approve all the updates in smaller steps which worked. But after all the updates have been approved for our clients every contact with a client crashes the WSUS Service.
Strangly enogh when I only approve the important updates at first (which are only ~15.000) everything works perfectly fine which again points to a kind of bottleneck.
My suspicion is that the WSUS Service crashes at that point because the WSUS server has to process the information from the client against all the approved updates in the database which then crashes the WSUS service. Strangly neither the ISS nor the SQL-Server are really crashing.
Does anybody have similar expiriences or a viable solution?
Best Answer
It was in fact an IIS related prolem. The private memory available to the IIS app pool was to small. (As pointed out by @Appleoddity) After giving it three times the default available memory the WSUS service does now run perfectly well.