winget-pkgs icon indicating copy to clipboard operation
winget-pkgs copied to clipboard

[Package Issue]: Google.Chrome – Installer Hash Mismatch

Open iTzSnicholls89 opened this issue 1 year ago • 5 comments

### Please confirm these before moving forward

I have searched for my issue and not found a work-in-progress/duplicate/resolved issue.

I have not been informed if the issue is resolved in a preview version of the winget client. ### Category of the issue Installer hash mismatch.

Brief description of your issue

The installation of Google.Chrome fails due to an installer hash mismatch. This error occurs while running the installation via WinGet.

Steps to reproduce

winget install --id "Google.Chrome" --source "winget" --silent --accept-package-agreements --accept-source-agreements --verbose-logs

Actual behavior

PS C:\Users\XXX> winget install --id=Google.Chrome --source="winget" --silent --accept-package-agreements --accept-source-agreements --verbose-logs Found Google Chrome [Google.Chrome] Version 129.0.6668.90 This application is licensed to you by its owner. Microsoft is not responsible for, nor does it grant any licenses to, third-party packages. Downloading https://dl.google.com/dl/chrome/install/googlechromestandaloneenterprise64.msi ██████████████████████████████ 118 MB / 118 MB Installer hash does not match; this cannot be overridden when running as admin PS C:\Users\XXX>

Expected behavior

The package should install without any hash mismatch issues.

Environment

2024-10-17 16:34:33.506 [CORE] WinGet, version [1.8.1911], activity [{268E35D8-2EC7-4185-9F0B-48BA38528B50}] 2024-10-17 16:34:33.507 [CORE] OS: Windows.Desktop v10.0.22631.4249 2024-10-17 16:34:33.507 [CORE] Command line Args: "C:\Program Files\WindowsApps\Microsoft.DesktopAppInstaller_1.23.1911.0_x64__8wekyb3d8bbwe\winget.exe"

Screenshots and Logs

winget search Google.Chrome

Name Id Version Source

Google Chrome Google.Chrome 129.0.6668.90 winget

searching the Manifests area shows the version 130.0.6723.59

iTzSnicholls89 avatar Oct 17 '24 15:10 iTzSnicholls89

We've found some similar issues:

  • #181365 , similarity score: 98%
  • #96740 , similarity score: 93%
  • #135180 , similarity score: 89%
  • #97607 , similarity score: 88%
  • #120072 , similarity score: 88%
  • #147885 , similarity score: 85%

If any of the above are duplicates, please consider closing this issue out and adding additional context in the original issue.

Note: You can give me feedback by 👍 or 👎 this comment.

similar-issues-ai[bot] avatar Oct 17 '24 15:10 similar-issues-ai[bot]

The current version of Google Chrome in the WinGet repo is 130.0.6723.59. You may need to update your source cache through winget source update.

SpecterShell avatar Oct 18 '24 02:10 SpecterShell

Tried this but still issue exists

PS C:\Users\XXX> winget source update Updating all sources... Updating source: msstore... Done Updating source: winget... ████████████████████ 0% Done PS C:\Users\XXX> winget install --id=Google.Chrome --source="winget" --silent --accept-package-agreements --accept-source-agreements --verbose-logs Found Google Chrome [Google.Chrome] Version 129.0.6668.90 This application is licensed to you by its owner. Microsoft is not responsible for, nor does it grant any licenses to, third-party packages. Downloading https://dl.google.com/dl/chrome/install/googlechromestandaloneenterprise64.msi ██████████████████████████████ 118 MB / 118 MB Installer hash does not match; this cannot be overridden when running as admin

iTzSnicholls89 avatar Oct 18 '24 09:10 iTzSnicholls89

That's weird. It works normally on my end:

❯ winget install --id=Google.Chrome --source="winget" --silent --accept-package-agreements --accept-source-agreements --verbose-logs
Found Google Chrome [Google.Chrome] Version 130.0.6723.59
This application is licensed to you by its owner.
Microsoft is not responsible for, nor does it grant any licenses to, third-party packages.
Downloading https://dl.google.com/dl/chrome/install/googlechromestandaloneenterprise64.msi
  ██████████████████████████████   118 MB /  118 MB
Successfully verified installer hash

It might be a CDN issue from the WinGet source server.

SpecterShell avatar Oct 18 '24 10:10 SpecterShell

Manually verified. Currently behind a proxy in Hong Kong SAR., China.

16:50:53 D:\...\winget-pkgs  [master ≡] 1ms pwsh> winget download -e --id Google.Chrome -s winget --accept-package-agreements --accept-source-agreements
已找到 Google Chrome [Google.Chrome] 版本 130.0.6723.70
此应用程序由其所有者授权给你。
Microsoft 对第三方程序包概不负责,也不向第三方程序包授予任何许可证。
正在下载 https://dl.google.com/dl/chrome/install/googlechromestandaloneenterprise64.msi
  ██████████████████████████████   120 MB /  120 MB
已成功验证安装程序哈希
已下载安装程序: D:\Dragon1573\Downloads\Google.Chrome_130.0.6723.70\Google Chrome_130.0.6723.70_Machine_X64_wix_zh-CN.msi

Dragon1573 avatar Oct 27 '24 08:10 Dragon1573

I had this issue today. I was able to work around it by bypassing the check.

PS C:\Users\jaraco> sudo winget settings --enable InstallerHashOverride
Enabled admin setting 'InstallerHashOverride'.
PS C:\Users\jaraco> winget install Google.Chrome --ignore-security-hash
Found Google Chrome [Google.Chrome] Version 132.0.6834.84
This application is licensed to you by its owner.
Microsoft is not responsible for, nor does it grant any licenses to, third-party packages.
Downloading https://dl.google.com/dl/chrome/install/googlechromestandaloneenterprise64.msi
  ██████████████████████████████   122 MB /  122 MB
Installer hash does not match; proceeding due to --ignore-security-hash
...

Of course, that workaround isn't available when installing as admin.

It sounds like this error is a common problem for packages that updated themselves frequently (such as Google Chrome). Perhaps there's a better solution that doesn't leave these packages often broken.

jaraco avatar Jan 23 '25 16:01 jaraco

Same problem for me…

eclipse313 avatar Jan 23 '25 17:01 eclipse313

It might be a CDN issue from the WinGet source server.

In my first experience, I was on a corporate machine with VPNs and other administrative controls. To exclude those as a possibility, I tested on another machine, a mostly clean Windows 11 VM with a regular IP connection (no VPNs, proxies, etc), and the issue replicated, so the issue seems to be that the hashes in winget have fallen behind the contents of the installer.

jaraco avatar Jan 23 '25 18:01 jaraco

The Chrome package in the WinGet repo has been updated to 132.0.6834.111, but the pipeline for generating the index is having some issues: https://github.com/microsoft/winget-pkgs/issues/216213

SpecterShell avatar Jan 24 '25 01:01 SpecterShell