Skip to content

New-SelfSignedCertificate doesn't exist on windows #6656

@ForkBug

Description

@ForkBug

Type New-SelfSignedCertificate, we got

PS C:\Program Files\PowerShell\6.0.2> New-SelfSignedCertificate
New-SelfSignedCertificate : The term 'New-SelfSignedCertificate' 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

  • New-SelfSignedCertificate
  • CategoryInfo : ObjectNotFound: (New-SelfSignedCertificate:String) [], CommandNotFoundException
  • FullyQualifiedErrorId : CommandNotFoundException

At least it should work on windows 2016

Metadata

Metadata

Assignees

No one assigned

    Labels

    Issue-Questionideally support can be provided via other mechanisms, but sometimes folks do open an issue to get aResolution-ExternalThe issue is caused by external component(s).

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions