sodcalculator

10 Tech How-To

Fix Access Denied Error on Windows 10 Administrator Account

Guide 10-38487 · Updated · Step by step

If you are logged into a Windows 10 administrator account but still get an “Access Denied” error when opening files, changing system settings, or running commands, the fix usually involves taking ownership of the file or folder, enabling the built-in Administrator account, or repairing corrupted permission entries. Below are the exact steps to resolve this common issue, plus background on why it happens and how to prevent it.

Why an Administrator Account Still Gets “Access Denied”

Windows 10 separates the administrator group from the built-in Administrator account. Even if your user account is a member of the Administrators group, User Account Control (UAC) runs most programs with standard user privileges unless you explicitly choose “Run as administrator.” This means many system files, protected folders, and registry keys are still off-limits to your normal token.

Additionally, file and folder permissions are stored in Access Control Lists (ACLs). If the ACL for a file was created under a different user profile, after a system migration, or by a previous Windows installation, your current account may not have the necessary rights—even if you are an admin. The error message often appears as “You need permission to perform this action” or “Access is denied” when you try to open, modify, or delete the item.

Fix 1: Run the Program or Command as Administrator

This is the quickest fix and works for most cases where the error appears in a specific app or command prompt.

  1. Right-click the program or shortcut and select “Run as administrator”.
  2. If you are using Command Prompt or PowerShell, open it from the Start menu, right-click it, and choose “Run as administrator”.
  3. When the UAC prompt appears, click Yes.

If the error only happens in one program, this usually solves it. For a more permanent solution, you can set the program to always run as administrator by going to its Properties → Compatibility tab → check “Run this program as an administrator.”

Fix 2: Take Ownership of the File or Folder

When the error persists on a specific file or folder, you need to take ownership and then grant your account full control. This is common after moving files from an old hard drive or from another computer.

  1. Right-click the file or folder and select Properties.
  2. Go to the Security tab and click Advanced.
  3. Next to “Owner,” click Change.
  4. Type your username (or Administrators) in the “Enter the object name to select” box and click Check Names, then OK.
  5. Check the box “Replace owner on subcontainers and objects” if you want to take ownership of everything inside a folder.
  6. Click OK to go back to the Security tab.
  7. Click Edit, select your user, and check Full control. Apply and OK.

If the UI method fails (which it sometimes does on stubborn files), use Command Prompt as administrator and run:

takeown /f "C:\path\to\file" /r /d y
icacls "C:\path\to\file" /grant administrators:F /t

Replace the path with your own. The /r and /t flags apply it recursively to all subfolders.

Fix 3: Enable the Built-in Administrator Account

If you still get denied, the built-in Administrator account—which is disabled by default—may be the only account with full access to certain system files. You can enable it temporarily to perform the task, then disable it again.

  1. Open Command Prompt as administrator.
  2. Type net user administrator /active:yes and press Enter.
  3. Log out and log in as “Administrator” (no password by default).
  4. Perform the file operation that was failing.
  5. When done, log out, log back into your normal account, and run net user administrator /active:no in an admin Command Prompt to disable it again.

This account is not subject to UAC filtering, so it has the highest level of access. Be careful: leaving it enabled is a security risk because it has no password by default.

Fix 4: Repair Corrupted Permissions with DISM and SFC

Sometimes the access denied error is caused by corrupted system files or a broken user profile. Running the built-in system file checkers can repair these.

  1. Open Command Prompt as administrator.
  2. Run DISM /Online /Cleanup-Image /RestoreHealth and wait for it to finish (this can take 10–20 minutes).
  3. Then run sfc /scannow and wait for the scan to complete.
  4. Restart your computer.

If the error was due to a corrupted system file, this often resolves it. If it doesn’t, you may need to create a new user profile and migrate your files, since a damaged profile can cause permission errors even for admins.

Common Mistakes and Misconceptions

  • Mistake: Using the Settings app to change permissions. The Settings app does not expose full ACL controls. Always use the Properties → Security tab in File Explorer.
  • Mistake: Disabling UAC entirely. This is not recommended and can actually break some modern apps. It also doesn’t always fix access denied errors because ACLs still apply.
  • Misconception: “I’m admin, so I can do anything.” Windows separates the admin group from the elevated token. You must explicitly elevate.
  • Mistake: Changing permissions on the entire C: drive. This can cause system instability and should be avoided. Only change permissions on the specific file or folder you need.

When to Use Each Fix

Scenario Best Fix
Error only in one app Run as administrator
Error on a specific file/folder Take ownership
Error on system files or after malware DISM + SFC
Error persists everywhere Enable built-in Administrator or create new profile

If you are dealing with a file that is locked by another process, close all programs that might be using it. You can also try booting into Safe Mode, which loads a minimal set of drivers and may allow you to change permissions without interference.

Safety and Security Considerations

Taking ownership or granting full control to a folder can expose it to other users on the same computer. Only do this on files you own or need to access. Never take ownership of the entire Windows folder or the whole C: drive—this can break system protection and make your PC vulnerable.

The built-in Administrator account should be kept disabled when not in use. If you enable it, set a strong password immediately. Also, avoid running unknown scripts with elevated privileges, as they can use your admin rights to harm the system.

Frequently Asked Questions

Why do I get “Access Denied” even though I am the only user?

Because Windows still applies ACLs and UAC. Even a single-user system runs many processes with standard privileges. The file’s owner may be a system account (like SYSTEM) or a previous user profile, so your account lacks the necessary rights.

Can I fix this by disabling User Account Control?

Disabling UAC is not recommended and often doesn’t fix the error. It can also break apps that require elevation and leaves your system more vulnerable. It’s better to use the ownership or built-in Administrator methods.

What if I can’t take ownership because the button is greyed out?

This usually happens when you are not running the Properties window as administrator. Close the window, right-click the file, and choose “Run as administrator” if available, or open File Explorer as administrator first. If that fails, use the takeown command in an elevated Command Prompt.

Will this fix work on Windows 11?

Yes, the same steps apply to Windows 11. The interface is slightly different but the underlying permission system is unchanged.

Is it safe to take ownership of system files?

No, not generally. System files are owned by TrustedInstaller for a reason. Only take ownership of files you need to modify, and consider restoring the original owner afterward if possible. For system file corruption, use DISM and SFC instead.

What if I still get “Access Denied” after all these steps?

It could be a hardware issue (like a failing drive) or the file is in use by a background service. Try restarting and then performing the operation. If it persists, create a new local administrator account and see if the error occurs there—if not, your original profile is corrupted.

Related

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →