Take Ownership of Files or Folders in Windows 10

Updated 4 November 2026 · Standard formula, shown below

To take ownership of a file or folder in Windows 10 means to change its permission settings so your user account gains full control, allowing you to view, modify, or delete it. This is typically needed when you receive an “Access Denied” error or when a file was created by another user account or a previous Windows installation. The process is built into Windows 10 and does not require any third-party software.

Why Ownership Matters

Windows 10 uses a security model called Access Control Lists (ACLs) to determine who can do what with each file and folder. Every object on an NTFS drive has an owner – usually the account that created it. The owner has the right to change permissions, even for administrators who might otherwise be blocked. When you take ownership, you become the new owner, and then you can grant yourself “Full control” permissions. This is different from simply being an administrator: administrators often cannot access files owned by another user without first taking ownership, because the owner can restrict even admin access.

When You Need to Take Ownership

Common scenarios where you’d need to take ownership include:

After upgrading or reinstalling Windows, old user profile folders (like C:\Users\OldName) remain but are owned by a now-deleted account.
Files copied from another computer or an external drive may have permissions that block your current user.
System files or folders that you need to modify for troubleshooting or customization (though be cautious with system locations).
When a program or service creates files under a different account, such as SYSTEM or TrustedInstaller.

A very common example: you try to delete a folder in C:\Users and get “You need permission to perform this action” or “Folder Access Denied.” That’s when ownership change is the standard fix.

How to Take Ownership Using File Explorer (GUI)

You can do it entirely through the graphical interface, no command line needed. Here are the steps:

Right-click the file or folder and select Properties.
Go to the Security tab and click the Advanced button at the bottom.
At the top of the Advanced Security Settings window, you’ll see “Owner: [current owner]”. Click Change next to it.
In the “Select User or Group” dialog, type your username (e.g., YourName) or Administrators and click Check Names, then OK.
Back in Advanced Security, check the box “Replace owner on subcontainers and objects” if you want to take ownership of everything inside the folder.
Click OK and then OK again to close Properties.
Reopen Properties > Security, click Advanced, and now you can select your user and click Edit to grant Full control (or simply check the boxes under “Allow” for your account).

If you only need to read or delete the object, taking ownership alone may be enough, but to edit or run it, you’ll also need to set permissions.

Command-Line Method: takeown and icacls

For power users, the command prompt or PowerShell offers a faster, more scriptable way. Open Command Prompt as Administrator (right-click Start > “Command Prompt (Admin)” or “Windows PowerShell (Admin)”).

To take ownership of a folder and everything inside it:

takeown /f "C:\Path\To\Folder" /r /d y

Then to grant yourself full control:

icacls "C:\Path\To\Folder" /grant YourUserName:F /t

Replace YourUserName with your actual Windows username. The /r and /t flags make the commands recursive (apply to all subfolders and files). The /d y in takeown automatically answers “yes” to the prompt about non-Windows directories.

If you prefer PowerShell, you can use the same commands because they are built-in executables. For a single file, omit the /r and /t flags.

Common Mistakes and Pitfalls

Several things often trip people up:

Forgetting to apply to subfolders: If you only take ownership of the top folder, files inside may still be inaccessible. Always use the recursive options or check the “Replace owner” box.
Not granting permissions after ownership: Ownership alone doesn’t give you access; you must also set permissions. The icacls step is essential.
Taking ownership of system folders: Modifying ownership of C:\Windows or its subfolders can break Windows updates and security. Only do this if you have a specific, well-understood reason, and consider backing up first.
Using the wrong username: If you type your Microsoft account email instead of the local username, the command may fail. Use whoami in the command prompt to see your exact username.
Not running as administrator: The GUI method requires an admin account, and the command-line tools need an elevated prompt. Otherwise you’ll get “Access is denied.”

Alternatives and When Not to Use Ownership

Sometimes ownership isn’t the right solution. If you’re trying to access a file that’s locked by another program, restarting the program or the PC may be enough. If the file is encrypted with EFS (Encrypting File System), taking ownership won’t let you read it – you need the original encryption key. For files on a network share, the permissions are managed on the server, not locally, so you’d need to contact the network administrator.

Another alternative is to use the built-in Reset this PC feature to reinstall Windows while keeping your files, but that’s drastic. For simple access issues, you can also try right-clicking the folder, going to Properties > Security > Edit, and adding your user with full control – but that only works if you already have permission to change permissions, which ownership change grants.

Frequently Asked Questions

Why do I get “Access Denied” even as administrator?

Administrators do not automatically have access to every file. The owner of a file can explicitly deny administrators, or the file may be owned by a system account like TrustedInstaller. Taking ownership is the way to override that, but you must do it deliberately.

Is it safe to take ownership of system files?

Generally, no. System files are protected for a reason. If you change ownership of critical Windows folders, you could cause instability or prevent updates. Only take ownership of system files if you are following a specific, reputable guide and understand the risks. Always consider creating a system restore point first.

Can I take ownership of a folder without admin rights?

No. Changing ownership is a privileged operation. You must be logged in as an administrator or provide admin credentials when prompted. Standard users cannot take ownership of files they don’t own.

What’s the difference between ownership and permissions?

Ownership is the “right to control” – the owner can always change permissions. Permissions are the specific rules that say who can read, write, execute, etc. Taking ownership is the first step; then you set permissions to actually allow your account to access the file.

Does taking ownership work on FAT32 or exFAT drives?

No. Those file systems do not support NTFS permissions or ownership. If your drive is formatted as FAT32 or exFAT, you won’t see a Security tab in Properties. You’d need to convert the drive to NTFS (which may erase data) or copy the files to an NTFS drive.

Will taking ownership delete my files?

No. Changing ownership only changes the security metadata; it does not alter the file contents. Your data remains intact. However, if you then delete the file, it’s gone, so be careful.

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.