Repository navigation
Running powershell -command 'Get-FileHash' fails #8635
Description
Steps to reproduce
powershell -noprofile -command "(get-filehash $PSHOME\powershell.exe).hash"Expected behavior
DE96A6E69944335375DC1AC238336066889D9FFC7D73628EF4FE1B1B160AB32C
Actual behavior
get-filehash : The term 'get-filehash' 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:2
+ (get-filehash C:\Windows\System32\WindowsPowerShell\v1.0\powershell.e ...
+ ~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (get-filehash:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
Actual behavior on a different computer
get-filehash : The 'get-filehash' command was found in the module 'Microsoft.PowerShell.Utility', but the module could
not be loaded. For more information, run 'Import-Module Microsoft.PowerShell.Utility'.
At line:1 char:2
+ (get-filehash $pshome\powershell.exe).hash
+ ~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (get-filehash:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CouldNotAutoloadMatchingModule
Environment data
Name Value
---- -----
PSVersion 6.1.1
PSEdition Core
GitCommitId 6.1.1
OS Microsoft Windows 10.0.17763
Platform Win32NT
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
WSManStackVersion 3.0
Activity
1480c1 commentedon Jan 13, 2019
Additional notes:
powershell -noprofile -command '$PSVersionTable'in powershell core outputs:kvprasoon commentedon Jan 14, 2019
This fails when the call is from PS Core. Below are some observations.
powershell -noprofile -command "gcm get-file*"mklement0 commentedon Jan 14, 2019
If you invoke
powershell.exefrom PowerShell Core, the problem is the presence of the Core standard module path in$env:PSModulePathbefore the Windows PowerShell standard module path, which causes Windows Powershell not to findGet-FileHash.You can verify this as follows:
Conversely, prepending the Core module path provokes the symptom:
Your second error message is more accurate and helpful, as it indicates that the command was found, but that its enclosing module failed to load (presumably because the module is a Core module).
I only see the obscure not-found error message in preview.3.
What was different on the other computer that caused the couldn't-import message? Different PS version?
Generally, since Windows PowerShell knows nothing about PowerShell Core, the presence of Core module directories in
$env:PSModulePathis likely to cause problems.I don't know what the proper solution is, short of undefining
$env:PSModulePathfor the child process behind the scenes whenpowershell.exeis being invoked, so that Windows PowerShell's regular$env:PSModulePathvalue takes effect.1480c1 commentedon Jan 14, 2019
There is no difference between the two computers that I am aware of as the $PSVersionTable matched under a cursory exam and I used the same Windows (x64) stable installer for both. The only difference that I can hypothesize, other than the obvious different hardware and probably unrelated software and username, is that the first computer had been updated to the october update during the first window and the second is still on the previous update.
iSazonov commentedon Jan 15, 2019
We discussed to have another env path for PowerShell Core .
mklement0 commentedon Jan 15, 2019
Ilya (@iSazonov):
PowerShell Core already does set its own
$env:PSModulePathvalue, which is appropriate in principle (but needs tweaking - see #6850).By contrast, the issue at hand is that when the Windows PowerShell's CLI (
powershell.exe) is called while PowerShell Core's$env:PSModulePathvalue is in effect, problems arise, because child processes automatically inherit the calling process' environment variables.iSazonov commentedon Jan 15, 2019
I believe the issue should be addressed in RFC requested in #6850.
I think the problem in important and it would be nice if MSGT team forced the RFC.
mklement0 commentedon Jan 15, 2019
Ilya (@iSazonov):
PowerShell Core doesn't inherit PSModulePath environment variable from the environment #6850 discusses how PowerShell Core itself should determine its
$env:PSModulePathvalue.However, resolving PowerShell Core doesn't inherit PSModulePath environment variable from the environment #6850 will not resolve this issue, which requires hiding Core-specific
$env:PSModulePathentries from child processes running the Windows PowerShell CLI,powershell.exe.iSazonov commentedon Jan 15, 2019
Michael Klement (@mklement0) There is a suggestion to introduce new
$ENV:PSModulePathCore. Seems it'll resolve the issue too.mklement0 commentedon Jan 15, 2019
Ilya (@iSazonov): Good point: If, ultimately, a new, edition-specific environment variable such as
$env:PSModulePathCoreis chosen for PS Core, the problem discussed here would indeed go away as well.MaximoTrinidad commentedon Feb 12, 2019
Hum!! Original issue was about the Hash.
As of now... No issues!
PowerShell Core Preview
PowerShell Core GA
MaximoTrinidad commentedon Feb 12, 2019
On the issue of calling Windows PowerShell from within PowerShell Core.
It works too!
Sorry I haven't try this before! Hehe
Executing the command line: powershell -noprofile -command "gcm get-file*"
I had no issues neither!
Is it possible the latest releases have fix the issues!!
:)
1480c1 commentedon Feb 13, 2019
1480c1 commentedon Feb 13, 2019
1480c1 commentedon Feb 13, 2019
This should give a better idea of what my original problem was.
test.bat
Running test.bat under 6.2.0-preview.4
Running under 6.1.2
MaximoTrinidad commentedon Feb 13, 2019
Ah!! I was running it from the DOS shell. and it works!
I understand now. My Bad! Hehe
In PowerShell Core 6.1.2 getting a different message:
1480c1 commentedon Feb 13, 2019
pwsh -noprofile -command {(get-filehash "$PSHOME\pwsh.exe").hash}
Your thing will evaluate to "C:\Program" and "Files\Powershell\6\pwsh.exe" as two separate arguments.
1480c1 commentedon Feb 13, 2019
Also note, I'm calling powershell from pwsh, not pwsh from pwsh.
MaximoTrinidad commentedon Feb 13, 2019
Christopher Degawa (@1480c1)
Even executing Get-filehash in Windows PowerShell in PowerShell Core. Definitely a cmdlet confusion issue.
Thanks for the Test.bat!
:)
SteveL-MSFT commentedon Feb 19, 2019
This is a dupe of #6850. Current proposal is to have a separate env var for PSCore6 so WinPS and PSCore6 can work from within each other.
ci: windows; switch to powershell core
use system md5 function of powershell
use system md5 function of powershell
use system md5 function of powershell