Accounts Add "Reset Permissions" to Context Menu in Windows 11

Ghot · Jan 1, 2024

Nice one.

I assume this "un-does" Take Ownership?

Brink · Jan 1, 2024

Ghot said:
Nice one.

I assume this "un-does" Take Ownership?

Hey mate,

It doesn't affect the "owner", but only resets the "permissions" bit.

Ghot · Jan 1, 2024

Brink said:
Hey mate,

It doesn't affect the "owner", but only resets the "permissions' bit.

Thanks... it'll still be useful for messed up permissions. Added to Leader Board.

paradoxum · Jan 26, 2024

I could have used this so many times D: thanks

Brink · Jan 26, 2024

paradoxum said:
I could have used this so many times D: thanks

charge · Feb 12, 2024

Hi
i know a little bit because my English is so poor.
"Reset Permissions" in context menu of files and folders. This one i choice
Add_Reset_Permissions_to_context_menu.reg
Add_Reset_Permissions_with_Pause_to_context_menu.reg
thanks

Almighty1 · Mar 31, 2025

Hey @Brink - How would I use it to reset permissions for the entire C: drive?

Brink · Mar 31, 2025

Almighty1 said:
Hey @Brink - How would I use it to reset permissions for the entire C: drive?

You can't with this context menu. It would most likely break things.

Depending on how bad it is, a repair install may help.

Almighty1 · Mar 31, 2025

Brink said:
You can't with this context menu. It would most likely break things.

Depending on how bad it is, a repair install may help.

I already did a repair install though. DDU (Display Driver Uninstaller), the author claims the log shows that C:\ProgramData\Intel has a permissions issue except he doesn't know exactly where the permissions is having problems. You can see this thread which explains it better.

Display Driver Uninstaller (DDU) v18.1.0.0 causes GSOD in Safe Mode - Page 2 - Wagnardsoft Forum

Brink · Mar 31, 2025

Almighty1 said:
I already did a repair install though. DDU (Display Driver Uninstaller), the author claims the log shows that C:\ProgramData\Intel has a permissions issue except he doesn't know exactly where the permissions is having problems. You can see this thread which explains it better.

Display Driver Uninstaller (DDU) v18.1.0.0 causes GSOD in Safe Mode - Page 2 - Wagnardsoft Forum

I suppose you could try manually navigating to the path allowing access if prompted (if not then take ownership if needed), and then try the uninstaller again.

Almighty1 · Mar 31, 2025

Brink said:
I suppose you could try manually navigating to the path allowing access if prompted (if not then take ownership if needed), and then try the uninstaller again.

I actually looked at the logs for DDU and it seems the access denies are in the registry as C:\ProgramData\Intel according to the logs seems to really be at C:\ProgramData\Intel\GFXInstaller which is just the Intel Graphics Driver so it seems one can just remove the Intel Graphics driver in Device Manager until it says Microsoft Basic Graphics and then delete C:\ProgramData\Intel\GFXInstaller as this is what the logs shows:

Code:

C:\ProgramData\Intel\GCC\gcc_svc_log_2025-03-30.txt</Message>
        </Event>
        <Event>
            <Time>3/30/2025 5:12:32 PM</Time>
            <Message>Deleted file:
C:\ProgramData\Intel\GCC\gcc_svc_log_2025-03-29.txt</Message>
        </Event>
        <Event>
            <Time>3/30/2025 5:12:32 PM</Time>
            <Message>Deleted file:
C:\ProgramData\Intel\GCC\gcc_svc_lace_log_2025-03-30.txt</Message>
        </Event>
        <Event>
            <Time>3/30/2025 5:12:32 PM</Time>
            <Message>Deleted file:
C:\ProgramData\Intel\GCC\gcc_svc_lace_log_2025-03-29.txt</Message>
        </Event>
        <Event>
            <Time>3/30/2025 5:12:32 PM</Time>
            <Message>Deleted directory:
C:\ProgramData\Intel\GCC</Message>
        </Event>
        <Event>
            <Time>3/30/2025 5:12:32 PM</Time>
            <Message>Deleted file:
C:\ProgramData\Intel\GFXInstaller\Installer\IntelGFX_20250329_113356_Install.log</Message>
        </Event>
        <Event>
            <Time>3/30/2025 5:12:32 PM</Time>
            <Message>Deleted file:
