Some of those reasons are covered in this blog post:įirstly, some packages (like Google Chrome) don't included versioned URL's for their application installer. There can be a number of reasons 'why' the checksum is different. This is a security feature, and when Chocolatey finds that the checksum differs between the file that is downloaded, and what was expected, it will not proceed with the installation. Secondly, a checksum is used to ensure that the file that is downloaded at runtime is the same as the one that the package maintainer expected it to be when the package was created. In most cases, for new package submissions, Moderators (myself included) will request that checksums be added to package installation script, regardless of whether they happen over HTTP or HTTPS. With regard to checksums, the guidance is that checksums for an installer/zip/etc are required when the download happens over HTTP, and that checksums are recommended when the download happens over HTTPS.

There are a couple of different topics being asked about here, so I wanted to make sure that each is covered.įirstly, Moderators of packages submitted to Chocolatey Community Repository make a number of checks.

Chocolatey install chrome