How do we determine if the Windows Security Audit service has caused a memory leak/deadlock with another application

Question

We have had a service which has been running stably for more than a decade, suddenly enter a stalled state (that is, not stopped but not doing anything either). The only thing I can find in the event viewer for anything happening at the time the service's logs stop is Microsoft Windows security auditing, followed by an SCM info for "The Windows Update service entered the stopped state" at the time of the service failure. Several other services (for the same application) running at the time appear unaffected.

Answer 1

Hello,

Thank you for posting in Q&A forum.

This situation may be caused by the status change of the Windows Update service affecting your service. We suggest you try the following methods to check:

Ensure that the settings of the Windows Update service do not conflict with your service by checking the Windows Update settings. You can view and change update settings through the "Windows Update" option in the control panel.

Check the update history of the system to see if there were any system updates installed before the service failed. Some updates may affect the stability of the system, especially during service runtime.

Check if there are any resource depletion, network issues, or other service failures in the system that may cause service stagnation

Attempting to restart the Windows Update service may resolve the issue of service stagnation. You can run a command prompt as an administrator and enter the following command to perform this operation:

Net stop wuauerv

Net start wuauerv

Hope this answer can help you well.

Best regards，

Jill Zhou