C:\ProgramData\Intel\GFXInstaller\Bootstrapper\IntelGFX_Bootstrapper_20250329_113349.log</Message>
        </Event>
        <Event>
            <Time>3/30/2025 5:12:32 PM</Time>
            <Message>Deleted directory:
C:\ProgramData\Intel\GFXInstaller\Installer</Message>
        </Event>
        <Event>
            <Time>3/30/2025 5:12:32 PM</Time>
            <Message>Deleted directory:
C:\ProgramData\Intel\GFXInstaller\Bootstrapper</Message>
        </Event>
        <Event>
            <Time>3/30/2025 5:12:32 PM</Time>
            <Message>Deleted directory:
C:\ProgramData\Intel\GFXInstaller</Message>
        </Event>
        <Warning>
            <Time>3/30/2025 5:12:32 PM</Time>
            <Message>Couldn't find directories, access denied!01</Message>
            <Values Separator=" : ">
                <KvP>
                    <Key>
</Key>
                    <Value>C:\ProgramData\Intel\</Value>
                </KvP>
            </Values>
        </Warning>
        <Warning>
            <Time>3/30/2025 5:12:32 PM</Time>
            <Message>Remaining folders found  : C:\ProgramData\Intel\ --&gt; C:\ProgramData\Intel\DAL</Message>
        </Warning>
        <Warning>
            <Time>3/30/2025 5:12:32 PM</Time>
            <Message>Remaining folders found  : C:\ProgramData\Intel\ --&gt; C:\ProgramData\Intel\DSA</Message>
        </Warning>
        <Warning>
            <Time>3/30/2025 5:12:32 PM</Time>
            <Message>Remaining folders found  : C:\ProgramData\Intel\ --&gt; C:\ProgramData\Intel\iCLS Client</Message>
        </Warning>
        <Warning>
            <Time>3/30/2025 5:12:32 PM</Time>
            <Message>Remaining folders found  : C:\ProgramData\Intel\ --&gt; C:\ProgramData\Intel\Installer</Message>
        </Warning>
        <Warning>
            <Time>3/30/2025 5:12:32 PM</Time>
            <Message>Remaining folders found  : C:\ProgramData\Intel\ --&gt; C:\ProgramData\Intel\Intel Extreme Tuning Utility</Message>
        </Warning>
        <Warning>
            <Time>3/30/2025 5:12:32 PM</Time>
            <Message>Remaining folders found  : C:\ProgramData\Intel\ --&gt; C:\ProgramData\Intel\IntelSGXPSW</Message>
        </Warning>
        <Warning>
            <Time>3/30/2025 5:12:32 PM</Time>
            <Message>Remaining folders found  : C:\ProgramData\Intel\ --&gt; C:\ProgramData\Intel\Logs</Message>
        </Warning>
        <Warning>
            <Time>3/30/2025 5:12:32 PM</Time>
            <Message>Remaining folders found  : C:\ProgramData\Intel\ --&gt; C:\ProgramData\Intel\Package Cache</Message>
        </Warning>
        <Warning>
            <Time>3/30/2025 5:12:32 PM</Time>
            <Message>Remaining folders found  : C:\ProgramData\Intel\ --&gt; C:\ProgramData\Intel\Uploader</Message>
        </Warning>

Wouldn't something like Tweaking.com Windows Repair tool fix both the registry and the files to the default permissions?

Brink · Mar 31, 2025

Almighty1 said:

I actually looked at the logs for DDU and it seems the access denies are in the registry as C:\ProgramData\Intel according to the logs seems to really be at C:\ProgramData\Intel\GFXInstaller which is just the Intel Graphics Driver so it seems one can just remove the Intel Graphics driver in Device Manager until it says Microsoft Basic Graphics and then delete C:\ProgramData\Intel\GFXInstaller as this is what the logs shows:

Code:

C:\ProgramData\Intel\GCC\gcc_svc_log_2025-03-30.txt</Message>
        </Event>
        <Event>
            <Time>3/30/2025 5:12:32 PM</Time>
            <Message>Deleted file:
C:\ProgramData\Intel\GCC\gcc_svc_log_2025-03-29.txt</Message>
        </Event>
        <Event>
            <Time>3/30/2025 5:12:32 PM</Time>
            <Message>Deleted file:
C:\ProgramData\Intel\GCC\gcc_svc_lace_log_2025-03-30.txt</Message>
        </Event>
        <Event>
            <Time>3/30/2025 5:12:32 PM</Time>
            <Message>Deleted file:
