What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general.

Learn more

PRTG Network Monitor

Intuitive to Use. Easy to manage.
More than 500,000 users rely on Paessler PRTG every day. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free Download

Top Tags

View all Tags

WMI Query Failed (80070005: Access is denied) (code: PE015) - June 2022 Windows Update



Hi all, Since apply the latest June 2022 windows server Patch (KB5014702) (Server 2016) WMI queries are failing with - (80070005: Access is denied) (code: PE015). Un-installing this MS patch resolves the issue.

Is this a knowing issue? And is there a work around that doesn't involve uninstalling the Windows Update?

2022 80070005 june pe015 wmi

Created on Jul 1, 2022 2:53:31 AM

4 Replies

Accepted Answer



If you recently installed Windows Updates KB5014702; KB5014692; KB5014754; KB5014699 & KB50004442 you might be affected by hardening changes. Microsoft recently rolled out a patch which hardens the DCOM authentication, which can cause authentication login attempts to fail.

In our experience the issue should be fixed if all updates are installed on PRTG server as well as on the target device. Please ensure that all servers are on the same patch level and reboot your PRTG Server afterwards. If you are still facing this issue even though all servers are on the same patch level, feel free to reach out to us directly via mail at [email protected] so we can take a closer look.

Alternatively as a workaround you can try to roll back the update or remove the registry entry as described here. As workaround you can also use this article to disable the hardening changes again.

Created on Jul 1, 2022 7:07:34 AM by  Timo Dambach [Paessler Support]



Hi all, we have the same issue - WMI sensors are failing with (80070005: Access is denied) (code: PE015) after applying these patches - (KB5014805) (KB5014356) (KB5011267) (KB5015811). Any update on that?

Created on Jul 25, 2022 3:00:29 PM



Hello, did you check if the probe server is on the same patch level as the affected target devices?

Created on Jul 26, 2022 7:47:50 AM by  Timo Dambach [Paessler Support]



I can confirm that having the probe and monitored devices on the same patch level resolved the issue. Thank you Timo Dambach.

Created on Jul 26, 2022 11:42:45 AM

Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.