If your WSUS application pool keeps stopping in IIS, I will show you how to resolve it permanently in this guide. This is a common issue reported by many SCCM administrators, and if not resolved, it can result in synchronization failures and complications with patch management.
While troubleshooting software updates deployment issue in SCCM, I observed that the WSUS console failed to load and displayed a “Reset Server Node” error. Closing the WSUS console and re-launching it resulted in the same problem.
Upon further investigation, I discovered that the in IIS > Application Pools, the WSUSPool had stopped. I manually started the WSUS app pool but after some time it stopped automatically.
To address the issue, I attempted running the iisreset command and performed a WSUS server cleanup. However, the WSUS IIS application pool unexpectedly crashed shortly after starting the update synchronization.
The clients failed to receive Windows updates from WSUS/SUP and reported 0x80244022 error. In some environments, I have also noticed clients causing the WSUS App Pool to become unresponsive with HTTP 503 errors during WSUS sync. If you are also in the same situation, don’t worry, I will show you how to fix this permanently.
Why does WSUS IIS App Pool crashes?
Frequent reasons for the WSUS App pool halting in an SCCM environment include:
- Insufficient Resources: The server hosting WSUS may not have enough CPU, memory, or disk space to handle the load.
- Application Pool Settings: Incorrect application pool settings, such as idle timeout or recycling settings, can cause frequent stops.
- High Number of Updates: If you have enabled a large number of product updates in WSUS/SUP, it can overwhelm the server, especially if cleanup tasks are not performed regularly.
- Log File Growth: IIS logs can grow excessively large, consuming disk space and causing the application pool to stop. Learn how to manage SCCM IIS log files.
Resolving WSUS Application Pool Keeps Stopping
The WSUS application pool crashes or stops because of low private memory limits assigned to the App Pool. To resolve this issue, increase the private memory limit for the App Pool and restart the WsusPool application pool in IIS.
Launch the Internet Information Services Manager on the WSUS Server. Go to Application Pools> WSUSPool > Advanced Settings. Scroll down to the bottom of the Advanced Settings window and look for Private Memory Limit (KB). You will notice that the default value is 1843200 KB. You must increase the Private Memory Limit to 4 GB (4000000 KB). Click OK.
After you perform the above steps, right-click WsusPool and select Recycle. This will reinitialize the WSUS app pool. In the SCCM console, go to Software Updates workspace and select Synchronize software updates. The software updates synchronization begins, and this should resolve the WSUS application pool keeps stopping problem.
In addition to following the above solution, I also recommend performing the below configurations:
- Run the WSUS Server Cleanup Wizard regularly to remove unnecessary updates. Decline superseded and expired updates to reduce the load on WSUS. Follow the Microsoft’s guidelines for WSUS best practices.
- You must ensure WSUS is running the latest version and has all necessary patches applied. In addition, if you are using SCCM to deploy updates, ensure you upgrade it to the latest version and install the latest hotfixes to avoid compatibility issues.
- If none of the solutions work and if WSUS application pool is crashing continuously, consider rebuilding WSUS. To accomplish this, first uninstall WSUS completely and delete the SUSDB database. Restart your server and reinstall WSUS on the Windows server and configure it from scratch.
That concludes this troubleshooting guide. If you have any questions, feel free to share them in the comments section.
