'You Need Permission to Perform This Action' Error: How to Fix It

Tech & Gaming
1

The “You require permission from [username/SYSTEM/TrustedInstaller] to make changes to this file” error in Windows means you don’t have sufficient permissions to modify, delete, or rename that file or folder. Here’s how to fix it.

Understanding the permission types

The error message tells you who currently owns the file:

  • [Your username]: You own it but somehow lack full control – unusual, often a corruption
  • SYSTEM: Windows system processes own it – common for OS files and program files
  • TrustedInstaller: Windows Update and component store owns it – applies to core Windows files
  • Administrators: The Administrators group owns it but your user account needs to be added

Fix 1: Take ownership via Properties

  1. Right-click the file or folder > Properties > Security tab
  2. Click Advanced > Change (next to the Owner field)
  3. Type your username > Check Names > OK
  4. Check “Replace owner on subcontainers and objects” (for folders)
  5. Click Apply > OK
  6. Back in Security tab, click Edit > select your user > check Full Control > Apply

Fix 2: Take ownership via Command Prompt (faster for folders)

Open Command Prompt as administrator and run:

takeown /f "C:\path\to/file" /r /d y
icacls "C:\path\to/file" /grant administrators:F /t

Replace the path with the actual file or folder path. The /r and /t flags apply the change recursively to all subfolders and files.

Fix 3: For TrustedInstaller-owned files

TrustedInstaller owns core Windows system files. Modifying these is generally not recommended – they’re protected for good reason. If you need to for a specific purpose, the ownership change process is the same, but be aware you’re modifying files that Windows Update may overwrite later.

Fix 4: Disable inheritance issues

Sometimes permissions are inherited from a parent folder in a way that blocks access. Advanced Security Settings > Permissions tab > Disable Inheritance > “Convert inherited permissions into explicit permissions on this object.” This gives you direct control over the permissions without relying on inheritance.

2

the TrustedInstaller warning is important. those files are protected because windows update depends on them having correct versions. taking ownership and modifying a TrustedInstaller file can cause update failures or system instability. only do it if you know specifically why you need to.

3

The inheritance issue is an underappreciated cause. A folder’s permission inheritance getting misconfigured – sometimes after software installs or Windows updates – causes files inside to have unexpected restrictions even when the parent folder looks accessible. Disabling and re-enabling inheritance resets the permissions to a known state.

4

the takeown + icacls command combination from an admin prompt is the fastest approach for folder trees. doing it through the GUI for a folder with thousands of files takes forever. the command line approach processes the whole tree in seconds.

5

This error pattern appearing on program files after an incomplete uninstall is common. The uninstaller removes some files, leaves others, and the leftover files have system or installer ownership that prevents manual cleanup. The takeown command handles this cleanly for folder cleanup purposes.

6

Worth noting that running the takeown command requires the Command Prompt to be elevated (Run as administrator). Running it as a normal user will fail silently or with an access denied error itself. Administrator prompt is the starting point for any permission repair work.