NTFSSecurity Tutorial 1 – Getting, adding and removing permissions


Managing file and folder permissions in Windows PowerShell is not that easy, and there are numerous articles and blog posts describing how it works by using the .NET classes. This is far from being comfortable, and there is one major and one minor restriction:

  • Path length
  • Generic rights

This post introduces the NTFSSecurity module, which provides a bunch of cmdlets for managing permissions on NTFS drives. It does not use the Windows PowerShell way to access the file system, and it works around the MAX_PATH, which is 260 characters. (For more information, see Naming Files, Paths, and Namespaces). This is achieved thanks to AlphaFS.

This post examines displaying permissions and granting users permission.


You can download the module from the Script Center Repository: File System Security PowerShell Module. Please unblock the file before extracting it.

For more information about installing Windows PowerShell modules, see Hey, Scripting Guy! How Can I Install Windows PowerShell Modules on Multiple Users' Computers?

Some backgrounds

Windows stores the permissions in the discretionary access control list (DACL), which is part of the Security Descriptor. The Security Descriptor also includes the system access control list (SACL), where the auditing is configured, and member information. This post is about permissions and it does not discuss the SACL or member information.
The DACL contains access control entries (ACEs) that define the permissions someone has on the object. Each ACE contains the following values:

  • Account: Who is granted or denied access. Windows does not store the user’s SamAccountName, but rather, the SID.
  • Rights: The permissions granted or denied.
  • Type: Grant or deny access.
  • IsInherited: True if the ACE is inherited from a parent object.
  • InheritanceFlags and PropagationFlags: These bits control the inheritance. The NTFSSecurity module converts the bits into something more readable that is discussed later in this post.

By default, a security descriptor on the file system inherits permissions from the parent object. Users who have full access on drive C also have full access to all subfolders if the inheritance is not disabled.

Managing permissions

Reading the permissions of a single item

The first and easiest task is to retrieve the DACL from a specific file. The cmdlet that the NTFSSecurity module provides for retrieving existing permissions is Get-NTFSAccess. You can pipe a file or folder to that cmdlet or work with the Path parameter:

Get-Item D:\Data | Get-NTFSAccess

Get-NTFSAccess -Path D:\Data

The output might look like this:

The output is grouped by the file or folder, which is important when getting the permissions of more than one object. Next to the path is information about if the file or folder inherits the permissions from the parent object. My example shows that four of the displayed ACEs have been inherited from drive D.

Some more details about the columns:

  • Account: The account that has been granted or denied access to the item. As mentioned, Windows does not store the user’s name, but rather, the SID. If the SID can be translated into the name, NTFSSecurity shows it; otherwise, the SID is displayed.
  • AccessRights: These are the actual permissions that the account has been granted or denied. The list behind this field also supports generic rights.
  • Applies to: The .NET Framework stores the inheritance information in two-bit fields: InheritanceFlags and PropagationFlags. These fields are quite difficult to interpret, so NTFSSecurity converts them into something that is known from the Windows Explorer:
    • ThisFolderOnly
    • ThisFolderSubfoldersAndFiles
    • ThisFolderAndSubfolders
    • ThisFolderAndFiles
    • SubfoldersAndFilesOnly
    • SubfoldersOnly
    • FilesOnly
  • Type: Either Allow or Deny
  • Inherited: If the ACE is inherited from the parent, this is True. The first two ACEs have been defined explicitly in the folder.
  • InhertedFrom: This column only contains information if IsInherited is True, and it indicates where the ACE is inherited from.

Reading the permissions of a multiple item

All NTFSSecurity cmdlets support pipelining. If you need to get the permissions from multiple items, you do not need to run a ForEach loop. You can simply pipe the files and folders to Get-NTFSAccess.

dir C:\Data | Get-NTFSAccess

Get-NTFSAccess provides ways to filter the ACEs. A common scenario is to get the ACEs of a specific account or only those that have not been inherited.
If you want to display only permissions that have been added explicitly and hide all the inherited permissions, use the ExcludeInherited switch:

dir | Get-NTFSAccess –ExcludeInherited

If you want to display only the permissions assigned to a certain user, use the Account parameter:

dir | Get-NTFSAccess -Account raandree9\randr_000
Note: This displays the permissions as defined in the ACL. This is not the effective permissions. Effective permissions will be discussed in an upcoming post.

Granting access

