Windows 10: Confusion in windows NTFS permission

I have logeed in with a local account which is a member of users groups. this group member is only permission of read & execute.but this user still can able to perform write and delete jobs for same directory.i dont know how this user can perform these jobs on which he has no permission on directory.

:)

 

NTFS Permission Confuse me

1. Full control:
   
2. Modify
   
3. Read & execute:
   
4. List folder contents:
   
5. Read:
   
6. Write:
   

The write and read permission within the NFTS permission confuses me can you explain or simplify these permission in regards to a file and and folder please

 

NTFS Permissions Confusion


I clearly do not understand NTFS permissions. Can someone please help eliminate my confusion.

When I am signed in to RAVEN\Clayton (local, standard account) and I check Properties->Security on D:\Users\Clayton\Utilities, I find:





To me this indicates that SYSTEM, RAVEN\Administrators, and RAVEN\Clayton (Owner) have Full Control. Clicking Advanced and looking at Effective Access for RAVEN\Admin (local, administrators account):





To me this indicates RAVEN\Admin (a member of RAVEN\Administrators) has Full Control on D:\Users\Clayton\Utilities. All this makes sense to me.

However, if I sign in as RAVEN\Admin and click on D:\Users\Clayton, I find:





If I try to look at Properties on D:\Users\Clayton, I get:





I simply do not understand this. If RAVEN\Administrators has Full Control on D:\Users\Clayton and all its children, then why does RAVEN\Admin (a member of RAVEN\Administrators) get permission errors? Makes zero sense to me.

 

xp ntfs permissions erased - help!

NEVER, ever, remove FULL CONTROL permissions in the Access Control Lists/rights priveleges from:

• Administators Group

• YOUR local Administrator User

• SYSTEM

on NTFS rights on your disks (via Explorer.exe rightclick properties menu, security tab) that use that filesystem, OR in the REGISTRY either, via rightclick on HIVES/KEYS permissions popup menu options...

(Sure way to lock yourself out, period, & I have done it myself early on w/ NTFS filesystems &/or the Registry before... only way to learn sometimes, is making mistakes!)

* Keep this in mind, those of you that start experimenting w/ security @ these 2 levels!

APK

P.S.=> Leaving them @ FULL POWER, in both areas, usually 9/10 times allows you to get back into your rig (logging on as your LOCAL ADMINISTRATOR USER, to fix it), & make alterations to rights/acl's as needed, to "get it right", eventually... especially when you're still learning/experimenting! apk