You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Get-FileHash tests consistently failing on Server 2016 #5960
Build current sources and run Start-PSPester, no parameters
Expected behavior
All Tests pass.
Actual behavior
Each test Get-FileHash.Tests.ps1 that is comparing against an expected hash is failing with a mismatched hash value.
Note that this mismatch is not a case-sensitivity failure; while the string lengths match for each algorithm, the the hash values are completely different.
Environment data
Running on server datacenter 2016
$PSVersionTable
Name Value
PSVersion 6.0.0
PSEdition Core
GitCommitId v6.0.0-128-gf587fd06d6046859ca1a9fe3470d5f9615dc5e01
OS Microsoft Windows 10.0.17080
Platform Win32NT
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
WSManStackVersion 3.0
This issue has not had any activity in 6 months, if there is no further activity in 7 days, the issue will be closed automatically.
Activity in this case refers only to comments on the issue. If the issue is closed and you are the author, you can re-open the issue using the button below. Please add more information to be considered during retriage. If you are not the author but the issue is impacting you after it has been closed, please submit a new issue with updated details and a link to this issue and the original.
Activity
rjmholt commentedon Mar 22, 2018
Dan Travison (@dantraMSFT) Does #6430 fix this?
ThomasNieto commentedon Jul 31, 2023
Dan Travison (@dantraMSFT) are you still experiencing this issue?
microsoft-github-policy-service commentedon Jan 28, 2024
This issue has not had any activity in 6 months, if there is no further activity in 7 days, the issue will be closed automatically.
Activity in this case refers only to comments on the issue. If the issue is closed and you are the author, you can re-open the issue using the button below. Please add more information to be considered during retriage. If you are not the author but the issue is impacting you after it has been closed, please submit a new issue with updated details and a link to this issue and the original.