Get-Acl should produce nonterminating errors when it fails to access a file or directory - by David Wyatt

Status : 


Sign in
to vote
ID 794618 Comments
Status Active Workarounds
Type Bug Repros 4
Opened 7/19/2013 9:15:41 PM
Access Restriction Public


Get-Acl currently throws terminating errors anytime it fails to access a file or directory, even though it accepts an array of strings for the Path / LiteralPath parameters, and accepts pipeline input.  Per Microsoft's guidelines for cmdlet error reporting (, it seems like these should be non-terminating errors, as they are related to a specific input object, and should not prevent processing of more input objects.

It is currently only possible to work around this issue by piping objects to ForEach-Object (instead of directly to Get-Acl), and in the foreach block, call Get-Acl once for each object.
Sign in to post a comment.