Summary

You need permission to perform this action is one message covering at least five different situations, and only one of them is a genuine permissions problem. This article works through them in the order they actually occur: a file still open somewhere, a read-only tick box, a server-side permission you cannot see locally, a protected user profile folder, and the cases where ownership genuinely has to change — with the exact ticket wording for that last one.

Symptoms

• A dialog titled Folder Access Denied or File Access Denied appears reading You need permission to perform this action, with Try Again and Cancel buttons.
• Clicking Try Again produces the identical message every time.
• Renaming, deleting, or moving works on some files in a folder and fails on others.
• A related message reads You require permission from SYSTEM to make changes to this file or names another user account.
• Saving over an existing document produces The file is read-only or prompts you to save under a different name.
• The item lives on a mapped drive, a synced SharePoint library, or a folder copied off a colleague's old laptop.

In this guide

• 1. Close the File Everywhere It Is Open
• 2. Clear the Read-only Attribute in Properties
• 3. Read the Security Tab to See What Access You Actually Have
• 4. Handle Files That Came from Another User's Profile
• 5. Files on a Network Share or SharePoint Are Decided by the Server
• 6. Ask IT to Take Ownership — With the Exact Wording

Before You Start

• Windows 11 or Windows 10, signed in with your normal work account.
• The location of the file or folder — a local drive, a mapped network drive, or a synced cloud folder. The fix branches on that, so check the address bar in File Explorer before you start.
• No admin rights required for Steps 1 to 5. Step 6 is the one that goes to IT.

Instructions

1. Close the File Everywhere It Is Open

Windows uses the same wording for "you are not allowed" and "something else is holding this". The second is far more common, so rule it out first.

1. Close the file in the app you were using — Word, Excel, Adobe Acrobat, an image viewer, whatever last touched it. Closing the document is not enough on its own; close the whole application window.
2. Turn off the File Explorer preview. In File Explorer, open the View menu on the toolbar, point to Show, and clear Preview pane. On Windows 10, open the View tab on the ribbon and untick Preview pane. The preview pane opens files to render them and holds them while they are merely selected.
3. End any leftover process. Press Ctrl + Shift + Esc to open Task Manager, select Processes in the left sidebar, and look under Background processes for an app that has no window — a crashed Microsoft Word or Adobe Acrobat entry is the usual culprit. Right-click it and select End task. The row disappears.
4. Find the holder by name if you still cannot tell. Press the Start key, type resmon, and open Resource Monitor. On the CPU tab, click the Associated Handles bar to expand it, then type the file name into the Search Handles box on the right. Every process holding that file is listed by name in the results.
5. Close the app named in those results, then try your rename or delete again. The dialog does not reappear.

Note: If the file is an Office document and the message names a person rather than an action, you are looking at a different problem with a different fix — see How to Fix "File Locked for Editing by Another User" in Office.

Verification: Right-click the file and select Rename. The name becomes editable and pressing Enter saves the new name with no dialog.

2. Clear the Read-only Attribute in Properties

A read-only file rejects every change regardless of what permissions you hold. The tick box that sets it is yours to clear.

1. Right-click the file or folder and select Properties. A window opens on the General tab.
2. Look at Attributes at the bottom of that tab. Read-only and Hidden sit side by side as tick boxes.
3. Clear the Read-only box.
4. Click Apply. On a folder, a Confirm Attribute Changes dialog appears offering Apply changes to this folder only and Apply changes to this folder, subfolders and files. Choose the second to clear the attribute on everything inside, then click OK.
5. Click OK to close Properties, then try your change again.

Note: A folder's Read-only box often appears filled with a solid square rather than a tick. That means some items inside are read-only and some are not — it is not an error. Clearing it and applying to subfolders and files resolves the mixed state.

Tip: If the box will not stay cleared and returns the moment you reopen Properties, the file is on a write-protected drive or is being opened from inside a ZIP archive rather than extracted from it. Extract the archive properly first — see How to Compress and Extract ZIP Files in Windows 11.

3. Read the Security Tab to See What Access You Actually Have

The Security tab answers the question directly, and reading it changes nothing. You can look at any file you are able to open.

1. Right-click the file or folder, select Properties, and open the Security tab.
2. Read the Group or user names list at the top. It shows entries such as SYSTEM, Administrators, Users, and named accounts. Your own account appears as your work email address or as DOMAIN\yourname.
3. Select your own name in that list, or Users if your name is not listed individually. The Permissions for pane below fills in.
4. Read the ticks in the Allow and Deny columns against each row:
   • Full control — you can do anything, including changing permissions.
   • Modify — you can edit, rename, and delete. This is what most work files need.
   • Read & execute and Read — you can open and copy, but not save changes back.
   • Write — you can add new content but not necessarily delete.
   • A tick in the Deny column beats every Allow anywhere else. One Deny entry is enough to block you completely.
5. Click Advanced to open Advanced Security Settings. Owner: appears at the very top with a Change link beside it. Note the name shown — that is who controls the file, and it is the single most useful fact to put in a ticket.
6. Open the Effective Access tab in that same window, click Select a user, type your account name, click Check Names, then OK, then View effective access. Windows lists every individual permission with a green tick or a red cross, having already worked through every group you belong to.
7. Close both windows with Cancel. Nothing you did in this step altered the file.

Note: The Edit button on the Security tab prompts for administrator credentials on a standard work account. Reading is open to you; changing is not. What you read here is what makes Step 6 fast.

4. Handle Files That Came from Another User's Profile

Windows walls off every user profile folder from every other account by design. This is why a colleague's old files behave differently from ordinary files.