Granting access to a file or folder is also quite easy to do by using the Add-NTFSAccess cmdlet. Add-NTFSAccess provides the following parameters:

  • Account: This can be a user account name (SamAccountName) or a SID. The user account name has to contain the domain (domain\username). Built-in SIDs are also supported, such as Everyone, NT AUTHORITY\SYSTEM, or BUILTIN\Administrators. For more information, see Well-known security identifiers in Windows operating systems.
  • AccessRights: This parameter takes one or more of file system rights, for example, FullControl, Modify, or Read. If you want to assign multiple rights, provide them in a comma-separated list.

Note: Use Tab expansion or the ISE to get a list of all available values.

  • AccessType: Allow or deny
  • AppliesTo: This parameter sets the scope of the ACE. The options are the same as Windows Explorer provides. By default (when not defined), the scope is ThisFolderSubfoldersAndFiles.

Note: Use Tab expansion or the ISE to get a list of all available values.

  • PassThru: By default, the cmdlet does not return any data. If the PassThru switch is used, the cmdlet displays the ACL after adding the ACE.

The next commands give the well-known group, Authenticated Users, read access to the folder C:\Data. The built-in administrators and the local group, Editors, are getting full control:

Add-NTFSAccess -Path C:\Data `

-Account 'NT AUTHORITY\Authenticated Users' `

-AccessRights Read

Add-NTFSAccess -Path C:\Data `

-Account 'BUILTIN\Administrators', 'raandree9\Editors' `

-AccessRights FullControl

Note: The modifying cmdlets of the NTFSSecurity Module do not return any data by default. If you want to get back the modified ACL, use the PassThru switch.

Removing Access

Removing access is similar to adding permissions. The command Remove-NTFSAccess takes the same parameters as Add-NTFSAccess.
To remove a user from the ACL, provide the path, the account name, and the permissions you want to remove, for example:

Remove-NTFSAccess D:\Data -Account RAANDREE0\randr_000 -AccessRights Read -PassThru

If the user has different permissions than those you want to remove, nothing happens. There needs to be an exact match.

Note: You cannot remove inherited permissions. Get-NTFSAccess informs about the source of the inherited permissions where the respective ACE can be changed or removed.

Remove-NTFSAccess accepts pipeline input. If you want to remove all permissions for a certain user account, you can read the permissions first and then pipe the results to Remove-NTFSAccess. This operation can also run reclusively:

Get-ChildItem -Path d:\ -Recurse |

Get-NTFSAccess -Account raandree0\randr_000 -ExcludeInherited |


Note: The cmdlets in the NTFSSecurity module do not provide a way to process files and folders reclusively. You have to use Get-ChildItem or Get-ChildItem2 with the Recurse switch. (The Get-ChildItem2 cmdlet is part of the NTFSSecurity module, and it will be discussed in a future post).

NTFS Inheritance

After you set permissions on a parent folder, new files and subfolders that are created in the folder inherit these permissions. If you do not want them to inherit permissions, set ApplyTo to “ThisFolderOnly” when you set special permissions for the parent folder. In cases where you want to prevent certain files or subfolders from inheriting permissions, disable (or block) the inheritance.

There are two types of permissions:

  • Explicit permissions: Set by default when the object is created by user action.
  • Inherited permissions: Propagated to an object from a parent object. Inherited permissions ease the task of managing permissions and ensure consistency of permissions among all objects within a given container.

To add an ACE that does not affect any child elements, use the following command:

Add-NTFSAccess .\Data -Account raandree1\install -AccessRights Modify -AppliesTo ThisFolderOnly

If the AppliesTo parameter is not used, the ACE applies to “ThisFolderSubfoldersAndFiles,” like when using the Windows Explorer to add permissions. All child elements will inherit the ACE created by the following command:

Add-Access -Path .\Data -Account BUILTIN\Administrators -AccessRights FullControl

To verify which child items have inherited the ACE, you can get and pipe all child elements recursively to Get-NTFSAccess. With the following command, Windows PowerShell reads only the inherited ACEs that are assigned to the built-in administrators group that are inherited from D:\Data:

dir -Recurse | Get-NTFSAccess -Account BUILTIN\Administrators -ExcludeExplicit | Where-Object InheritedFrom -eq 'D:\Data'


The next post will explore how to report, enable, and disable inheritance in folders (the NTFSSecurity module provides the same feature as the Windows Explorer). I will also discuss taking ownership of files without losing the ACL.

