Hello.

Sometimes random Windows hosts give the error as written in the title. Mostly, it's right after installing updates on the particular host. For some hours, this message's is terurned by PRTG.

Looking at the host we found nothing off, we can poll the update list with PowerShell. The server is accassable.

What could be the cause of this?


Article Comments

Attention: This article is a record of a conversation with the Paessler support team. The information in this conversation is not updated to preserve the historical record. As a result, some of the information or recommendations in this conversation might be out of date.

Hello there,

I recommend the same my colleague Torsten already recommended here for further analysis.

Kind regards,

Erhard


May, 2018 - Permalink

Hello. Sorry, I have missed this reply. Thank you, and i've send support the requested information. PAE1030597


May, 2018 - Permalink