Frustration with WSUS... one error after the other

Question

Three months ago I was assigned the task of monitoring the WSUS Server, apparently the person previously in charge did not do any kind of monitoring or review of updates. In short, WSUS was totally abandoned.

At the beginning it was impossible to work or even open the console because it presented multiple database connection errors, reset server node error and others.
After making the adjustments recommended in the good practices and some others recommended by users through the web, it was possible to stabilize the use of the console, although it is still very slow, it does not present the amount of errors that at the beginning.

It was found that although the computers were reporting correctly they were not taking the updates that were applied, after some research it was verified that it was a dual scan error for which a reconfiguration of the current GPO was made since these workstations do not have internet connection.
The group with which the new GPO was tested started to update through WSUS without problems.

Now suddenly all the workstations and servers have stopped reporting a couple of days ago to WSUS, this happened once before but with the server restart the process was normalized but this is not the case since it has been restarted several times and the failure persists.

When reviewing the events it was possible to verify that there are constant errors:

WSUS Error
12022 Client web service not working
12032 The server's synchronization web service does not work.

ISS error
5013 A process serving application pool 'WsusPool' exceeded time limits during shut down

WSUS Server is a VM 1.8Ghz, 9 GB RAM, OS 70 GB, 1 TB updates, Windows Server 2016

Answer 1

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/

You'll also want to review:
https://www.ajtek.ca/wsus/wsus-system-requirements-what-should-i-plan-for/

1TB of updates is HUGE (normally, with WAM, the WsusContent store is <200GB and usually <100GB).

For your clients not reporting: you'll also want to review
https://www.ajtek.ca/wsus/client-machines-not-reporting-to-wsus-properly/

Pay attention to the troubleshooting part below the Client Side Script.

Lastly, it may not be worth saving. You can re-install WSUS fairly easily and start new in just a few hours.
https://www.ajtek.ca/wsus/how-to-remove-wsus-completely-and-reinstall-it/