An Error Occurred While Applying Security Information To The File

Visible text word count: 1800

This Windows message means a permission or ownership block; taking ownership, resetting ACLs, or releasing a lock usually clears it.

You’ll see this when you try to change a folder’s permissions in the file window and Windows can’t push the new rules to each item. It starts writing access entries, hits a file or subfolder it can’t edit, then stops with the “an error occurred while applying security information to the file” message.

The fix is usually straightforward. You become the owner, remove a deny entry, stop a process that’s holding the file open, or reset the access list back to a clean state. Start with the safer checks, then move to the deeper repairs.

What This Message Is Telling You

Windows controls access with ownership and permissions. Ownership decides who can edit the permission list. Permissions decide who can read, write, delete, or run the file. When you click Apply, Windows tries to write a new list, then copy it down into subfolders and files.

If you’re not the owner, or your account lacks rights to edit that list, Windows can’t finish the job. Admin sign-in alone may not be enough, since many folders are owned by the system or a service account.

Behind the scenes, the permission list is an access control list (ACL). It contains entries that allow or deny actions for users and groups. When you change a parent folder and choose to apply it to subfolders, Windows must rewrite ACL entries on each child item. One stubborn file can stop the whole run, so the message is often less about the folder you clicked and more about one child that refuses the change.

Check the exact file named in the error — If the dialog lists a path, copy it into the file window and work with that one item first.
Look for Deny entries on that item — A Deny rule applied directly to the file can block edits even when the parent folder looks fine.

Common Causes You Can Spot Fast

The file is in use — A running app, sync client, backup tool, or preview pane may be holding it open.
The owner is blocked — The folder is owned by TrustedInstaller, SYSTEM, another user, or an unknown SID.
A deny entry exists — An explicit Deny rule overrides allow rules and can stop changes from applying.
Inheritance is broken — Child items have custom access lists that resist the parent’s changes.

What You See	Likely Cause	What To Try
“Access is denied” on one item	Owner or permission block	Take ownership, then grant access
Fails across many subfolders	Broken inheritance	Enable inheritance, replace child entries
Stops on a single deep file	Lock or long path	Close apps, reboot, or try Safe Mode

Quick Checks Before You Change Anything

Do these checks first. They cut wasted time.

Confirm Your Account Can Edit Permissions

On Windows, an administrator account can still act like a standard user until you approve a UAC prompt. If the Security dialog never asks for approval, you might be editing with a limited token. Switching to the command-line steps later in this guide forces the admin prompt and can succeed when the file window dialog stalls.

You can sanity-check your work after changes. In Advanced Security Settings, use the Effective Access view to see what rights a user or group has on the folder. If it shows Read and Execute only, your edits did not land.

Confirm the target path — Make sure it’s your data folder, not a system path like Windows or Program Files.
Close anything that could touch it — Exit apps, pause sync, and close preview panes.
Try a reboot — A restart clears stuck handles and refreshes access tokens.
Copy the folder as insurance — If it holds work files, copy it to another drive first.

If the error shows up during delete, test a rename. A rename failure often means something still has the folder open.

An Error Occurred While Applying Security Information To The File On Windows

Most fixes work in Advanced Security Settings. The goal is to claim ownership, fix inheritance, then apply a permission set that matches what you’re doing.

Take Ownership From The Advanced Dialog

Ownership comes first. Once you own the folder, Windows will let you edit its permission list without tripping over “access denied.”

Open Properties — Right-click the folder, choose Properties, then open the Security tab.
Enter Advanced Security Settings — Click Advanced to open the detailed view.
Change the owner — Click Change next to Owner, type your username or Administrators, then confirm.
Apply to child items — Tick “Replace owner on subcontainers and objects” when you want the whole tree updated.
Apply and reopen — Click Apply, close the window, then open Advanced again so the new owner loads.

Fix Inheritance And Replace Child Entries

If a folder has many items with custom access lists, Windows may fail while trying to push your change to each child. Turning on inheritance can standardize the tree.

Enable inheritance — Click “Enable inheritance” if it appears.
Replace child permissions — Use “Replace all child object permission entries with inheritable permission entries from this object” when you want one consistent set.
Remove deny rules that target you — Deny beats allow, so remove or narrow Deny entries that block your account.

Grant The Access You Actually Want