Comments (44)

  1. D Lee says:

    Does anyone know why I would get a number when exporting the AccessRights instead of the actual rights? If I run this:

    dir -Directory $Directory | Get-NTFSAccess | Select-Object FullName, Account, AccessRights, IsInherited | Export-Csv -Path C:\Audit\exports\test.csv

    In a console I get this:

    S:\Servicing\Clients\Deutsche Bank MMA\Shared_Servicing – Read Only ReadAndExecute, Synchronize True

    But when I use powershell to fire up excel and move it into an excel file I get this:

    S:\Servicing\Clients\Deutsche Bank NT AUTHORITY\SYSTEM 2032127 TRUE

    What’s that number?

  2. Nick says:

    I am having trouble removing FullControl permissions from a security group for a file share folder and subfolders below it. I ran the following command and let it finish, but when I look at the passthru results, no changes have been made. What could be the cause of this problem? I was able to test the command using a test user on a different directory and it worked fine.
    Here is the command I wrote:

    Remove-NTFSAccess -path ‘\\domain\Share\OfficeShare’ -Account $username -AccessRights FullControl -PassThru -Verbose

    Account Access Rights Applies to Type IsInherited InheritedFrom
    ——- ————- ———- —- ———– ————-
    Domain\OfficeGroup FullControl ThisFolderSubfoldersAn… Allow True

    VERBOSE: Disabeling all 0 enabled privileges…
    VERBOSE: …finished

  3. Niklas says:

    Hi Raimund,
    Great module, i however have some issues. I’m trying to set up access according to IGDLA.
    Ive created all groups, and all the shares, and my naming standard is L__NTFS_Read/write” and when I try to add the group access i get the following error:

    “Add-NTFSAccess : Cannot bind parameter ‘Account’. Cannot convert value “name of group” to type “Security2.IdentityReference2”. Error: “Some or
    all identity references could not be translated.”

    $folders = Get-ChildItem -Directory C:\

    foreach ($folder in $folders)
    $string1 = “L_”
    $string2 = “_NTFS_Read”
    $Read = $string1 + $folder.name + $string2


    Add-NTFSAccess $folder.fullname -Account ‘$read’ -AccessRights Read -AppliesTo ThisFolderSubfoldersAndFiles


    1. Niklas says:

      L__NTFS_Read/write *

      1. Hi Niklas,

        this means that windows could not translate the name into a SID. What happens if you cast the name into a SID manually?

        PS C:\Users\Install> [Security2.IdentityReference2]’G1 R_W’

        Sid AccountName LastError
        — ———– ———
        S-1-5-21-1637053477-203267982-1749320357-1608 G1 R_W

        Why have you put the variable $read into single quotes when invoking Add-NTFSAccess? You should not use quotes at all as using them like you did it actually makes Add-NTFSAccess look for an account named $read.


        1. Niklas says:

          HI Raimund,

          Thanks for the feedback.

          It works fine if i add the SID manually.

          The reason for my varible is that for each one of my directories i have created a local Read/write security group that i want to add as access to the specific directory. The groups naming standard include the name of the folder (e.g. L__NTFS_Read). So instead of having to add the group name manually for each access, I thought i could be solved by a foreach loop were i fetch the name in varible ($read).

          I double checked the varible and it provides the “correct name” of security group, however after you mentioned the SID, you checked and not correct SID was connected to the varible. So i did the following changes:

          $folders = Get-ChildItem -Directory C:\

          foreach ($folder in $folders)
          $string1 = “L_”
          $string2 = “_NTFS_Read”
          $Read = $string1 + $folder.name + $string2
          $SID = Get-ADGroup $read | select sid <————– to get the SID of the group, which works

          Add-NTFSAccess $folder.fullname -Account $SID -AccessRights Read -AppliesTo ThisFolderSubfoldersAndFiles


          But I now instead get the following error:
          Add-NTFSAccess : Cannot bind parameter 'Account'. Cannot convert the "@{sid=S-1-5-21-4252645733-789415554-1726247307-116
          4}" value of type "Selected.Microsoft.ActiveDirectory.Management.ADGroup" to type "Security2.IdentityReference2".
          At line:15 char:42
          + Add-NTFSAccess $folder.fullname -Account $SID -AccessRights Read -AppliesTo This …
          + ~~~~
          + CategoryInfo : InvalidArgument: (:) [Add-NTFSAccess], ParameterBindingException
          + FullyQualifiedErrorId : CannotConvertArgumentNoMessage,NTFSSecurity.AddAccess

          So it doesn't seem like it is able to add the account, even when I call the SID. If add the same SID manually, it works.


          1. Niklas says:

            name stanard of the groups shoud be L__NTFS_Read/Write .(seems like i miss this each time)

  4. Alain_P says:

    Hello Raimond,
    I’m trying to use values from an array to set rights, but this not working.
    Could you please advise me how to change my statements?

    $Folder = @(“Home”,”Profiles”)
    #Set Rights
    ForEach ($Folder in $Folder)
    Clear-NTFSAccess -Path “C:\Test\$Folder” -DisableInheritance
    Add-NTFSAccess -Path “C:\Test\$Folder” -Account ‘Administrators’,’SYSTEM’ -AccessRights FullControl
    Add-NTFSAccess -Path “C:\Test\$Folder” -Account ‘domain\Folder_M_DL’ -AccessRights Modify

    Thank you.

    1. Can you be more specific about what is not working?

      As you are doing three changed on the same folder, I would recommend working with the security descriptor to write all changes at once:

      $sd = Get-NTFSSecurityDescriptor -Path D:\test
      $sd | Disable-NTFSAccessInheritance -RemoveInheritedAccessRules
      $sd | Clear-NTFSAccess
      $sd | Add-NTFSAccess -Account SYSTEM -AccessRights FullControl -AppliesTo ThisFolderSubfoldersAndFiles
      $sd | Add-NTFSAccess -Account randr -AccessRights FullControl -AppliesTo ThisFolderSubfoldersAndFiles
      $sd | Set-NTFSSecurityDescriptor


  5. Rohin says:

    Hi Raimund, I’d like to use this module to control registry permissions via the default PSProviders, HKLM, HKCU. I was honestly surprised it didn’t just work, but it gives an error.

    “Get-Item HKLM:\SOFTWARE | Get-NTFSAccess
    Get-NTFSAccess : Unable to find the specified file.”

    Would you consider this for a future update?

    1. Sorry, this is why the cmdlets are name *-NTFS*. Nothing else as NTFS rights are supported. I know that there are some modules that handle both but this is quite hard to accomplish and has other downsides as permissions in the registry and NTFS are not the same.

      I have started a similar project for the registry. But this is not ready yet and needs someone with dev skills to take over. Interested? 🙂


  6. Rohan Jannu says:

    Hello Raimund ,
    I am wondering if Get-ChildItem2 command include the -Include parameter is it possible in next revision?
    I want to filter ChildItems with extensions.

    1. I have to admin, I have never used the Include parameter. What is your use case? Are you filtering for multiple extensions?

      1. Rohan Jannu says:

        yes I want to filter multiple Extension. how can I do that

        I tried like this:-
        Get-ChildItem2 -Path “C:\Users\Rohan-PC\Desktop” -Filter ” *.ps1, *.txt, *.pdf ” -Recurse

        but not worked for me……..results are blank only 🙁 could you please help regarding this

        1. Rohan Jannu says:

          Also tried like this:-

          Get-ChildItem2 -Path “C:\Users\Rohan-PC\Desktop” -Filter ‘ *.ps1′ ,’ *.txt,’, ‘ *.pdf ‘ -Recurse

          1. Rohan Jannu says:

            Raimund please help me 🙁

  7. Sam says:

    I tried to install the module, i go the error:

    PS C:\Windows\System32\WindowsPowerShell\v1.0> Get-Module -ListAvailable
    Get-Module : An item with the same key has already been added.
    At line:1 char:1
    + Get-Module -ListAvailable
    + ~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo : NotSpecified: (:) [Get-Module], ArgumentException
    + FullyQualifiedErrorId : System.ArgumentException,Microsoft.PowerShell.Commands.GetModuleCommand

    Any clue how to fix?

    1. Hans says:

      Sam, Did you manage to resolve this? I am getting the exact same error on one of my machines. Working fine on another…

  8. Cynthia says:

    How can I modify the below script to include: CreationTime, LastAccessTime and LastWriteTime as well as to exclude files. I just want folders and subfolders

    Get-Item D:\Data | Get-NTFSAccess

    Thanks in advance for your help!

  9. Cynthia says:

    After following the install instructions, downloading, then unblocking the module. I’m trying to run Get-NTFSAccess -Path D:\Data script to my specified drive/folder but results are:

    Get-Access : The term “Get-Access” is not recognized as the name of a cmdlet, function, script file, or operable program….

    Can you please help? Thank you in advance.

    1. I have renamed the commands long ago to meet the common PowerShell naming standard. However I did not find the time to update this article. Please use Get-NTFSAccess. All commands are matching the pattern *-NTFS*.


      1. Cynthia says:

        Thanks Raimund. It still didn’t work states “CategoryInfo: ObjectNotFound: (Get-NTFSAccess:String), CommandNotFound Exception. FullyQualifiedErrorId: CommandNotFoundException”.

        After unblocking and then extracting NTFSSecurity, the files extracted are: AlphaFS.dll, NTFSSecurity.dll, NTFSSecurity.format, NTFSSecurity.Init, NTFSSecurity, NTFSSecurity.types, NTFSSecurity-Help, PrivilegeControl.dll, ProcessPrivileges.dll and Security2.dll. Are these all the files that I should have? Am I missing any?

        I need to export all share folders, 2nd level subfolders and their corresponding permissions, access rights and if Inherited or not. I have used the below scripts but would like to have one that combines the output to a csv file. Can you please help?

        Get-ChildItem -Recurse | Select-Object -Property FullName, name, CreationTime, LastAccessTime, LastWriteTime, Attributes | Export-Csv structure.csv

        get-childitem \\fileshare\folder -recurse | get-acl | select-object path,owner,accesstostring,group | export-csv “C:\security.csv”

        Thanks again in advance for your help and information!

        1. Jonathan says:

          Did you Import the Module in order to run the cmdlet?

          Import-Module NTFSSecurity

    2. Where did you copy the files after extraction to? it should be in one of the following folders:

      C:\Program Files\WindowsPowerShell\Modules\NTFSSecurity

      Does the module show up then calling “Get-Module -ListAvailable”?

      1. Cynthia says:

        Thanks Raimund for getting back to me. It worked! I did have the files extracted to the incorrect location. I’m new to PowerShell and trying to learn due to a project I’ve been assigned. This is very helpful. I really appreciate it! Thanks again. If I come across any other questions I will definitely ask you. Thanks!

  10. Nick says:

    I am wondering if this script is expecting just a single word for the domain name.. ie. domain\user?? In my case, our domain is something.something.com or the old NETBIOS of something_com. Looks like the script doesn’t like the periods or underscores??

  11. Chris says:

    Is the module cable of handling file permissions at the very bottom of the directory tree (say you have a file that has some permissions not applied at the parent directory level). I tried using a “Get-ChildItem -Recurse ‘E:\FileShares\New folder’ | Get-NTFSAccess | Export-Csv permissions.csv” command which exports the permissions as expected. However when trying to restore the permissions I get some illegal character/ReadFileError messages because users do use wildcard characters (?,[,],etc) in there filenames.

    Add-NTFSAccess : Illegal characters: [?] in path.
    Parameter name: E:\FileShares\New folder\Recipes\Shepherd?s Pie.pdf
    At line:1 char:32
    + Import-Csv .\permissions.csv | Add-NTFSAccess
    + ~~~~~~~~~~~~~~
    + CategoryInfo : OpenError: (E:\FileShares\N…pherd?s Pie.pdf:String) [Add-NTFSAccess], ArgumentException
    + FullyQualifiedErrorId : ReadFileError,NTFSSecurity.AddAccess

    I am also attempting to replace the Fullname field in the cvs file to include opening and closing quotation marks but that does not resolve the above execution errors. Any ideas.


    1. Chris says:

      Update: I check my string conversion and there was something wrong with the code and the ending quotation mark was missing I corrected it and but the error persists (this is when using a double quotation mark). If I change this to single quotation mark encapsulation the error changes to the following.

      Add-NTFSAccess : Unable to find the specified file.
      At line:1 char:36
      + Import-Csv .\new-permissions.csv | Add-NTFSAccess
      + ~~~~~~~~~~~~~~
      + CategoryInfo : OpenError: (‘E:\FileShares\New folder\Policies’:String) [Add-NTFSAccess], FileNotFoundException
      + FullyQualifiedErrorId : ReadFileError,NTFSSecurity.AddAccess

    2. Chris says:

      I reviewed my string conversion code in the csv and corrected a mistake – no closing quotation mark. This did not resolve the issue though (this using double quotation mark). I changed the code to use single quotation marks and the error changed to the following.

      Add-NTFSAccess : Unable to find the specified file.
      At line:1 char:36
      + Import-Csv .\new-permissions.csv | Add-NTFSAccess
      + ~~~~~~~~~~~~~~
      + CategoryInfo : OpenError: (‘E:\FileShares\New folder\Policies’:String) [Add-NTFSAccess], FileNotFoundException
      + FullyQualifiedErrorId : ReadFileError,NTFSSecurity.AddAccess


      1. Sorry for the late reply. Do you still have the issue? I have done quite a lot exports / imports and did not face issues so far. To speed this up you can also reach me at raandree@live.com.

  12. Kevin says:


    Est il possible de supprimer des droits “non hérité” ?
    Je cherche sur internet mais sans succès pour le moment.


  13. jcook says:

    I am unable to simply add an account to a shared folder using this cmdlet because it is apparently trying to assign ownership even though I am just running add-ntfsaccess? Command I am running with identifying information removed is:
    add-ntfsaccess -path ‘\\\\’ -account ‘contoso\AdminAccount’ -accessrights FullControl -verbose

    Output is:
    VERBOSE: EnablePrivileges enabled in PrivateDate
    add-ntfsaccess : (1307) This security ID may not be assigned as the owner of this object:
    At line:1 char:1
    + add-ntfsaccess -path ‘\\\\’ -account “contoso\ …
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo : WriteError: (\\\!prf_dir\kchristophe:String) [Add-NTFSAccess], IOException
    + FullyQualifiedErrorId : AddAceError,NTFSSecurity.AddAccess

    VERBOSE: EnablePrivileges enabled in PrivateDate
    VERBOSE: Disabeling all 0 enabled privileges…
    VERBOSE: …finished

  14. dinh says:

    Hi there, I installed and loaded the module on a brand new Windows 10 system. But it seems that the module was not loaded correctly. the cmdlets are not recognized by Powershell.
    PS E:\users\hung>> dir2
    dir2 : The term ‘Get-ChildItem2’ is not recognized as the name of a cmdlet, function, script file, or op
    program. Check the spelling of the name, or if a path was included, verify that the path is correct and
    At line:1 char:1
    + dir2
    + ~~~~
    + CategoryInfo : ObjectNotFound: (Get-ChildItem2:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

    1. Hi,

      have you unbloked the Zip file before extracting it? If any file of the module is still blocked, loading it does not work.



  15. Auriga says:

    Is there a way to get effective rights of a given (domain) account?
    (e.g.. user x has accessrights Modify to folder y, because user x is member of group z )

  16. ohenrikh says:

    I need to set NSFS on a lot of MountPoint disks – Have you a solution for that?

  17. HELEN says:

    Thank’s a lot to Michael. Now it does work as I wanted.

  18. Hi Helen,

    like Raimund stated in his article above:

    Note: You cannot remove inherited permissions. Get-NTFSAccess informs about the source of the inherited permissions where the respective ACE can be changed or removed.

    Saying – if you want to remove an inherited permission you have to do this on the folder where the inheritance started or you break inheritance on the folder you want to handle.
    Suggesting to use Disable-Inheritance with -RemoveInheritedAccessRules switch.


    PFE | Have keyboard. Will travel.

  19. HELEN says:

    I didn’t catch how to remove all Inherited acl using this module? May be someone did it.

    I tryed this
    1. Get-NTFSAccess -Path $_.Folder | where IsInherited -eq $True | Remove-NTFSAccess

    2. Get-NTFSAccess -Path $_.Folder | Remove-NTFSAccess
    doesn’t work
    Please help.

  20. Mick6969 says:

    Sorry new to the blog, maybe changing the subject completely but I have a problem recently with turning back on my antivirus (Avast) back on on my PC’s services without this I can’t obviously ‘Tick’ both the antivirus & firewall as required to be on at
    start up & continuous can anybody help please….

  21. Frank Miller says:

    I have a very special case, I have GenericAll and FullControl for the group Everyone (S-1-1-0) in two seperate entries and i can’t delete either of it. I think it has something to do with the fact that I should delete them both at once but if I have understood
    the script correctly, it is not possible to do something like this remove-ace c:test -Account S-1-1-0 -AccessRights FullControl GenericAl

  22. Scott Abel says:

    Are you able to remove groups? I can’t seem to be able to get it to remove a group

  23. Jacques Willemen says:

    Hi Raimund as always you are doing a fantastic job.
    To avoid misunderstanding, would you mind replacing "reclusively" by "recursively", a few times in this story?

  24. Anonymous says:

    In my previous post, Use PowerShell to Get, Add, and Remove NTFS Permissions , I talked about

Skip to main content