Support Forum: Get Support for Patch My PC Products and Services

Microsoft Configuration Manager and Intune (Enterprises/Paid) => Report Publishing/Download/Hash Issues (Enterprises Using ConfigMgr and Intune) => Topic started by: ccowart83 on August 17, 2021, 11:16:13 AM

Title: Chrome 92.0.4515.131 (x86)
Post by: ccowart83 on August 17, 2021, 11:16:13 AM
Getting HASH error on Chrome x86

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. Additional details: Downloaded Hash [1mVmBOrXd/mWav+Ekgxc0wK7la8=] Catalog Hash [WgS1usCN9JO5auBTpmX9UcpXiS8=]
Title: Re: Chrome 92.0.4515.131 (x86)
Post by: Wes Mitchell on August 17, 2021, 12:26:44 PM
Hi Ccowart83
That error is normal when there is a newer version of a specific software that isn't in our current catalog and cant be validated, once the Patch My PC catalog has been updated with the newer software version you will not receive that error anymore. That software was updated in today's catalog, here is the explanation of the error: https://patchmypc.com/digest-verification-failed-on-content-for-software-update

Google Chrome 92.0.4515.159 (x64/x86)
Release Notes for Google Chrome 92.0.4515.159
Release Type: Ô¼ñ
CVE-IDs:
CVE-2021-30598; CVE-2021-30599; CVE-2021-30600; CVE-2021-30601;
CVE-2021-30602; CVE-2021-30603; CVE-2021-30604
Title: Re: Chrome 92.0.4515.131 (x86)
Post by: derMarc88 on March 02, 2022, 07:13:00 AM
I have the same problem right now. On the support pages there are only solutions for SCCM. We're running PatchMyPC with the Intune version.
Is there any way to update the catalog to get rid of this error?
Title: Re: Chrome 92.0.4515.131 (x86)
Post by: derMarc88 on March 03, 2022, 12:34:48 AM
Quote from: derMarc88 on March 02, 2022, 07:13:00 AM
I have the same problem right now. On the support pages there are only solutions for SCCM. We're running PatchMyPC with the Intune version.
Is there any way to update the catalog to get rid of this error?

it's fixed. Thank you!