Add Take Ownership to Context Menu in Windows 10  

Page 57 of 58 FirstFirst ... 74755565758 LastLast
  1. Barman58's Avatar
    Posts : 3,931
    Windows 10 Pro x64 2004 - 19041 - 264 XP/Vista/Win7/Win8.1 in VM for testing
       #560

    As a long time IT Pro, who learned how permissions worked back in NT, I have to add a caution to the use of Take ownership as a general Fix to permissions Issues, especially in the System areas of the Windows Drive. This is less of an issue when used in Data areas although it is always better to add the correct permissions in a way that it is designed to use.

    I personally would only use Take Ownership in an emergency, I normally find that adding my personal user name to the files & folder permissions that I need to access is perfectly adequate for day to day use, (the need for changes is usually the result of bad programming practice by the developer by not using the Windows SDK rules)

    Taking of ownership when used indiscriminately can cause failure of Windows Process's that need Ownership Rights to operate correctly.

    If you feel you have to Take Ownership of files or folders in the system area please be sure you have a valid system backup before you start, also remember that Windows is often set up to cascade permission changes to folders and files beneath the folders you are working in, so check that you only change the minimum needed to achieve your requirements.
      My Computers

  2. Brink's Avatar
    Posts : 56,844
    64-bit Windows 10 Pro for Workstations build 21376
    Thread Starter
       #561

    bamajon1974 said:
    Gotcha. So can a "take ownership" subkey be created in HKCR\* or \exefile keys with the appropriate take ownership commands rather than the runas commands to get around breaking the runas keys that run exe files as admins?

    Thanks!
    The .reg files in the tutorial have been updated to have "Take Ownership" added to application files (ex: .exe) without removing or breaking "Run as administrator".
      My Computers


  3. Posts : 396
    Win7 Pro X64, Win10 Pro x640
       #562

    Brink said:
    The .reg files in the tutorial have been updated to have "Take Ownership" added to application files (ex: .exe) without removing or breaking "Run as administrator".
    Thank you! That was surprisingly easy. I thought that the take ownership command needed the runas string to not break functionality of the command. I assume that is not the case?
      My Computer

  4. Brink's Avatar
    Posts : 56,844
    64-bit Windows 10 Pro for Workstations build 21376
    Thread Starter
       #563

    bamajon1974 said:
    Thank you! That was surprisingly easy. I thought that the take ownership command needed the runas string to not break functionality of the command. I assume that is not the case?
    There are ways around that.
      My Computers


  5. Posts : 396
    Win7 Pro X64, Win10 Pro x640
       #564

    Understood. Should the subkey in the Drive entry be fixed as well?
      My Computer

  6. Brink's Avatar
    Posts : 56,844
    64-bit Windows 10 Pro for Workstations build 21376
    Thread Starter
       #565

    bamajon1974 said:
    Understood. Should the subkey in the Drive entry be fixed as well?
    No need for a workaround since Drive uses the "runas" key.
      My Computers


  7. Posts : 1
    WIN10
       #566

    How to reverse ownership back to the TrustedInstaller recursively ?


    This worked very nice with the context window and I would like to
    reverse this ownership back to the original "TrustedInstaller" recursively.
    It has me as the owner: Owner : NOK\mjg
    snippet:
    [SIZE=3][SIZE=1]Name : Microsoft.WindowsScan_6.3.9654.17133_x64__8wekyb3d8bbwe
    Owner : NOK\mjg

    Name : Microsoft.WindowsSoundRecorder_2021.2011.20.0_neutral_~_8wekyb3d8bbwe
    Owner : NOK\mjg

    Name : Microsoft.WindowsStore_12011.1001.1.0_neutral_split.scale-100_8wekyb3d8bbwe
    Owner : NOK\mjg

    Name : Microsoft.WindowsStore_12011.1001.1.0_x64__8wekyb3d8bbwe
    Owner : NOK\mjg

    Name : Microsoft.WindowsStore_12011.1001.113.0_neutral_~_8wekyb3d8bbwe
    Owner : NOK\mjg

    Name : Microsoft.WinJS.1.0_1.0.9200.20789_neutral__8wekyb3d8bbwe
    Owner : NOK\mjg

    How might I do that ?

    thanks in advance !
    p.s.
    my microsoft store is corrupt and tried many things to repair and give up
    just want to put permissions back for now
      My Computer

  8. Brink's Avatar
    Posts : 56,844
    64-bit Windows 10 Pro for Workstations build 21376
    Thread Starter
       #567

    SavetheBeez said:
    This worked very nice with the context window and I would like to
    reverse this ownership back to the original "TrustedInstaller" recursively.
    It has me as the owner: Owner : NOK\mjg
    snippet:
    [SIZE=3][SIZE=1]Name : Microsoft.WindowsScan_6.3.9654.17133_x64__8wekyb3d8bbwe
    Owner : NOK\mjg

    Name : Microsoft.WindowsSoundRecorder_2021.2011.20.0_neutral_~_8wekyb3d8bbwe
    Owner : NOK\mjg

    Name : Microsoft.WindowsStore_12011.1001.1.0_neutral_split.scale-100_8wekyb3d8bbwe
    Owner : NOK\mjg

    Name : Microsoft.WindowsStore_12011.1001.1.0_x64__8wekyb3d8bbwe
    Owner : NOK\mjg

    Name : Microsoft.WindowsStore_12011.1001.113.0_neutral_~_8wekyb3d8bbwe
    Owner : NOK\mjg

    Name : Microsoft.WinJS.1.0_1.0.9200.20789_neutral__8wekyb3d8bbwe
    Owner : NOK\mjg

    How might I do that ?

    thanks in advance !
    p.s.
    my microsoft store is corrupt and tried many things to repair and give up
    just want to put permissions back for now
    Hello, and welcome to Ten Forums.

    If you like, you could use the context menu added by the tutorial below to change the owner to TrustedInstaller.

    Add Change Owner to Context Menu in Windows 10
      My Computers

  9. Gorlash's Avatar
    Posts : 55
    Microsoft Windows 10 Pro 64-bit 19042 Multiprocessor Free
       #568

    I want to sincerely thank the author of this script, for producing and releasing it!!! I am using the straight context menu version.

    I had re-installed Windows on a new SSD, and kept my original disk for reference material, but dozens of directories simply are not accessible now, because of the S-1-5-21-(etc) permissions issue... all of the original \Windows, plus much in \Program Files and \Program Files(x86), were not removable due to this issue.

    There are many websites which (try to) explain how to solve this problem, but their methods are both unwieldy and unreliable... I was getting a sore throat from growling so much!!!

    But 'Take Ownership' menu item *JUST WORKS* !!!!!!!!!!!!! Thank you Thank you Thank you Thank you !!!!
      My Computer

  10. Brink's Avatar
    Posts : 56,844
    64-bit Windows 10 Pro for Workstations build 21376
    Thread Starter
       #569

    Gorlash said:
    I want to sincerely thank the author of this script, for producing and releasing it!!! I am using the straight context menu version.

    I had re-installed Windows on a new SSD, and kept my original disk for reference material, but dozens of directories simply are not accessible now, because of the S-1-5-21-(etc) permissions issue... all of the original \Windows, plus much in \Program Files and \Program Files(x86), were not removable due to this issue.

    There are many websites which (try to) explain how to solve this problem, but their methods are both unwieldy and unreliable... I was getting a sore throat from growling so much!!!

    But 'Take Ownership' menu item *JUST WORKS* !!!!!!!!!!!!! Thank you Thank you Thank you Thank you !!!!
    I'm glad it could help.

      My Computers


 
Page 57 of 58 FirstFirst ... 74755565758 LastLast

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 18:43.
Find Us




Windows 10 Forums