Add Take Ownership to Context Menu in Windows 10  

CJW said:

I have the "Take Ownership" button on my Context Menu & it has always worked just fine.

My question is, if I Take Ownership of a file/folder (in my case, I want to take ownership of C:\ProgramData\Microsoft\Windows\SystemData\<User_Account_Security_Identifier>\ReadOnly, so I can delete a Lock Screen picture; how do I revert the folder back to its default setting?

Hello mate,

You could use the "Reset Permissions" context menu added by the tutorial below to reset the permissions of the folder back to its default inherited permissions. It will not change the owner though.

Add Reset Permissions to Context Menu in Windows

LesFerch said:

What is the purpose of the repeated command line under the "IsolatedCommand" value name?

My searches on that value name just lead me to a whole bunch of hits on variations of this reg file and ChatGPT provides no clarity either. I tested with that value removed and the functionality appears to remain unchanged.

I also noticed that the language agnostic enhancement by @garlin did not get propagated to elevenforum. Was that intentional?

Hello mate,

If I remember correctly, the "IsolatedCommand" value was added since the single command line may not always work by itself.

The language agnostic enhancement was giving an error under the drive "runas" section in W11. It's used for the rest though.

LesFerch said:

As far as I can determine, that "IsolatedCommand" value does nothing. It may have done something at one time as per this old article:

User Assisted Compromise (UAC)

The article says that putting "notepad.exe" in the "IsolatedCommand" value will launch notepad. I observed no such behavior on Windows 10 and 11. OTOH, placing notepad.exe in the Default value always opens notepad, so that part is working as expected.



I just tested and found that the W10 reg file fails to create any entries at all under HKCR\Drive\shell\runas\command on both Windows 10 and 11.

I'll also do some more testing tomorrow.

LesFerch said:

I just tested and found that the W10 reg file fails to create any entries at all under HKCR\Drive\shell\runas\command on both Windows 10 and 11.

I'm seeing the same. I've updated the REG files to use the same version from W11.

LesFerch said:

After doing some research and VM testing, I found that the "IsolatedCommand" entry is used on Windows 10 builds up to 17025.

Glad you found the reason. I couldn't remember exactly why, but new it was needed.