Windows 10: PowerShell "Get-Command -Verb Get" format different from documentation

According to the documentation for PowerShell 6, the PowerShell command "Get-Command -Verb Get" should output a format similar to:

CommandType Name Definition

----------- ---- ----------
Cmdlet Get-Acl Get-Acl [[-Path] <String[]>]...
Cmdlet Get-Alias Get-Alias [[-Name] <String[]...
Cmdlet Get-AuthenticodeSignature Get-AuthenticodeSignature [-...
Cmdlet Get-ChildItem Get-ChildItem [[-Path] <Stri...
...


However, when I enter the same command in either the default version of Windows PowerShell or PowerShell 6.2.3, it's headinglooks like


CommandType Name Version Source
----------- ---- ------- ------

Function Get-AppBackgroundTask 1.0.0.0 AppBackgroundTask
Function Get-AppxLastError 2.0.1.0 Appx
Function Get-AppxLog 2.0.1.0 Appx


It doesn't show the Definition (syntax) as shown in the documentation. Is the documentation wrong, or does it apply yet another version of PowerShell?

:)

 

PowerShell Bitlocker command uses unaproved verbs and verbosity setting

If I have this statement at the start of a script:

#requires -Version 3.0 -Modules BitLocker, Hyper-V, Storage

I see this message when I run the script:

WARNING: The names of some imported commands from the module 'BitLocker' include unapproved verbs that might make them

less discoverable. To find the commands with unapproved verbs, run the Import-Module command again with the Verbose

parameter. For a list of approved verbs, type Get-Verb.

I also find that if I want to use:

Write-Verbose

Statements to debug the script if:

$VerbosePreference = 'Continue'

The BitLocker CmdLets hang and do not appear complete.

If I set:

$VerbosePreference = 'SilentlyContinue'

Everything works as expected.

I am running the script as a normal user with an elevated PowerShell process doing the work using a named pipe for communication.

Any thoughts?

Win10/64 V1803 17134.166

 

PowerShell Bitlocker command uses unaproved verbs and verbosity setting

Sorry, I understand what you have said but BitLocker PowerShell CmdLets are built into Windows - I am doing nothing to import, load or anything else. The naming convention issue is NOT of my making.

This message should IMHO not occur if Microsoft are following their own naming conventions.

PS C:\WINDOWS\system32> Import-Module -name bitlocker

VERBOSE: Loading module from path 'C:\WINDOWS\system32\WindowsPowerShell\v1.0\Modules\bitlocker\bitlocker.psd1'.

VERBOSE: Loading 'FormatsToProcess' from path

'C:\WINDOWS\system32\WindowsPowerShell\v1.0\Modules\bitlocker\BitLocker.Format.ps1xml'.

VERBOSE: Loading module from path

'C:\WINDOWS\system32\WindowsPowerShell\v1.0\Modules\bitlocker\Microsoft.BitLocker.Structures.dll'.

VERBOSE: Loading module from path 'C:\WINDOWS\system32\WindowsPowerShell\v1.0\Modules\bitlocker\BitLocker.psm1'.

VERBOSE: Exporting function 'Get-ExceptionForHrInternal'.

VERBOSE: Exporting function 'IsNanoPowerShell'.

VERBOSE: Exporting function 'Decrypt-SecureStringInternal'.

VERBOSE: Exporting function 'Get-Win32EncryptableVolumeInternal'.

VERBOSE: Exporting function 'Read-UserSecretInternal'.

VERBOSE: Exporting function 'Get-BitLockerVolumeInternal'.

VERBOSE: Exporting function 'Get-BitLockerVolume'.

VERBOSE: Exporting function 'Suspend-BitLocker'.

VERBOSE: Exporting function 'Resume-BitLocker'.

VERBOSE: Exporting function 'Lock-BitLocker'.

VERBOSE: Exporting function 'Unlock-PasswordInternal'.

VERBOSE: Exporting function 'Unlock-RecoveryPasswordInternal'.

VERBOSE: Exporting function 'Unlock-RecoveryKeyInternal'.

VERBOSE: Exporting function 'Unlock-BitLocker'.

VERBOSE: Exporting function 'Add-RecoveryPasswordProtectorInternal'.

VERBOSE: Exporting function 'Add-PasswordProtectorInternal'.

VERBOSE: Exporting function 'Remove-KeyProtectorByTypeInternal'.

VERBOSE: Exporting function 'Add-TpmProtectorInternal'.

VERBOSE: Exporting function 'Add-TpmAndPinProtectorInternal'.

VERBOSE: Exporting function 'Add-TpmAndStartupKeyProtectorInternal'.

VERBOSE: Exporting function 'Add-TpmAndPinAndStartupKeyProtectorInternal'.

VERBOSE: Exporting function 'Add-ExternalKeyProtectorInternal'.

VERBOSE: Exporting function 'Add-SidProtectorInternal'.

VERBOSE: Exporting function 'Add-BitLockerKeyProtector'.

VERBOSE: Exporting function 'Remove-BitLockerKeyProtector'.

VERBOSE: Exporting function 'Backup-BitLockerKeyProtector'.

VERBOSE: Exporting function 'BackupToAAD-BitLockerKeyProtector'.

VERBOSE: Exporting function 'Enable-BitLockerAutoUnlock'.

VERBOSE: Exporting function 'Disable-BitLockerAutoUnlock'.

VERBOSE: Exporting function 'Disable-BitLocker'.

VERBOSE: Exporting function 'Clear-BitLockerAutoUnlock'.

VERBOSE: Exporting function 'Unlock-AdAccountOrGroupInternal'.

VERBOSE: Exporting function 'Test-SystemEntropyForBitLockerInternal'.

VERBOSE: Exporting function 'Test-TpmProtectorNeededInternal'.

VERBOSE: Exporting function 'Test-TpmForBitLockerInternal'.

VERBOSE: Exporting function 'Enable-BitLockerInternal'.

VERBOSE: Exporting function 'Show-BitLockerRequiredActionsInternal'.

VERBOSE: Exporting function 'Get-RecoveryKeyProtectorsCountInternal'.

VERBOSE: Exporting function 'Set-BitLockerVolumeInternal'.

VERBOSE: Exporting function 'Enable-BitLocker'.

VERBOSE: Importing function 'Add-BitLockerKeyProtector'.

VERBOSE: Importing function 'Backup-BitLockerKeyProtector'.

WARNING: The names of some imported commands from the module 'bitlocker' include unapproved verbs that might make them

less discoverable. To find the commands with unapproved verbs, run the Import-Module command again with the Verbose

parameter. For a list of approved verbs, type Get-Verb.

VERBOSE: The 'BackupToAAD-BitLockerKeyProtector' command in the bitlocker' module was imported, but because its name

does not include an approved verb, it might be difficult to find. For a list of approved verbs, type Get-Verb.

VERBOSE: Importing function 'BackupToAAD-BitLockerKeyProtector'.

VERBOSE: Importing function 'Clear-BitLockerAutoUnlock'.

VERBOSE: Importing function 'Disable-BitLocker'.

VERBOSE: Importing function 'Disable-BitLockerAutoUnlock'.

VERBOSE: Importing function 'Enable-BitLocker'.

VERBOSE: Importing function 'Enable-BitLockerAutoUnlock'.

VERBOSE: Importing function 'Get-BitLockerVolume'.

VERBOSE: Importing function 'Lock-BitLocker'.

VERBOSE: Importing function 'Remove-BitLockerKeyProtector'.

VERBOSE: Importing function 'Resume-BitLocker'.

VERBOSE: Importing function 'Suspend-BitLocker'.

VERBOSE: Importing function 'Unlock-BitLocker'.

PS C:\WINDOWS\system32>

This one looks like it causes the issue:

WARNING: The names of some imported commands from the module 'bitlocker' include unapproved verbs that might make them

less discoverable. To find the commands with unapproved verbs, run the Import-Module command again with the Verbose

parameter. For a list of approved verbs, type Get-Verb.

VERBOSE: The 'BackupToAAD-BitLockerKeyProtector' command in the bitlocker' module was imported, but because its name

does not include an approved verb, it might be difficult to find. For a list of approved verbs, type Get-Verb.

VERBOSE: Importing function 'BackupToAAD-BitLockerKeyProtector'.

If Verbose is on all CmdLets I have used do not output ANY verbose statements but BitLocker does.

Try setting $VerbosePreference to 'Continue' and then with one of your own BitLocker disks or VHD which is not unlocked try:

Code:

Unlock-BitLocker -MountPoint '<path>' -Password ((Get-Credential -UserName 'Do Not Change' -Message 'Enter the Password').GetNetworkCredential().password |ConvertTo-SecureString -AsPlainText -Force)

Where <path> is a directory not just a drive letter and see the stream of output that I think is causing the issue.

 

PowerShell instead of Commandline in Creators Update

Interestingly enough my personal laptop just got the update...and still has Command Prompt listed, not PowerShell...

Edit: Not that it matters...I use both regularly. *Toast :toast: