Downloads of v 4.2.4:


Last Update:

29 Aug 2018

Package Maintainer(s):

Software Author(s):

  • Raimund Andrée


randree nttfssecurity security ntfs permissions powershell

File System Security PowerShell Module (Install)

4.2.4 | Updated: 29 Aug 2018



Downloads of v 4.2.4:



Software Author(s):

  • Raimund Andrée

File System Security PowerShell Module (Install) 4.2.4

This Package Contains an Exempted Check

1 Test Passing and 1 Exempted Test

Validation Testing Passed

Verification Testing Exempt:

Requires PowerShell 5

To install File System Security PowerShell Module (Install), run the following command from the command line or from PowerShell:


To upgrade File System Security PowerShell Module (Install), run the following command from the command line or from PowerShell:


To uninstall File System Security PowerShell Module (Install), run the following command from the command line or from PowerShell:


NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Enter your internal repository url

(this should look similar to

4. Choose your deployment method:

choco upgrade ntfssecurity-psmodule -y --source="'STEP 3 URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:

choco upgrade ntfssecurity-psmodule -y --source="'STEP 3 URL'"

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0

Exit $exitCode

- name: Ensure ntfssecurity-psmodule installed
    name: ntfssecurity-psmodule
    state: present
    version: 4.2.4
    source: STEP 3 URL

See docs at

Coming early 2020! Central Managment Reporting available now! More information...

chocolatey_package 'ntfssecurity-psmodule' do
  action    :install
  version  '4.2.4'
  source   'STEP 3 URL'

See docs at

    Name: ntfssecurity-psmodule,
    Version: 4.2.4,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller ntfssecurity-psmodule
   Name     = 'ntfssecurity-psmodule'
   Ensure   = 'Present'
   Version  = '4.2.4'
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

package { 'ntfssecurity-psmodule':
  provider => 'chocolatey',
  ensure   => '4.2.4',
  source   => 'STEP 3 URL',

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install ntfssecurity-psmodule version="4.2.4" source="STEP 3 URL"

See docs at

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package was approved by moderator gep13 on 31 Aug 2018.


Managing permissions with PowerShell is only a bit easier than in VBS or the command line as there are no cmdlets for most day-to-day tasks like getting a permission report or adding permission to an item. PowerShell only offers Get-Acl and Set-Acl but everything in between getting and setting the ACL is missing. This module closes the gap.

The module provides 10 cmdlets to manage permissions on the file system, like adding and removing ACEs, setting the inheritance, getting the current permissions or even get the effective permissions for a certain user. The available cmdlets are listed below with a short description. More information can be retreived in the PowerShell using Get-Help.

  • Add-NTFSAccess - Adds a specific ace to the current object.
  • Get-NTFSAccess - Gives you a list of all permissions.
  • Get-NTFSOrphanedAccess - Lists all permissions that can no longer be resolved.
  • Remove-NTFSAccess - Removes the permission for a certain account.
  • Get-NTFSEffectiveAccess - Shows the permissions an account actually has on a file or folder.
  • Get-NTFSInheritance - Shows if inheritance is blocked
  • Enable-NTFSInheritance - It can be a problem if certain files or folders on a volume have inheritance disabled. Making sure that inheritance is enabled can be done using this cmdlet
  • Disable-NTFSInheritance - see Enable-NTFSInheritance
  • Get-NTFSOwner - Shows the owner of a file or folder.
  • Set-NTFSOwner - Sets the owner to a specific account.

For documentation please refer to:
NTFSSecurity Tutorial 1 - Getting, adding and removing permissions
NTFSSecurity Tutorial 2 - Managing NTFS Inheritance and Using Privileges


Click here to Patreon-ize the package maintainer.

$ErrorActionPreference = 'Stop'
$packageName = 'ntfssecurity-psmodule'

$PSversion = $PSVersionTable.PSVersion.Major
if ($PSversion -lt "5")
    Write-Warning "PowerShell < v5 detected."
	Write-Warning "$packageName installs via the PowerShell Gallery and thus PowerShell v5 is a prerequisite."
	Write-Warning "If PowerShell v5 was installed as a dependency, you need to reboot and reinstall this package."

# Will fail if packageVersion is a revised version not matching module version, i.e. x.x.x.0020180101
if (Get-Module -ListAvailable -Name NTFSSecurity -ErrorAction SilentlyContinue){
     Update-Module "NTFSSecurity" -RequiredVersion "$env:packageVersion" -Force
   } else {   
     Get-PackageProvider -Name NuGet -Force
     Install-Module -Name NTFSSecurity -Scope AllUsers -RequiredVersion $env:packageVersion -AllowClobber -Force
     Import-Module NTFSSecurity
$ErrorActionPreference = 'Stop'
$packageName = 'ntfssecurity-psmodule'

Uninstall-Module -Name "NTFSSecurity" -Force

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version Downloads Last Updated Status
File System Security PowerShell Module (Install) 4.2.3 326 Friday, February 2, 2018 Approved
Discussion for the File System Security PowerShell Module (Install) Package

Ground Rules:

  • This discussion is only about File System Security PowerShell Module (Install) and the File System Security PowerShell Module (Install) package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or File System Security PowerShell Module (Install), or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus