To help you better we need some information from you.
*** Please fill in the fields below. If you leave fields empty or specify 'latest' rather than the actual version your answer will be delayed as we will be forced to ask you for this information. ***
Product: PowerShell Studio 2022 (64 Bit)
Build: v5.8.213
OS: Windows 10 Enterprise (64 Bit)
Build: v10.0.19044.0
*** Please add details and screenshots as needed below. ***
When I run the Verify Script tool from Home/Analysis, I get the error, "Missing Cmdlets: Get-FileHash" and I would like to confirm this will not affect my compiled EXE. Thank you.
*** Tools Output window contents ***
MainForm.psf: -----------------------------------------------
MainForm.psf: Verify Script - MainForm.psf
MainForm.psf: -----------------------------------------------
MainForm.psf: Profile: Local Machine
MainForm.psf: PowerShell V5 (64 Bit)
MainForm.psf:
MainForm.psf: -----------------------------------------------
MainForm.psf: Missing Cmdlets:
MainForm.psf: -----------------------------------------------
MainForm.psf:
MainForm.psf (1498): Get-FileHash
MainForm.psf:
DO NOT POST LICENSES, KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM
Analysis - Verify Script shows a missing standard cmdlet
Forum rules
DO NOT POST LICENSE NUMBERS, ACTIVATION KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM.
Only the original author and our tech personnel can reply to a topic that is created in this forum. If you find a topic that relates to an issue you are having, please create a new topic and reference the other in your post.
Any code longer than three lines should be added as code using the 'Select Code' dropdown menu or attached as a file.
DO NOT POST LICENSE NUMBERS, ACTIVATION KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM.
Only the original author and our tech personnel can reply to a topic that is created in this forum. If you find a topic that relates to an issue you are having, please create a new topic and reference the other in your post.
Any code longer than three lines should be added as code using the 'Select Code' dropdown menu or attached as a file.
- dhatlestad
- Posts: 11
- Last visit: Thu Mar 21, 2024 7:53 am
Re: Analysis - Verify Script shows a missing standard cmdlet
Are you running PowerShell v5 or v7?
Is the cmdlet recognized in the editor when you hover over it?
Is the cmdlet recognized in the editor when you hover over it?
Brittney
SAPIEN Technologies, Inc.
SAPIEN Technologies, Inc.
- dhatlestad
- Posts: 11
- Last visit: Thu Mar 21, 2024 7:53 am
Re: Analysis - Verify Script shows a missing standard cmdlet
I am using Windows PowerShell 5.1. The editor does not highlight nor recognize Get-FileHash.
Re: Analysis - Verify Script shows a missing standard cmdlet
This should not affect your executable.
This is an issue with the editor and cache which will be addressed in a future release of PowerShell Studio.
This is an issue with the editor and cache which will be addressed in a future release of PowerShell Studio.
Brittney
SAPIEN Technologies, Inc.
SAPIEN Technologies, Inc.
- Alexander Riedel
- Posts: 8478
- Last visit: Tue Mar 26, 2024 8:52 am
- Been upvoted: 37 times
Re: Analysis - Verify Script shows a missing standard cmdlet
It seems that this is a Microsoft PowerShell bug. The cmdlet 'Get-FileHash' is not reported as an exported command.
Try this on your computer in a Windows PowerShell Console:
Try this on your computer in a Windows PowerShell Console:
- $Module = Get-Module "Microsoft.PowerShell.Utility"
- $cmdlets = Get-Command -Module $Module.Name -CommandType All
- $cmdlets.contains('Get-FileHash')
Alexander Riedel
SAPIEN Technologies, Inc.
SAPIEN Technologies, Inc.
- dhatlestad
- Posts: 11
- Last visit: Thu Mar 21, 2024 7:53 am
Re: Analysis - Verify Script shows a missing standard cmdlet
Confirmed this is as you described. Get-FileHash is not reported as a cmdlet but thankfully, it seems to be functional.
Thank you.
Thank you.
- Alexander Riedel
- Posts: 8478
- Last visit: Tue Mar 26, 2024 8:52 am
- Been upvoted: 37 times
Re: Analysis - Verify Script shows a missing standard cmdlet
We have identified the issue here. It is an interaction between PowerShell 7 and its runtime and Windows PowerShell.
We will deploy a workaround in the the next service build.
We will deploy a workaround in the the next service build.
Alexander Riedel
SAPIEN Technologies, Inc.
SAPIEN Technologies, Inc.