After ownership and inheritance are handled, grant access with a light touch. Full control is fine for a personal folder, yet it’s a bad idea on system folders.

Use Modify for shared folders — Modify lets people work with files without handing out permission to rewrite the whole permission list.
Keep SYSTEM and Administrators present — Windows services rely on these entries.
Remove unknown SIDs carefully — If a SID no longer maps to a user, removing it can help once you’ve confirmed the folder is not tied to an app.

Fixing The Error With Command Prompt

If the file window dialog won’t apply changes, the command line can. Two built-in tools handle most cases: takeown for ownership and icacls for editing or resetting access control lists. Run them from Command Prompt or Windows Terminal started as administrator.

Take Ownership With Takeown

Microsoft documents takeown as a way for an admin to regain access by making an admin the owner of a file or folder. Use /a when you want the Administrators group as the owner. The /r switch walks subfolders and files.

Open Command Prompt as administrator — Search for Command Prompt, right-click it, then choose Run as administrator.
Take ownership of a folder tree — takeown /f "D:\Path\Folder" /a /r /d y
Take ownership of one file — takeown /f "D:\Path\File.ext" /a

Repair Permissions With Icacls

Icacls can grant rights, fix inheritance, and reset permissions. A reset is often the cleanest path when the access list is tangled after software moves or manual edits.

Grant Full control to your account — icacls "D:\Path\Folder" /grant "%USERNAME%":(F) /t
Reset permissions across the tree — icacls "D:\Path\Folder" /reset /t /c
Enable inheritance — icacls "D:\Path\Folder" /inheritance:e /t

When you use icacls, a few switches matter. /t walks the folder tree, /c keeps going when one file fails, and /reset restores inherited defaults on each item. On a shared folder, run a reset, then grant only the group rights you need.

If icacls fails on one file, it prints that file’s path. Fix that one item, then rerun the command. This approach keeps you from changing more than you meant to change.

Stubborn Cases That Stop Permission Changes

Some folders behave differently. The same error can show up after you take ownership because a service keeps resetting permissions, or because the file has encryption or extra protection rules.

System And App Package Folders

Folders under Windows, Program Files, and WindowsApps are meant to be controlled by the operating system. Changing owners there can break updates, app launches, or Store installs. If you’re working in one of these paths, narrow your edits to the one file you must touch, then put the owner back when you’re done.

Try app repair tools first — Use Windows Settings repair or reinstall options for the affected app.
Undo ownership changes after the task — Set the owner back to the original account once cleanup is finished.

Encrypted Files And Security Tools

If a file was encrypted with EFS, permissions alone may not grant access without the right certificate. Antivirus tools and ransomware protection features can block changes to protected folders, too.

Check for encryption — In file properties, advanced attributes can show encryption status on some systems.
Pause protection briefly — If a security tool is blocking permission edits, pause it, apply the change, then turn it back on right away.

Locked Files, Sync Conflicts, And Long Paths

A locked file is one a process is still using. Sync tools can keep files busy, and long paths can trip older apps. If you see the error on one deep item, reduce variables and retry.

Close sync and backup apps — Pause OneDrive, cloud drives, and backup tools that scan the folder.
Try Safe Mode — Safe Mode loads fewer services, so fewer things can hold the file open.
Move the folder higher — Copy it to a short path like D:\Temp, then retry.

Disk And File System Issues

If permission changes fail across random files on the same drive, check the file system. Windows must write security metadata, so a damaged file system can block updates.

Run a scan — Use the drive’s Tools tab to scan and repair file system errors.
Run chkdsk if needed — From a terminal started as administrator, run chkdsk /f on the affected drive.

Safer Habits So The Error Doesn’t Return

After the fix, keep permission work limited to folders you control. This reduces repeat issues and helps you avoid breaking system-managed paths.

Keep projects in a folder you own — A dedicated data folder on D: is easier to manage than Program Files.
Use new folders for messy leftovers — Move your files out, then delete the old folder once nothing is using it.
Grant access to a group — Use Users or a named group when sharing across accounts on the same PC.
Write down the commands you ran — A short note makes rollback work faster later.

If you hit the message again, or you see “an error occurred while applying security information to the file” on a new folder, follow the same order: clear locks, fix ownership, straighten inheritance, then use takeown and icacls when the UI refuses. In most cases, that sequence gets the folder working again without extra drama.