Hash error for Google Chrome

[PauliBaumeister]

Hi, i try to create a package for Google Chrome, but i get this error:

New-WtWingetPackage -PackageId Google.Chrome -PackageFolder C:\winget\
INFO: Packaging package Google.Chrome 131.0.6778.86
INFO: [WingetManager] Getting package info for Google.Chrome 131.0.6778.86 from github
INFO: [IntuneManager] Generating IntuneWin package for Google.Chrome 131.0.6778.86 X64 System in C:\winget\
INFO: [IntuneManager] Downloading installer from https://dl.google.com/dl/chrome/install/googlechromestandaloneenterprise64.msi to C:\Users\TimoHilbertz\AppData\Local\Temp\wintuner\Google.Chrome\131.0.6778.86\googlechromestandaloneenterprise64.msi
INFO: [DefaultFileManager] Downloading https://dl.google.com/dl/chrome/install/googlechromestandaloneenterprise64.msi to C:\Users\TimoHilbertz\AppData\Local\Temp\wintuner\Google.Chrome\131.0.6778.86\googlechromestandaloneenterprise64.msi
WARNING: [DefaultFileManager] Downloading large file https://dl.google.com/dl/chrome/install/googlechromestandaloneenterprise64.msi to C:\Users\TimoHilbertz\AppData\Local\Temp\wintuner\Google.Chrome\131.0.6778.86\googlechromestandaloneenterprise64.msi with size 121MB
New-WtWingetPackage: Hash mismatch for https://dl.google.com/dl/chrome/install/googlechromestandaloneenterprise64.msi. Expected 9FCF15CB2390B84887B94E8E2F41D01EFF325ECCDAC405E4F9A156DBC209689D but got 9F52A6D72435AE981B55D29356CAEBCEFA22E8E6EE5D1468C35CF8414572B140
New-WtWingetPackage: Hash mismatch for https://dl.google.com/dl/chrome/install/googlechromestandaloneenterprise64.msi. Expected 9FCF15CB2390B84887B94E8E2F41D01EFF325ECCDAC405E4F9A156DBC209689D but got 9F52A6D72435AE981B55D29356CAEBCEFA22E8E6EE5D1468C35CF8414572B140

I guess that this issue is related to a problem that only Google can fix, right?
Is there any way to skip the hash checking, and if yes, i guess it's not really recommended because it is a basic security feature?

Many thanks!

[svrooij]

Duplicate of #122

Summary, there won't be such a parameter because, Yes this is a security feature. Google is re-using the same url for each new version, so sometimes it works and then they produce a new version and there is a mismatch. This is an ever returning issue.

[PauliBaumeister]

sorry for the dupe, i'm still learning ;-)
so i guess that we can only be patient and wait for a new release - and beg Google to change their stupid practice?