Take Ownership Shortcut

Add "Take Ownership" to Context Menu of Files, Folders, and Drives in Windows​

   Information

This tutorial will show you how to add Take Ownership to the context menu of all files, folders, and drives for all users in Windows.

This will allow you to be able to instantly take ownership of a file, folder (and all contents), or drive (and all contents) by changing the owner to the current user and grant the Owner_Rights SID (current owner) full access permission.

You must be an administrator to be able to add, remove, and use the "Take Ownership" context menu.

   Note

Application files (ex: EXE, CMD, MSI) will continue to have Run as administrator instead of Take Ownership in their context menu.

---

When you right click or press and hold on a file, folder, or drive, and click/tap on Take Ownership, you may be prompted by UAC for permission to do so first.

If a user is logged in as an administrator, then the user would just click/tap on Yes to approve and take ownership. The owner of the file, folder, or drive would be changed to the current administrator user account. Permissions would be set to allow the Owner_Rights SID (current owner) full control of the file, folder, or drive.

If a user is logged in as a standard user, then the user would need to enter a selected administrator's password to approve and take ownership. The owner of the file, folder, or drive would be changed to the selected administrator account, and not the standard user. Permissions would be set to allow the Owner_Rights SID (current owner) full control of the file, folder, or drive.

---

The Take Ownership context menu will not be available when you right click on the C: drive, C:\Program Files folder, C:\Program Files (x86) folder, C:\ProgramData folder, C:\Users folder, and C:\Windows folder. This was done because taking ownership of these system folders can make Windows unstable since it would also take ownership of all the folder's content at the same time.

You will still be able to use the Take Ownership context menu of files inside the folder locations above.

If you would like to have a custom location(s) of your own to not have the context menu, then please feel free to post a request in this tutorial thread. I'll be happy to post back with a custom .reg file for it.

   Warning

This context menu will only work with English Windows installations.

If you have a different language, then please post a reply with what language you have instead. I'll be happy to post back a translated version for you.

EXAMPLE: Take Ownership in Context Menu






Here's How:

1. Do step 2, 3, or 4 below for what you would like to do.


2. To Add "Take Ownership" to Context Menu

   Note

Application files (ex: EXE, CMD, MSI) will still have Run as administrator instead of Take Ownership in the context menu when you use this step.

A) Click/tap on the Download button below to download the file below, and go to step 5 below.

Add_Take_Ownership_to_context_menu


Download


3. To Add "Take Ownership" with Pause to Context Menu

   Note

This option pauses the command when you use the "Take Ownership" context menu to be able to see the command results. This can be handy to verify setting ownership and permissions was successful or not.

Application files (ex: EXE, CMD, MSI) will still have Run as administrator instead of Take Ownership in the context menu when you use this step.

A) Click/tap on the Download button below to download the file below, and go to step 5 below.

Add_Take_Ownership_with_Pause_to_context_menu.reg


Download


4. To Remove "Take Ownership" from Context Menu

   Note

This is the default setting, and will also restore the default Run as administrator for .exe files.

A) Click/tap on the Download button below to download the file below, and go to step 5 below.

Remove_Take_Ownership_from_context_menu.reg


Download


5. Save the .reg file to your Desktop.

6. Double click on the downloaded .reg file to merge it.

7. If prompted, click on Run, Yes (UAC), Yes, and OK to approve the merge.

8. When finished, you can delete the downloaded .reg file if you like.



That's it,
Shawn

Related Tutorials

---

• How to Add or Remove the Security Tab from Properties in Windows 7
• How to Restore TrustedInstaller as Owner of a File in Vista and Windows 7
• How to Allow or Deny Permissions to Users and Groups
• How to Add or Remove Users and Groups from "User Rights Assignment"
• How to Allow or Prevent Users and Groups to Take Ownership
• How to Add Reset Permissions to Context Menu in Windows
• Enable or Disable Inherited Permissions for Files and Folders in Windows

Related Windows 10 Tutorials

---

• How to Add View Owner to Context Menu in Windows
• Change Permissions of File, Folder, Drive, or Registry Key for Users and Groups in Windows 10
• How to Change Owner of File, Folder, Drive, or Registry Key in Windows 10
• How to Add Advanced security to context menu in Windows 8 and Windows 10
• How to Add a File Attributes context menu in Windows 10
• How to Remove Security tab from Drives, Files, and Folders Properties in Windows 10
• How to Add Reset Permissions to Context Menu in Windows
• Enable or Disable Inherited Permissions for Files and Folders in Windows
• How to Add Inherited Permissions Context Menu in Windows
• How to Add List Permissions Context Menu in Windows
• How to Backup and Restore Permissions of Files, Folders, or Drives in Windows 10
• How to Add Change Owner to Context Menu in Windows 10

 