1. Check the path in the File Explorer address bar. Anything under C:\Users\ followed by a name that is not yours is a protected profile folder, and so is anything copied out of one while keeping its original permissions.
2. Expect the Continue button to fail. Windows offers You don't currently have permission to access this folder with a Continue button, and that button asks for administrator credentials rather than granting access.
3. Copy rather than move where you can read the files. A copy lands in your own folder with your own permissions attached and leaves the original untouched. Right-click, select Copy, then paste into a folder under your own profile such as Documents.
4. Go to the cloud copy first when the person has left. Their work files live in their OneDrive and in the SharePoint or Teams libraries they contributed to, not only on the laptop. IT can restore a departed colleague's OneDrive to a folder you own — that is a standard request and it avoids the local permissions problem entirely.
5. Send IT this wording when the laptop really is the only copy: "I have Priya Raman's old laptop, asset tag ABC-1234. Please grant my account access to C:\Users\praman\Documents or copy its contents to a folder I own. Windows blocks me with 'You need permission to perform this action'."

Tip: Files copied off an old machine often carry the old account's permissions with them onto the new drive. Copying them a second time — from that folder into your own Documents — resets the permissions to yours and clears the error for good.

5. Files on a Network Share or SharePoint Are Decided by the Server

On a mapped drive or a synced cloud library, the answer comes from the server. Nothing you change locally has any effect on it.

1. Identify the location. A path starting \\ is a network share. A drive letter under This PC with a network cable badge on the icon is a mapped share — right-click it and select Properties to see the real \\server\share path.
2. Recognise the tell. On a share, the Security tab often shows generous permissions while the action still fails, because share-level permissions sit above the file permissions you are reading and the more restrictive of the two wins.
3. Ask the folder owner, not IT, for a departmental share. The team that owns the folder decides who writes to it, and they can usually make the change themselves within the hour.
4. Use the built-in request flow for SharePoint and OneDrive. The error page carries a text box and a Request Access button that emails the site owner directly — see How to Request Access to a SharePoint Site or File and How to Troubleshoot SharePoint "Access Denied" and Permission Errors.
5. Check you are signed in as the right account before escalating. A browser holding a personal Microsoft account or a previous employer's account produces a denial that looks identical to a genuine one — How to Fix "Access Denied" and Permission Errors in Microsoft 365 covers that check.
6. Allow time after access is granted. SharePoint and OneDrive apply changes within about 15 minutes; a Teams channel takes longer. Sign out and back in rather than waiting on a page refresh.

Note: Editing permissions on the local synced copy of a SharePoint file achieves nothing — OneDrive replaces them with the server's version at the next sync. The change has to happen in the browser, made by someone with site owner rights.

6. Ask IT to Take Ownership — With the Exact Wording

When the owner shown in Step 3 is an account nobody uses any more, ownership has to change, and only an administrator can change it. Make the ticket precise and it takes minutes.

1. Gather the four facts from Step 3: the full path to the file or folder, the Owner: name from Advanced Security Settings, the permissions your own account currently holds, and the exact text of the error.
2. Send a ticket in this form: "Please take ownership of D:\Projects\2019 Archive on my PC, asset tag ABC-1234, and grant my account Modify permission. The current owner is an account that no longer exists. I get 'You need permission to perform this action' when I try to rename or delete anything inside it."
3. Say what the files are for and when you need them. Ownership changes are quick, and a stated deadline moves the ticket up the queue — How to Submit an Effective IT Support Ticket covers what makes a request act quickly.
4. Ask for Modify, not Full control. Modify covers editing, renaming, and deleting. Full control additionally lets you change permissions, which most policies reserve for administrators and which slows approval down.
5. Confirm afterwards. Reopen the Security tab, select your name, and check that Modify now shows a tick in the Allow column.

Note: Do not run takeown or icacls commands you find online, and do not install a third-party unlocking tool. Both need administrator rights you do not have, the commands fail with Access is denied on a standard account, and installing unapproved software is a separate policy problem — see Understanding IT Policies: Why You Can't Download That App.

Troubleshooting

WARNING

Clearing Read-only and copying files are safe. Changing entries on the Security tab is not — removing a group such as SYSTEM or Administrators can lock a folder so that nobody, including IT, can reach it without a lengthy recovery. Read the Security tab freely; leave the Edit button alone and send the ticket in Step 6 instead.

Symptom / Error	Potential Cause	Solution
Error appears on every file in one folder	Folder marked read-only, or a Deny entry	Clear Read-only on the folder and apply to subfolders and files (Step 2), then check for Deny ticks on the Security tab (Step 3).
Error on one file only, others fine	That file is still open somewhere	Find the process holding it with Resource Monitor (Step 1) and close that app.
You require permission from SYSTEM	Protected system or profile location	Copy the file to your own Documents folder and work on the copy (Step 4). Never alter permissions on a system folder.
Changes save but revert on their own	Local copy of a server-controlled file	The permission lives on the server, not your PC (Step 5). Request access through SharePoint rather than editing the synced copy.
Error when saving to Documents or Desktop	Controlled folder access is blocking the app	Open Windows Security > Virus & threat protection > Ransomware protection and check whether Controlled folder access is on. Ask IT to allow the app through it.
Rename fails and the path is very long	Path length, not permissions	Check the path length before assuming a permission problem — see How to Fix "File Path Too Long" Errors on Windows.

Related Articles

• How to Fix "File Locked for Editing by Another User" in Office
• How to Fix "Access Denied" and Permission Errors in Microsoft 365
• How to Troubleshoot SharePoint "Access Denied" and Permission Errors
• How to Request Access to a SharePoint Site or File
• Understanding File Sharing and Permissions in Microsoft 365
• How to Fix "File Path Too Long" Errors on Windows
• How to Submit an Effective IT Support Ticket

Did this solve your problem?