›_ TechLoved

"You have been denied permission to access this folder"

Windows blocks you from opening a folder you own. The ownership got mangled — usually because the folder came from another machine, another user, or a backup drive. Here is how to fix it properly, including the subfolder trap that the standard guide misses.

Before you start — do not do this on system folders

If the folder you cannot access is somewhere inside C:\Windows, C:\Program Files, or C:\ProgramData: stop. Taking ownership of those folders breaks Windows updates and several built-in features. There is almost always a different fix for those — usually you do not actually need access, and the application that uses the folder reads it correctly via SYSTEM permissions you cannot see.

The instructions below are for your own data folders: documents, photos, projects, copies from old hard drives, anything in C:\Users\YourName or on a secondary drive.

The proper fix (propagates to all subfolders)

Step 1 — open the folder Properties

Right-click the locked folder → PropertiesSecurity tab.

You will likely see a message at the bottom: "You must have read permissions to view the properties of this object". That is fine — click Advanced at the bottom anyway.

Step 2 — change the owner

In the Advanced Security Settings window, the Owner line at the top probably says something like "Unable to display current owner" or shows an unknown account.

  1. Click Change next to the owner.
  2. In the new window, type your Windows username (or click "Advanced" then "Find Now" and pick yours from the list).
  3. Click OK.
  4. You return to the Advanced window. Tick the box Replace owner on subcontainers and objects. This is the key — without it, only the top folder gets the new owner.
  5. Click Apply. Wait — depending on folder size this can take from seconds to many minutes.

Step 3 — grant yourself permissions

Owner ≠ permissions. After taking ownership, you still need to add an ACL entry for your account.

  1. Still in Advanced Security Settings, click Add.
  2. Click Select a principal. Type your username, click OK.
  3. Under "Basic permissions", tick Full control.
  4. At the bottom, tick Replace all child object permission entries with inheritable permission entries from this object.
  5. Click OK on each window. Confirm any "are you sure" dialogs.
  6. Wait for the apply step to finish — large folders can take several minutes.

Try opening the folder. Should work now.

Faster alternative — Command Prompt (admin)

If you have many folders to fix, the GUI gets tedious. From an admin Command Prompt:

takeown /F "C:\Path\To\Folder" /R /D Y
icacls "C:\Path\To\Folder" /grant:r "%USERNAME%":(OI)(CI)F /T

Line 1 takes ownership recursively. Line 2 grants Full control to your current user, recursively, with inheritance. Replace the path with your actual folder.

If "Access denied" still appears after the fix

Frequently asked

Why does Windows tell me I have been denied permission to access my own folder? +
Most often because the folder was created by a different user account, or copied from another machine where it had different ownership. Windows checks the NTFS access control list (ACL) on the folder; if your current account is not on the list, Windows blocks access regardless of admin status. The fix is to take ownership and re-grant permissions to your current user.
Should I just click "Take Ownership"? Is that safe? +
For folders containing your own data — usually yes. For Windows system folders (C:\Windows, C:\Program Files) — no. Taking ownership of system folders breaks Windows updates and can leave your machine unbootable. Only take ownership of user data folders.
I clicked "Continue" but it still says access denied. What now? +
The "Continue" button only adds your user to the ACL temporarily and does not propagate to subfolders. For a folder with deep contents, you need to use the Security tab properly: right-click the folder > Properties > Security > Advanced > Change Owner > apply to all subfolders > then add Full Control permissions.

Read next

Tested on: Windows 11 Pro 23H2 (NTFS), Windows 10 Pro 22H2. Published 2026-05-10.