C:\ProgramData\Intel\GCC\gcc_svc_lace_log_2025-03-29.txt</Message>
        </Event>
        <Event>
            <Time>3/30/2025 5:12:32 PM</Time>
            <Message>Deleted directory:
C:\ProgramData\Intel\GCC</Message>
        </Event>
        <Event>
            <Time>3/30/2025 5:12:32 PM</Time>
            <Message>Deleted file:
C:\ProgramData\Intel\GFXInstaller\Installer\IntelGFX_20250329_113356_Install.log</Message>
        </Event>
        <Event>
            <Time>3/30/2025 5:12:32 PM</Time>
            <Message>Deleted file:
C:\ProgramData\Intel\GFXInstaller\Bootstrapper\IntelGFX_Bootstrapper_20250329_113349.log</Message>
        </Event>
        <Event>
            <Time>3/30/2025 5:12:32 PM</Time>
            <Message>Deleted directory:
C:\ProgramData\Intel\GFXInstaller\Installer</Message>
        </Event>
        <Event>
            <Time>3/30/2025 5:12:32 PM</Time>
            <Message>Deleted directory:
C:\ProgramData\Intel\GFXInstaller\Bootstrapper</Message>
        </Event>
        <Event>
            <Time>3/30/2025 5:12:32 PM</Time>
            <Message>Deleted directory:
C:\ProgramData\Intel\GFXInstaller</Message>
        </Event>
        <Warning>
            <Time>3/30/2025 5:12:32 PM</Time>
            <Message>Couldn't find directories, access denied!01</Message>
            <Values Separator=" : ">
                <KvP>
                    <Key>
</Key>
                    <Value>C:\ProgramData\Intel\</Value>
                </KvP>
            </Values>
        </Warning>
        <Warning>
            <Time>3/30/2025 5:12:32 PM</Time>
            <Message>Remaining folders found  : C:\ProgramData\Intel\ --&gt; C:\ProgramData\Intel\DAL</Message>
        </Warning>
        <Warning>
            <Time>3/30/2025 5:12:32 PM</Time>
            <Message>Remaining folders found  : C:\ProgramData\Intel\ --&gt; C:\ProgramData\Intel\DSA</Message>
        </Warning>
        <Warning>
            <Time>3/30/2025 5:12:32 PM</Time>
            <Message>Remaining folders found  : C:\ProgramData\Intel\ --&gt; C:\ProgramData\Intel\iCLS Client</Message>
        </Warning>
        <Warning>
            <Time>3/30/2025 5:12:32 PM</Time>
            <Message>Remaining folders found  : C:\ProgramData\Intel\ --&gt; C:\ProgramData\Intel\Installer</Message>
        </Warning>
        <Warning>
            <Time>3/30/2025 5:12:32 PM</Time>
            <Message>Remaining folders found  : C:\ProgramData\Intel\ --&gt; C:\ProgramData\Intel\Intel Extreme Tuning Utility</Message>
        </Warning>
        <Warning>
            <Time>3/30/2025 5:12:32 PM</Time>
            <Message>Remaining folders found  : C:\ProgramData\Intel\ --&gt; C:\ProgramData\Intel\IntelSGXPSW</Message>
        </Warning>
        <Warning>
            <Time>3/30/2025 5:12:32 PM</Time>
            <Message>Remaining folders found  : C:\ProgramData\Intel\ --&gt; C:\ProgramData\Intel\Logs</Message>
        </Warning>
        <Warning>
            <Time>3/30/2025 5:12:32 PM</Time>
            <Message>Remaining folders found  : C:\ProgramData\Intel\ --&gt; C:\ProgramData\Intel\Package Cache</Message>
        </Warning>
        <Warning>
            <Time>3/30/2025 5:12:32 PM</Time>
            <Message>Remaining folders found  : C:\ProgramData\Intel\ --&gt; C:\ProgramData\Intel\Uploader</Message>
        </Warning>

Wouldn't something like Tweaking.com Windows Repair tool fix both the registry and the files to the default permissions?

Reinstalling the driver may restore them.

garlin · Mar 31, 2025

The dirty secret behind "Reset permissions" is it's often not very helpful.

There's a presumption that someone or some process has incorrectly altered one or more child folders from a given directory path, and resetting the inheritance from that directory level down to all child folders will restore the previous "correct" state.

More often that not, many subfolders will explicitly override their parent's permissions and you won't necessarily know where. There is no roadmap.

