Hello, we have two Windows 2012R2 servers, where the Last Windows Update sensor is not working properly. The error message says, that the remote registry service is not running. The service is set to "Automatic (Trigger Start)" on both machines, but not running. If I start the service manually and refresh the sensor, it is working correctly, but afterwards the service automatically stops and as far as I found out, this is by design and can not be changed. When I remotely connect to the registry on the servers, the service is automatically started as it should be, but it seems, that PRTG is not starting the service prior to the check. Is there any possibility to get this working? Any recommendations would be appreciated.

Article Comments

There are two options here:

Start PowerShell with administrative privileges and run the following command: sc triggerinfo "remoteregistry" delete

Sometimes this works, but we've seen customers were it didn't work properly. In this case you can try to create a WMI sensor that checks the remote registry and restarts it when needed. Make the update sensor depend on the WMI service sensor so you don't get errors when it's not started.

Unfortunately thats the only way as of right now :/


Aug, 2014 - Permalink

Important note: The Windows Last Update (Remote Registry) sensor is deprecated as of PRTG version 16.1.23.

Please see the following article for more details and possible alternatives:


Mar, 2016 - Permalink