The hash of file downloaded is different than the file hash in our catalog. Hash errors happen when vendors release updates that aren't available in our catalog yet. This error should be resolved in the next catalog update. It could also have been induced by a firewall issue. Additional details:[KAOp3QZNz/ID14Puj2Fz2rKZ8Bk=] vs [xRMLPqTqyAeQoV/Zn7R41ZNlL5o=]
Problem has started around 20 hours ago
Thank you. It looks like the hash of the .msi for Google Chrome's enterprise installer has changed, indicating a new version has been released. We will get this updated in the next catalogue release (more than likely today.)