A woman looking stressed and frustrated at a laptop

How to recusively apply NTFS permissions faster using PowerShell multithreading jobs

Do you relate to the cover photo? Have your NTFS permissions just bombed out and you can’t bare the idea of waiting hours or days for your new permissions to apply? Don’t worry, I’m here to help. It’s no secret that applying NTFS permissions to any directory tree larger than a few thousand files quickly decends in to a painstaking waiting game. The built in UI is garbage, and icacls is decent but single-threaded and slow....

<span title='2023-03-10 14:49:09 +0000 UTC'>10 March 2023</span>&nbsp;·&nbsp;5 min&nbsp;·&nbsp;868 words&nbsp;·&nbsp;Aiden Arnkels-Webb
Screenshot of Advanced NTFS Permissions

Why “traverse folder” and “execute file” is a combined NTFS permission

I’ve been asked why the Advanced Permissions dialogue on NTFS folders lists “Traverse folder / execute file” as one single permission. On the surface it seems counterintuitive that you’d allow a user to navigate through a folder, or execute its contents. There’s no official Microsoft documentation on the design decisions, however, from a filesystem perspective, entering a folder is the same as executing or running it. The same is true of 3 classic Unix filesystem flags and permissions, where the “X” flag allows both directory traversal and file execution, while “R” allows reading and “W” allows writing....

<span title='2019-12-03 13:02:00 +0000 UTC'>3 December 2019</span>&nbsp;·&nbsp;1 min&nbsp;·&nbsp;97 words&nbsp;·&nbsp;Aiden Arnkels-Webb