Application files (ex: EXE
) 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 signed 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 signed 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, 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.