search

microsoft / GDK

Microsoft Public GDK
http://aka.ms/gamedevdocs
Other
1.48k stars 99 forks source link

Installing GDK fails with hash mismatch error #22

Closed akoeplinger closed 2 years ago

akoeplinger commented 2 years ago

Since a few days installing GDK on our Azure Pipelines CI machines fails with an error:

[2022-02-06T10:39:10]i305: Verified acquired payload: package_MicrosoftGRDKx86Common_x86_en_us at path: C:\ProgramData\Package Cache\.unverified\package_MicrosoftGRDKx86Common_x86_en_us, moving to: C:\ProgramData\Package Cache\{00682A0F-F4CF-7141-E845-F371B339C9EB}v10.1.22000.1969\Installers\Microsoft GRDK x86 Common-x86_en-us.msi.
[2022-02-06T10:39:10]i338: Acquiring package: package_MicrosoftGRDKx86Common_x86_en_us, payload: pay55F24AFDCB65F8CCF2DB13F229DA19BA, copy from: D:\a\1\s\gdk-extract\GDK-October_2021_Republish\Installers\29ed3e615b33e5f98eeb2dc2ff475882.cab
[2022-02-06T10:39:10]e000: Error 0x80091007: Hash mismatch for path: C:\ProgramData\Package Cache\.unverified\pay55F24AFDCB65F8CCF2DB13F229DA19BA, expected: CE0266367A39A15902E5EAC8702ED1AC2481A20B, actual: 527D32C94D9801DDEDC1AE833248D1459A82A625
[2022-02-06T10:39:10]e000: Error 0x80091007: Failed to verify hash of payload: pay55F24AFDCB65F8CCF2DB13F229DA19BA
[2022-02-06T10:39:10]e310: Failed to verify payload: pay55F24AFDCB65F8CCF2DB13F229DA19BA at path: C:\ProgramData\Package Cache\.unverified\pay55F24AFDCB65F8CCF2DB13F229DA19BA, error: 0x80091007. Deleting file.
[2022-02-06T10:39:10]e000: Error 0x80091007: Failed to cache payload: pay55F24AFDCB65F8CCF2DB13F229DA19BA
[2022-02-06T10:39:10]i000: ERROR: Failed to verify the integrity of payload

Full log:

Microsoft Game Development Kit__211000(October_2021)_20220206103628.log

akoeplinger commented 2 years ago

@FLY1NGSQU1RR3L

akoeplinger commented 2 years ago

Ok looks like this fixed itself, probably some issue with the Microsoft download server?

FLY1NGSQU1RR3L commented 2 years ago

@akoeplinger No you are not imagining things. What I thought was a clever script for preparing our multi-headed branch releases and injecting folders like the VS2022 temporary workaround (VSIX installers) utterly failed because GitHub never forgets anything. Backed out the munged installer folders and created separate branches to keep everything neat and tidy.

March 2022 release publishing today to add release notes to the new branch.

FLY1NGSQU1RR3L commented 2 years ago

PS I completely forgot there was an "inbox" here and missed some of these messages. Apologies for the delay.

akoeplinger commented 2 years ago

No worries, thanks for following up!