Add Take Ownership to Context Menu in Windows 10  

Page 5 of 64 FirstFirst ... 345671555 ... LastLast

  1. Posts : 6
    Windows 10 x64 Pro
       #40

    Thank you for your help, I really appreciate it. Adding my username to permissions in the folder's properties and setting it to "Allow" "Full control" for my user account fixed the New context menu inside that folder.

    Still, I find it strange that one has to do that even after having clicked on the Take Ownership context menu.
      My Computer


  2. Posts : 68,881
    64-bit Windows 11 Pro for Workstations
    Thread Starter
       #41

    That's only because the "Take ownership" context menu only adds the "Administrators" group instead.
      My Computers


  3. Posts : 6
    Windows 10 x64 Pro
       #42

    Thank you for the reply. I think I understand now.

    Could you please tell me which of the below two modifications to the REG file is better?
    1. Replacing /grant administrators:F with /grant User:F
    2. Adding && icacls "%1" /grant User:F /c /l after icacls "%1" /grant administrators:F /c /l and before & pause
      My Computer


  4. Posts : 68,881
    64-bit Windows 11 Pro for Workstations
    Thread Starter
       #43

    It won't work properly in the context menu to call for the user name.

    It'll be best to manually add your name to permissions if needed instead.
      My Computers


  5. Posts : 6
    Windows 10 x64 Pro
       #44

    Thank you for the reply.

    Here is what I what I noticed. Let's say that we have the following file/folder structure:
    folder-1/folder-A/file1
    folder-1/folder-B/file2
    folder-1/file3

    If I take ownership of folder-1, then I will be the owner of file3 (e.g. I can rename it without having Windows ask me to provide administrator permission), but I will not be the owner of file1 and file2. Right clicking on folder-A or folder-B and then clicking on "Take Ownership" does nothing and I need to manually add my username to "Security/Group or user names" in order to become the owner of file1 and file2.

    However, if I first take ownership of folders A and B, and only then take ownership of folder-1, than I will be the owner of all three files.

    Is it possible to modify the script to address this problem or is it how it is supposed to be and there is no way around it?

    Thanks.
      My Computer


  6. Posts : 68,881
    64-bit Windows 11 Pro for Workstations
    Thread Starter
       #45

    It all depends on if the subfolders and subfiles have inheritable permissions from the parent folder that you take ownership of or not.

    The script will already change the owner to your account of the folder and it's contents though.
      My Computers


  7. Posts : 6
    Windows 10 x64 Pro
       #46

    I see. Thank you so much for your help.
      My Computer


  8. Posts : 9
    Windows 10
       #47

    Thanks for this, Shawn.
    Quick Q:
    Do you know what the "IsolatedCommand" string is used for?
    bv


    ---
    "The lyf so short, the craft so long to lerne."
    - Chaucer
    -----------------------------------------------------------------
      My Computer


  9. Posts : 68,881
    64-bit Windows 11 Pro for Workstations
    Thread Starter
       #48

    bobvance said:
    Thanks for this, Shawn.
    Quick Q:
    Do you know what the "IsolatedCommand" string is used for?
    bv


    ---
    "The lyf so short, the craft so long to lerne."
    - Chaucer
    -----------------------------------------------------------------
    Hey Bob, and welcome to Ten Forums. :)

    I don't know the official definition of "IsolatedCommand", but it's basically just a string value used to identify what command to run.
      My Computers


  10. Posts : 9
    Windows 10
       #49

    Right. I'm very familiar (so I thought ;>) with adding commands to context via reg hacks like these, but I always just put the command in the default value of "command". I never heard of "IsolatedCommand" before your little script, and Googling was of no help either.

    I just now played with it a little:
    Deleting
    "IsolatedCommand" appears to do no harm.
    Leaving
    "IsolatedCommand" in place, but clearing the default command string breaks it.
    I'm thinking that
    "IsolatedCommand" is not necessary, but I don't now enough about "runas" to be sure.

    bv


    ---
    "The lyf so short, the craft so long to lerne."
    - Chaucer
    -----------------------------------------------------------------
      My Computer


 

Tutorial Categories

Add Take Ownership to Context Menu in Windows 10 Tutorial Index Network & Sharing Instalation and Upgrade Browsers and Email General Tips Gaming Customization Apps and Features Virtualization BSOD System Security User Accounts Hardware and Drivers Updates and Activation Backup and Restore Performance and Maintenance Mixed Reality Phone


  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 05:34.
Find Us




Windows 10 Forums