[Brink]

If this was a system file, then you could try running SFC /SCANNOW to repair the file.

http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

If it's just the icons are messed up, then you could also try rebuilding the icon cache.

http://www.sevenforums.com/tutorials/49819-icon-cache-rebuild.html

 

[Brink]

UPDATE:

I have updated the .reg files for the Take Ownership context menu in this tutorial.

The Take Ownership context menu will now no longer be available when you right click on the C: drive, C:\Program Files folder, C:\Program Files (x86) folder, C:\ProgramData folder, C:\Users folder, and C:\Windows folder since taking ownership of these Windows system folders can make Windows unstable.

This was done to prevent taking ownership of these locations by mistake.

 

[Scoop]

Shawn,

Thanks for the updated Reg download info.

If we had previously downloaded the earlier version, will the updated version overwrite the earlier version?

For example, do we need to remove the earlier download version before downloading the updated version?

 

[Brink]

Hello Scoop,

No need to remove the old one. The new .reg file only has two new "Applies to" string values that get added to restrict the context menu. Just merging the new .reg file is fine to update.

 

[Scoop]

Hello Scoop,

No need to remove the old one. The new .reg file only has two new "Applies to" string values that get added to restrict the context menu. Just merging the new .reg file is fine to update.

10-4, thanks

 

[endeavor]

UPDATE:

I have updated the .reg files for the Take Ownership context menu in this tutorial.

The Take Ownership context menu will now no longer be available when you right click on the C: drive, C:\Program Files folder, C:\Program Files (x86) folder, C:\ProgramData folder, C:\Users folder, and C:\Windows folder since taking ownership of these Windows system folders can make Windows unstable.

This was done to prevent taking ownership of these locations by mistake.

And is a great idea!
I see you've already added it to Windows 8 AND Windows 10 tutorials already
I assume you are going to do that for your Vista one as well?
Vista: Context Menu - Take Ownership

 

[Brink]

You can use this on Vista as well if you like, but I pretty much haven't been updating anything for Vista anymore since it's so old now.

 

[Scoop]

Shawn,

I just downloaded & ran the updated reg file and noticed something changed besides the removal of the 'take ownership' option from my C: drive.

Here's what I did:

Right before downloading & running the updated reg file, I checked a few of my folders, some in 'My Docs', a couple on my Desktop. The 'take ownership' option was there as expected before running the updated reg file download.

After running the updated reg download, the 'take ownership' option isn't present with folders in the right-click menu.

Individual files within folders are ok, the option is still there.

I don't see a need for me to use that option on folders but I thought I'd mention it in case it wasn't known that this changed with the updated reg download.

 

[Brink]

Thank you for letting me know Scoop.

It was the option to exclude the context menu on the "C:\Users" folder. It carried over to the "This PC" and desktop folders as well. I updated the .reg files to remove this option to restore the context menu to them now.

Downloading and merging the updated .reg file will fix it for you.

 

[Pyprohly]

A needed preventative, Brink, although don’t you think banning the entire C:\Window hierarchy is a little too much? If I were unable to manipulate permission settings on my own, I would certainly like a tool like this that will permit myself to edit single files in the System32 folder with ease, but at the same time prevent me from doing anything drastically stupid.

As such, I propose the following AppliesTo string.

"AppliesTo"="NOT (System.ItemPathDisplay:=\"C:\\Users\" OR System.ItemPathDisplay:=\"C:\\ProgramData\" OR System.ItemPathDisplay:=\"C:\\Windows\" OR System.ItemPathDisplay:=\"C:\\Windows\\System32\" OR System.ItemPathDisplay:=\"C:\\Program Files\" OR System.ItemPathDisplay:=\"C:\\Program Files (x86)\")"

It’s similar to the one now except it applies strictly exclusively to those folders and not any of their child items.

 

[Scoop]

Shawn,

I downloaded & ran the updated version. Folders all showing the ownership option.

 

[Brink]

A needed preventative, Brink, although don’t you think banning the entire C:\Window hierarchy is a little too much? If I were unable to manipulate permission settings on my own, I would certainly like a tool like this that will permit myself to edit single files in the System32 folder with ease, but at the same time prevent me from doing anything drastically stupid.

