A community where customers and the community can provide feedback to make a better product for everyone! For more details on how we prioritize requests, please see:
Google has officially released its ARM native Chrome browser for Windows. As our users start to adopt Copilot+ PCs in the future, its important that we be able to deploy and patch the native version of Chrome to our fleet.
What Patch My PC product is this new application request for?
Patch My PC Enterprise
Jean-François Nivaille
Oct 30, 2025
If it's possible, add the possibility to create only one application package for chrome with multiple deployment type, for example one for x64 with adhoc requirements (only x64 OS) and a second one for ARM64 with other requirements (only ARM64 OS).
We use PatchMyPC to install the 64-bit MSI version of Google Chrome and noticed that the installation fails on ARM64 devices. This could be a bug in Google Chrome because I recall it worked previously, but it is causing a larger issue for our organization that uses Microsoft Defender XDR.
The installation writes a registry key to HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ but the key is not removed when the installation fails. The failure occurs before Google Chrome is able to update the DisplayVersion value so it uses the MSI version (currently 70.83.32895) instead of the application version. Microsoft Defender XDR flags this as a vulnerable legacy version of Google Chrome and increases our exposure score.
The support of ARM64 Google Chrome would be great because it would help mitigate this issue entirely.
If it's possible, add the possibility to create only one application package for chrome with multiple deployment type, for example one for x64 with adhoc requirements (only x64 OS) and a second one for ARM64 with other requirements (only ARM64 OS).
Waiting for completion of the following idea: https://ideas.patchmypc.com/ideas/PATCHMYPC-I-2540
We’d also love to start seeing ARM support by PMPC as we begin using these devices in our org.
We use PatchMyPC to install the 64-bit MSI version of Google Chrome and noticed that the installation fails on ARM64 devices. This could be a bug in Google Chrome because I recall it worked previously, but it is causing a larger issue for our organization that uses Microsoft Defender XDR.
The installation writes a registry key to HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ but the key is not removed when the installation fails. The failure occurs before Google Chrome is able to update the DisplayVersion value so it uses the MSI version (currently 70.83.32895) instead of the application version. Microsoft Defender XDR flags this as a vulnerable legacy version of Google Chrome and increases our exposure score.
The support of ARM64 Google Chrome would be great because it would help mitigate this issue entirely.