When Windows installs components, each component has a manifest file that has every folder it owns, and their security descriptors explicitly listed. The problem here is you're tackling a 3rd-party driver/tools/app folder which is commonly installed by a MSI package. Sometimes you're lucky and the vendor has a "repair" option on the MSI which just forces a reinstall.

If you don't, you only have two options:
1. Uninstall everything and delete (or rename) the folders. Re-install Intel's package again.

2. Find a friend who has the identical package installed. Run icacls to export their folder permissions, and restore those permissions on your PC.

Working system:

Code:

icacls "C:\ProgramData\Intel" /save "C:\path\ACLs.txt" /t /c

Broken system:

Code:

 icacls "C:\ProgramData\Intel" /restore "C:\path\ACLs.txt"

Almighty1 · Mar 31, 2025

@Brink and @garlin - Thanks for the pointers. In this case, since the logs themselves point to C:\ProgramData\Intel\GFXInstaller with the access denied which is basically the Intel Graphics drivers as the other folders in and C:\ProgramData\Intel all show Remaining Folders found which from what I can tell means it can access them without issues. If I right click on the Device Manager's Intel GPU and uninstall and delete files and repeat until it says Microsoft Basic Graphics Driver, then technically at that point the Intel Drivers are no longer needed since it's no longer in the Driver Store so if I deleted the C:\ProgramData\Intel\GFXInstaller folder at this point to get rid of it, then running the Intel Graphics Driver installer will recreate a new C:\ProgramData\Intel\GFXInstaller, wouldn't it also have the create permissions at this point from the installer?

garlin · Mar 31, 2025

They should. MSI-based installlers have a manifest which tells them how to create folders and permissions.

Almighty1 · Apr 1, 2025

Turns out reading the XML logs using DDU was better than using Notepad++ as the access denied was more of a C:\ProgramData\Intel issue so what I did was:
1. Copy the Intel folder from C:\ProgramData\ to Desktop to see where it had trouble, first it did a access denied on Intel but Try again got passed it but the second one was at IntelSGXPSW that try again could not get passed.
2. At this point, I cleared the Intel folder on the desktop and went directly into C:\ProgramData\Intel and copied each item to the Intel folder on the desktop.

I copied everything except for IntelSGXPSW which I did last and all the other folders copied successfully without complaints. The IntelSGXPSW had the same issue where it was access denied and try again did not work.
Properties on the folder shows:

Clicking on "Continue" only resulted in this:

I had to use the Privilege File Manager from Right-Click tools New App: Right-Click Tools in TrustedInstaller mode where it showed:

where it showed:

I could not even use my PrintScreen key in Snagit to do the screenshots and had to open Snagit and use the mouse as the File Manager's TrustedInstaller access was higher than the Administrator access given to the Print Screen key by a SnagitPriv.exe process.

And these were the files in the folder:

C:\ProgramData\Intel\IntelSGXPSW belongs to Intel® Software Guard Extensions (SGX) Platform Software Driver v2.25.100.3 so first I renamed it to IntelSGXPSW.old and then deleted the two .inf's for SGX, one was base and the other was the PSW with DriverStore Explorer and then used pnputil and installed the SGX base and PSW.inf's using Intel's documentation instructions as only older versions used a .exe installer while new versions were all INF based, the PSW.inf created the IntelSGXPSW folder and it had the exact same files and permissions as shown above and as Intel SGX is hardware on the Intel CPU, the permissions were done that way by design as from my research, it seems SGX is a security feature. So at the end, I deleted the IntelSGXPSW folder and renamed the IntelSGXPSW.old folder back from IntelSGXPSW as I wanted it to keep the April 9, 2019 folder creation date which was the date Dell built the computer and deleted the 4 files and basically repeated the uninstall of the two .inf files using DriverStore Explorer and installed the SGX base and PSW.inf's using pnputil which added the 4 files back to the IntelSGXPSW folder.

DDU (Display Driver Uninstaller) is for removing AMD/NVIDIA/Intel video drivers and Realtek Audio Drivers so if the folder is not related to any of those, it shouldn't need access to it as it's not even related.

Accounts Add "Reset Permissions" to Context Menu in Windows 11

Attachments

Well-known member

My Computers

Administrator

My Computers

Well-known member

My Computers

Sublimed

My Computer

Administrator

My Computers

New member

My Computer

Well-known member

My Computer

Administrator

My Computers

Well-known member

My Computer

Administrator

My Computers

Well-known member

My Computer

Administrator

My Computers

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Similar Windows 11 Tutorials