Google Chrome Installation and the checksums

[Chr1sDub]

Hey there,

I am currently dealing with the problem in a AVD environment and the installation of chrome via choco.

The sessionhosts in the environment are being freshly deployed every morning, based on an image.
Chrome is being updated via choco via script, every morning.

Now I noticed, that chrome ist not on the newest version on some host.
For example this morning: The newest version of chrome is 112.0.5615.87.

I noticed a sessionhost with an older version of chrome, checked the logs and came to this:

2023-04-13 01:28:58,596 6412 [INFO ] - Downloading googlechrome 64 bit
from 'https://dl.google.com/tag/s/dl/chrome/install/googlechromestandaloneenterprise64.msi'
2023-04-13 01:29:14,752 6412 [INFO ] -
2023-04-13 01:29:17,768 6412 [INFO ] - Download of googlechromestandaloneenterprise64.msi (91.95 MB) completed.
2023-04-13 01:29:21,440 6412 [ERROR] - ERROR: Checksum for 'C:\windows\TEMP\chocolatey\GoogleChrome\112.0.5615.50\googlechromestandaloneenterprise64.msi' did not meet '6e3e83188802d78d46819b87810d8f21760d185574480824889584cf2e7186e3' for checksum type 'sha256'. Consider passing the actual checksums through with --checksum --checksum64 once you validate the checksums are appropriate. A less secure option is to pass --ignore-checksums if necessary.
2023-04-13 01:29:21,705 6412 [ERROR] - The upgrade of googlechrome was NOT successful.
2023-04-13 01:29:21,705 6412 [ERROR] - Error while running 'C:\ProgramData\chocolatey\lib\GoogleChrome\tools\chocolateyInstall.ps1'.
See log for details.

As you can see, the version which is being downloaded, has another version number than the actual newest version.

The only way I can get rid of this at the moment, is to use the -ignore-checksum option.

Is there any other way to deal with this error?

Thank you in advance!

[TheCakeIsNaOH]

As you can see, the version which is being downloaded, has another version number than the actual newest version.

This is caused because Google decided to not offer individual versions, but just have a single URL that always offers the latest version. So whenever they update the installer, the file (and therefore the checksum) changes. Then the package is broken until it is updated with the checksum of the new version.

The solution is to set up an internal package repository, and internalize packages. An internalized googlechrome package will continue to work even when Google updates Chrome, as it no longer relies on their download URL.
https://docs.chocolatey.org/en-us/guides/create/recompile-packages

You can see options to host a package repository here:
https://docs.chocolatey.org/en-us/features/host-packages

[pauby]

Hi, In addition to what the TheCakeIsNaOH said, Google Chrome is cached for licensed customers, so they can install the older versions and get the actual installer, that matches the checksum, for that version. Kind regards, Paul

…

On Thu, 13 Apr 2023, at 7:09 AM, Chr1sDub wrote: Hey there, I am currently dealing with the problem in a AVD environment and the installation of chrome via choco. The sessionhosts in the environment are being freshly deployed every morning, based on an image. Chrome is being updated via choco via script, every morning. Now I noticed, that chrome ist not on the newest version on some host. For example this morning: The newest version of chrome is 112.0.5615.87. I noticed a sessionhost with an older version of chrome, checked the logs and came to this: > > 2023-04-13 01:28:58,596 6412 [INFO ] - Downloading googlechrome 64 bit > from 'https://dl.google.com/tag/s/dl/chrome/install/googlechromestandaloneenterprise64.msi' > 2023-04-13 01:29:14,752 6412 [INFO ] - > 2023-04-13 01:29:17,768 6412 [INFO ] - Download of googlechromestandaloneenterprise64.msi (91.95 MB) completed. > 2023-04-13 01:29:21,440 6412 [ERROR] - ERROR: Checksum for 'C:\windows\TEMP\chocolatey\GoogleChrome\112.0.5615.50\googlechromestandaloneenterprise64.msi' did not meet '6e3e83188802d78d46819b87810d8f21760d185574480824889584cf2e7186e3' for checksum type 'sha256'. Consider passing the actual checksums through with --checksum --checksum64 once you validate the checksums are appropriate. A less secure option is to pass --ignore-checksums if necessary. > 2023-04-13 01:29:21,705 6412 [ERROR] - The upgrade of googlechrome was NOT successful. > 2023-04-13 01:29:21,705 6412 [ERROR] - Error while running 'C:\ProgramData\chocolatey\lib\GoogleChrome\tools\chocolateyInstall.ps1'. > See log for details. > As you can see, the version which is being downloaded, has another version number than the actual newest version. The only way I can get rid of this at the moment, is to use the -ignore-checksum option. Is there any other way to deal with this error? Thank you in advance! — Reply to this email directly, view it on GitHub <#2215>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADBLNS6DGAMBJARZF7HAVJ3XA6KCFANCNFSM6AAAAAAW4TFPB4>. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>