As such, I propose the following AppliesTo string.

"AppliesTo"="NOT (System.ItemPathDisplay:=\"C:\\Users\" OR System.ItemPathDisplay:=\"C:\\ProgramData\" OR System.ItemPathDisplay:=\"C:\\Windows\" OR System.ItemPathDisplay:=\"C:\\Windows\\System32\" OR System.ItemPathDisplay:=\"C:\\Program Files\" OR System.ItemPathDisplay:=\"C:\\Program Files (x86)\")"

It’s similar to the one now except it applies strictly exclusively to those folders and not any of their child items.

Thank you. Updated.

 

[rob1j]

can two additions to context menue be done?

Nice one Brink! I am new here. It seems to me that "take ownership" "and restore to system", or other previous owner, would be very convenient if installed together. The problem as I see it is that the directory in the registry is always given as "runas/command" so the first installed is overwritten by the second. Is this a hard restriction or is there a way round it? I have tried a number of fudges but no luck.

 

[Brink]

Hello Rob, and welcome to Seven Forums.

Yeah, that's the main issue I ran across as well with it under "runas". I haven't found a viable alternative yet either.

 

[rob1j]

can two additions to context menue be done?

Thanks for the prompt reply Brink. I don't have the system knowledge to research this possibility so I think it stays at that.
Thanks again

 

[PEDRO1957]

Thanks a bunch. Hours ago I lost ownership to a folder. Do not know why. When I wanted to take ownership a window did pop out asking the object names ?What the hell was that ? I tried to place the path of the folder but it did not work.
Other dd message I got ws that I would need administrator rights in other files, being i was the administrator.
It was very annoying.
Until I found your wonderful shortcut that solved my problem.
That has never happened to me in windows XP. But it happens in windows 7. Annoying. Thank you.
Your shortcut was magical.
It worked like a charm.

Thank you

 

[Brink]

You're most welcome Pedro. I'm glad it could help.

 

[PEDRO1957]

Thank you for your answer.
Knowing very little about computers an explanation would be welcome.
I use windows 7 SP1

1- FOLDER OK

When I check folder properties ,security tab , I see in group or user names.

account unknown and a string of numbers.

PEDRO PEDROSO ( PEDROPEDROSO-PC \ PEDRO PEDROSO ) -


The folder is fine
The name pedrpedroso-pc , matches the name of my computer.

The folder is in external drive.
I did access the external drives through another computer weeks ago-windows XP.
That user unknown might be that computer i used.

All ok

2. but I have a folder I cannot delete
The folder is empty , so no big deal I guess.

When I try to delete it I got the message I need permission from administrator .

When I check the folder permissions, I find that the permissions are for pedropedroso-pc , and unknown user.

The permissions for both the folder that works fine and the folder I cannot delete are the same , but the folder I cannot delete ask me administrator permission

I checked the accounts I have and there is only one. Pedro Pedroso , who is administrator.


Why the folder is asking me administrator rights when I am administrator ?
I guess system is not OK.

Its a bug.

There is only one account in this PC , I am administrator, and the folder asks me Administrator rights ?

Anyway :

My question is about changing permissions manually.

I try to change permission , add user name .

Box opens

SELECT THIS OBJECT TYPE


Users, groups, or built in security principles

( All options are selected )



FROM THIS LOCATION

PEDROPEDROSO-PC

(There is only this option .Only this location available)



ENTER THE OBJECTS NAME TO SELECT

A problem is here .

What is that ?

I guess they are asking to name the folder I want to change.

I tried to place the folder address , but it did not work.

So I reach a dead end.

How to select object name ?

Besides if the permissions of the folders are only for pedropedroso-pc , what if I change computer with windows 10 ?

I wont be anymore in pedropedroso-pc

Will the folders open in another PC ?




Thank you in advance for your time.

These systems dont work very well anyway.

But you were my savior.

Besides this problem and chrome crashes, PC works well.

 

[isidroco]

Hi brink, your TakeOwnership batch was very useful to me. It's necesary to adapt it for SPANISH windows versions replacing the 4 instances of "/D y" (where y means yes) by "/D s" (where s= si, spanish for yes). That odd behaviour between different localized versions of programs used with command lines breaks a lot of batch files. MS guys are dumb avoiding universal command formats (among other things).

 

[Brink]

I'm glad it could help isidroco, and welcome to seven Forums.

Yeah, it would be nice to have parameters that would be universal for all languages.