Add missing -ProtectPrivateKey parameter to Import-PfxCertificate documentation #3977
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR Summary
Add missing

-ProtectPrivateKey
parameter to the Import-PfxCertificate cmdlet documentation.Parameter functionality is synonymous with the import option "Protect private key using virtualized-based security(Non-exportable)" in the Certificate Import Wizard:
Functionality of the option is explained by Crypt32 (Vadims Podans), creator of PSPKI:
https://security.stackexchange.com/a/186523/268642
Explanation for enum option
vsm
is hinted in the documentation for Virtualization-based Security (VBS).Virtual Secure Mode (VSM) capabilities were introduced in Windows 10 and Windows Server 2016, that is why the update only ranges until there.
PR Checklist