Error code

0x80070005 — Access denied

Windows or an application does not have the rights to read, write or modify a resource.

View my favorites

0x80070005 – Access denied

Domain: WindowsPriority: High

What does this error mean?

Windows or an application does not have the rights to read, write or modify a resource.

Probable causes

  • Insufficient rights
  • Invalid owner or ACL
  • Antivirus or blocking safety strategy

Verification and resolution

  1. Relaunching, Administration Action
  2. Control the file or folder permissions
  3. Check the event log and security strategies
Precaution: Do not permanently disable the antivirus or UAC to bypass the problem.

← Return to error codes

Operational context

Windows error 0x80070005 indicates that an operation was denied by an authorization boundary. The effective user token, NTFS/registry permissions, service identity, UAC elevation and security software should be checked before granting broader rights.

Step-by-step checks

  1. Identify the exact operation that returns 0x80070005 and the security principal performing it; do not troubleshoot only from the friendly application message.
  2. Inspect effective file, folder, registry or service permissions on the resource involved and compare them with a known-working account or host.
  3. Determine whether the process requires elevation, runs as a service account or is being redirected/blocked by application-control or endpoint-security policy.
  4. Use Event Viewer and application logs to find the denied object or privilege and correct the narrowest permission required rather than adding the user to Administrators.

Useful verification commands

Use commands only on systems you administer and capture the read-only output before making a configuration change.

whoami /all
icacls "C:\Path\To\Resource"
Get-Acl "C:\Path\To\Resource" | Format-List

How to validate the result

The original operation must succeed under the intended least-privilege identity, with no new broad administrative membership or blanket Full Control permission introduced.

Evidence to keep

Keep the failing path/object, user/service identity, ACL output, elevation context, relevant Security/Application events and the exact operation that was retested.

Frequently asked question

Should I fix 0x80070005 by granting Everyone Full Control?

No. That can hide the real authorization boundary and create a security problem. Grant only the permission required to the correct service or user identity.

Related BAOI resources: IT tools · procedures · IT dictionary.

♡ 0