Hi,
According to your description, first I recommend starting with the application pool check of IIS:
- Check the status of the application pool running the WSUS service.
(1) On your WSUS Server, launch the IIS Manager.
(2) Click 'Application Pools' is in the Connections list.
(3) Right click 'WsusPool' and select 'Start' to restart the WSUSPool.
- Lower memory limits can also cause a situation.
(1) On your WSUS Server, launch the IIS Manager.
(2) Click 'Application Pools' is in the Connections list.
(3) Right click 'WsusPool' and select 'Advanced Settings…'
'General' - 'Queue Length' : 25,000.
'Rapid-Fail Protection' - 'Service Unavailable'
Response: TcpLevel
'Rapid-Fail Protection' - 'Failure Interval (minutes)' : 30
'Rapid-Fail Protection' - 'Maximum Failures' : 60
'Recucling' - 'Private Memory limit' : x4 times, or set to 0 (unlimited).
(4) Click 'ok' to save and restart the server.
After completing the above steps, if the WSUS console can be started, then I recommend to perform the server cleanup wizard in the WSUS console, or consider using a script for server cleanup: "WSUS
Cleanup".
Regards,
Yic
Please remember to mark as answers if they help.
If you have feedback for TechNet Subscriber Support, contact
tnmff@microsoft.com.