- Google’s Chrome installer for PCs with AMD and Intel CPUs has been broken for the past week
- Detective work suggests that the version for these PCs was accidentally replaced by the Arm installer, which is for very different Snapdragon CPUs
- While the issue has now been fixed, Google took a long time to resolve it
Those trying to install the Chrome browser in Windows 11 or 10 over the course of the past week may well have been flummoxed by an error telling them the app won’t run on their PC – and I can’t quite believe how long it’s taken Google to fix this.
Nonetheless, the good news is that the glitch is fixed, even if it took the company way longer than it should have.
The problem, in case you missed it, was flagged on Reddit and by Windows Latest a week ago.
What happened was that on firing up the Chrome Installer file (ChromeSetup.exe, download from Google’s website), people watched the process come to a screeching halt, with an error message that read: “This app can’t run on your PC: To find a version for your PC, check with the software publisher.”
As to the cause, Windows Latest did some detective work, and theorized that what Google had done here – somehow – was accidentally swap the Arm installer of Chrome with the x86 installer. Meaning that the version of Chrome for Copilot+ PCs with Snapdragon (Arm-based) processors got swapped with the version for AMD or Intel CPUs.
That conclusion was based on digging into the setup file and finding references to ‘Arm’ which surely wouldn’t be there with a non-Arm executable. Furthermore, 9 to 5 Google backs up this theory, as the tech site tried the faulty version of Chrome on a Snapdragon PC, and found it worked fine (as it would do if it was the Arm installer).
9 to 5 Google was also on the ball in terms of noticing that the issue is finally cured, and you can now download the Chrome installer on a Windows PC with an AMD or Intel CPU, and it’ll work just as you’d expect.
Analysis: A bafflingly basic mistake with only one winner (Edge)
Okay, so mistakes can be made. Indeed, they happen all the time in the tech world, or elsewhere for that matter. But for such a basic glitch to be left in place to annoy a bunch of Windows users for the best part of a week is baffling – especially while reports were flying around about the problem.
I can’t imagine this was something that was particularly difficult to resolve, either, as it looks like a simple mix up of files, as noted (unless there’s something I’m missing here). Apparently, the Arm version of Google Chrome wasn’t affected, and the installer still worked for those with a Snapdragon-powered machine.
This could have cost Google some Chrome users potentially, who might have got fed up with the browser failing to install, and maybe even plumped for Microsoft Edge, its main rival, instead. (Incidentally, Edge is the best overall web browser as far as our roundup of the most compelling offerings out there is concerned).
You might also like
https://cdn.mos.cms.futurecdn.net/8Mw3Yhi8NZMR44GH526arM-1200-80.jpg
Source link
