Shared Folder Access Denied Fix Check Share and NTFS Permissions
You set the permission yourself, the user is in the list — and Windows still says Access Denied. That error is almost never random. It means one of two permission lists is still saying no, and this page checks both, in order.
✍️ Technical Anshu🪟 Windows 10 / 11⏱️ 7 minute fix
🎥 Full video — how access control on shared folders really works
The message is always the same and always unhelpful: “You do not have permission to access this folder.” What it hides is that two separate lists were checked — the share permission and the NTFS permission — and a “no” in either one wins. Most people keep editing the list that is already fine. Work through the four checks below and you will find the one that is actually blocking.
Network Error (example)
Windows cannot access \\OFFICE-PC\Accounts
You do not have permission to access \\OFFICE-PC\Accounts. Contact your network administrator to request access.
The two lists checked before this message appears
1. Share permissionSharing tab
2. NTFS permissionSecurity tab — stricter one wins
The standard Windows access denied message for a shared folder. PC and folder names are examples.
1
Check the Effective Access First — It Tells You the Truth
On the PC that holds the folder, right-click it → Properties → Security → Advanced
Open the Effective Access tab and select the exact user who is failing
The list shows what that user truly gets, after groups, denies and inheritance are all combined
If Effective Access already shows the right they need, the block is in the share permission or the connection itself — keep going below. If it shows less, the NTFS list is your problem.
2
Check 1 — The Share Permission
Open fsmgmt.msc → Shares → right-click your share → Properties
On Share Permissions, confirm the user — or a group they belong to — is listed with at least the level they need
Remember the scale: Read opens files, Change edits and deletes, Full Control also changes permissions
3
Check 2 — The NTFS Permission and the Deny Trap
Folder Properties → Security tab. Confirm the same user or group appears here too — being in only one list is not enough
Look for any Deny entry. An explicit Deny beats every Allow, even an administrator's: a "Deny: Write" on a big group (like Everyone or Users) silently blocks people you allowed by name
Check whether the folder inherited its list from a locked parent folder — click Advanced and see where each entry says "Inherited from"
4
Check 3 — Windows Is Using the Wrong Saved Password
A very common fake "permission" problem: the visiting PC saved an old or guest login for this server and keeps retrying it silently.
On the visiting PC, open Credential Manager → Windows Credentials and remove any entry for the file PC's name
Disconnect the old session: run net use * /delete in Command Prompt
Open the share again and log in with the correct account — tick "Remember" only once it works
5
Check 4 — The Account Itself
Confirm the account exists on the PC that holds the files (sharing accounts live there, not on the visitor's PC), that it has a password, and that it is not disabled or locked. Also confirm the user is actually in the group you granted — group changes need a fresh logon on the visiting PC before they apply.
🔴 Never “fix” this by adding Everyone with Full Control. That removes the error by removing all security — every PC on the network, including a guest's laptop, can then read and delete the folder. Find the one list that is wrong instead; it is one of the four checks above.
🎥 Watch the Full Video
The video shows the permission screens live — how the share list and the Security tab combine, and how admins grant access without opening the door to everyone.
Why does the admin account open the folder but a staff account cannot?
Administrators usually reach the folder through their own group entry, which may be the only correct one. The staff account depends on the entry you made for it — check Effective Access for that exact account to see what it really receives.
I changed the permission but the user still gets Access Denied. Why?
Two usual reasons: the visiting PC is still logged in with cached credentials (clear them with Credential Manager and net use), or the user was added to a group after logging in — group membership is read at logon, so sign out and back in on the visiting PC.
Does restarting the file PC help?
Rarely. Permissions apply immediately. A restart only helps clear stuck sessions — and the same result comes faster from fsmgmt.msc, where you can see and close open sessions and open files per user.
This guide is based on the Technical Anshu advanced sharing video • Stuck on any step? Ask in the video comments — you will get a reply there 🙏