Post Feature update to Windows 10, version 1803 – Getting Access is denied.

[Larry M]

Hello,

Post feature update to Windows 10, version 1803, I get “Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))” on all computers via BatchPatch.

For those computers I had to rollback to Windows 10, version 1709 (for an unrelated software incompatibility issue) I no longer get the “Access is denied…” issue.

Would this be something related to the Windows update that maybe blocking BatchPatch? I did test BatchPatch as well with the Windows Firewall turned off to verify ports. Basic telnet is working for ports 135 and 445 on those computers.

Thank you again for all your assistance!

[doug]

“Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))” indicates a permissions issue, not a firewall or port issue.

I couldn’t tell you why your permissions would be modified after upgrading to 1803, but I can tell you that Microsoft has historically had numerous issues in the first release of any feature upgrade, so I would caution against installing any feature upgrade so soon after it is released. It seems, based on your description, that when you applied the upgrade, the permissions on your computers were somehow modified/affected.

That said, since ‘Access Denied’ is a permissions problem, you should be able to resolve it on your 1803 machines by re-evaluating and fixing the permissions.

We have not yet done any testing with 1803 because it was just barely released the other day, so I’m not able to tell you with certainty what specifically might be going on in your situation.

-Doug

[Larry M]

Hi Doug,

Ok thank you. I understand, I will post anything I find.

Thank you again!

-Larry

[Kyle]

I have been troubleshooting this issue for several days now. I have a group of Windows 10 VMs that have the 1803 version update which I can RDP to via BatchPatch or through the regular method just fine, however I cannot use BatchPatch to check for updates or pull any information from the VM without getting this same WMI error.

Error 1601: Failed to retrieve WMI info. Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))

What I have seen so far coincides with doug’s assessment of this being a permissions issue as the other IT admin can check for updates just fine using the tool and pull information, also. This appears to be related to some registry entry or corrupt profile as one (or more) of the VMs had trouble loading my profile and did not get fixed until I removed the whole profile from the VM. The profile did not become corrupt until after 1803. After rebuilding my profile, the issue is still happening. Keep in mind that I can check for updates on another security domain’s Win10 devices just fine. I also double checked DCOM permissions just to be sure.

I am not sure if there are some settings I need to define by GPO to set straight or a regedit I need to do at this point. Any more insight would be appreciated.

Thanks!

[doug]

The section on ‘Access Denied’ in this article might help.

[doug]

We have found that there does seem to be *something* up with Win 10 1803. If target computers are Win 10 1803, but the BatchPatch computer is a previous version of Windows, there are no issues. But if the BatchPatch computer is Win 10 1803 and the target computer is also Win 10 1803, then we get ‘Access Denied.’ This only applies to non-domain computers, and we are confident that the issue is something with Win 10 1803, though at the moment we don’t know what the exact cause is. It doesn’t just affect BatchPatch but will actually affect any remote WMI connections made from a Win 10 1803 computer to a Win 10 1803 computer. We have also discovered other people on the web with the same issue.

[Author]

Posts