update-PWFolderSecurity not found.

I will try the 64 bit angle...the hyphen; there or not, gave me the same error... Thanks!

I will try the 64 bit angle...the hyphen; there or not, gave me the same error... Thanks!

ok, I uninstalled the x86 and set up the 64 bit....same error (with Hyphen)

PS C:\PS> Update‐pwfolderSecurity

Update‐pwfolderSecurity : The term 'Update‐pwfolderSecurity' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was
included, verify that the path is correct and try again.
At line:1 char:1
+ Update‐pwfolderSecurity
+ ~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (Update‐pwfolderSecurity:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

PS C:\PS> get-help pwfoldersecurity
Security Protocol now set to TLS 1.2
PWPS_DAB Version is 2.0.6.0
This is a 64-bit process.

Name Category Module Synopsis
---- -------- ------ --------

Update-PWFolderSecurity Cmdlet pwps_dab UpdatePWFolderSecurity is used to add user(s), group(s), or userlist(s) access control to specified folders.

Are all cmdlets doing this? Can you Try New-Pwlogin and see if its the same? 

When I import I do the following as Administrator 64 bit Powershell. (You need to be administrator)

Install-Module PWPS_DAB -Force -Verbose

Import-Module PWPS_DAB -Force -Verbose

I think it is "case"...

<lowercase PWF...>

PS C:\PS> Update‐pwfolderSecurity
Update‐pwfolderSecurity : The term 'Update‐pwfolderSecurity' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was
included, verify that the path is correct and try again.
At line:1 char:1
+ Update‐pwfolderSecurity
+ ~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (Update‐pwfolderSecurity:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

<uppercase PWF...>

PS C:\PS> Update-PWFolderSecurity
Update-PWFolderSecurity : Parameter set cannot be resolved using the specified named parameters.
At line:1 char:1
+ Update-PWFolderSecurity
+ ~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidArgument: (:) [Update-PWFolderSecurity], ParameterBindingException
+ FullyQualifiedErrorId : AmbiguousParameterSet,PWPS_DAB.UpdatePWFolderSecurity

It "finds it" now... I don't recall ever having case issues...maybe I was just lucky and always got the case .."just right"???

...thanks for the help! I'm off to the next tree to slam into.."Yoiks and away"

(assumption on the Looney tune literacy :-D)

Bob

I copied your first example and the issue seemed to be the -

When I copied the dash it was shorter then the dash I use. I have no idea how that happened.

If you copy both cmdlets into powershell you'll see what I mean.

yeah, the hyphen definitely needs to be in there...that example without the hyphen was a test someone else observer from the documentation of the cmdlet...a test that didn't work ;-)   It just got caught up in my capture, but thanks, you are absolutely correct. ( I wouldn't want anyone to fall down that rabbit hole).

It seems the real problem for me was the case of the Text:

"Update‐pwfolderSecurity" did not work......

however

"Update-PWFolderSecurity" does work

??? 

interesting....because

"New-Pwlogin"  works

but so does "new-pwlogin"....

maybe there are some aliases "lurking about"...

my "takeaway"...sometimes CMDlets ARE case-sensitive...(note to self)

The way I finally figured it out was to use "intellisense"...I selected from the list and it worked...then compared it to what had been failing.

I will be using that in the future.

I appreciate your comments with this....they were a BIG help!

Bob