Kaseya Community

WUAUSERV Not Running Error

This question is answered

I am beginning to test Kaseya agent installations on Windows 8.  After running a patch scan on a Windows 8 machine, I get the following error in Patch Status "The Windows service WUAUSERV (Automatic Updates/Windows Update) was not running."

Has anyone else ran into this?

Thanks.

Verified Answer
  • Please note as well that a hotfix has been released to address the triggered status of the windows update service (wuauserv) on Windows 8 and 2012 machines.  On all versions of OS prior to Win8 and 2012, the wuauserv service MUST be in a state of "RUNNING" or "STARTED" (started/start automatically/enabled/running) or you will receive this notification on the patch status page.  For Win8/2012 machines, you will need to ensure that the service is set to start automatically (enabled).  As long as the service is configured to start automatically (triggered), the patch installation scripts will be able to fire.  If you see this notification on a Win8/2012 endpoint, ensure the KServer has the latest hotfixes installed (System > Configure), ensure the service is NOT STOPPED on the endpoint, and re-run patch test or a patch scan on the endpoint.  This should clear the notification.

All Replies
  • Hi, this issue is addressed in: community.kaseya.com/.../81995.aspx

  • Please note as well that a hotfix has been released to address the triggered status of the windows update service (wuauserv) on Windows 8 and 2012 machines.  On all versions of OS prior to Win8 and 2012, the wuauserv service MUST be in a state of "RUNNING" or "STARTED" (started/start automatically/enabled/running) or you will receive this notification on the patch status page.  For Win8/2012 machines, you will need to ensure that the service is set to start automatically (enabled).  As long as the service is configured to start automatically (triggered), the patch installation scripts will be able to fire.  If you see this notification on a Win8/2012 endpoint, ensure the KServer has the latest hotfixes installed (System > Configure), ensure the service is NOT STOPPED on the endpoint, and re-run patch test or a patch scan on the endpoint.  This should clear the notification.