Why Edge is installed in “C:\Program Files (x86)\

Topic

New Reply

Why is x-64 nEdge installed in “C:\Program Files (x86)” instead of “C:\Program Files”?

Chuck Billow

Reply | Quote

Replies

It’s an historical mistake in the InstallDir path variable in Chromium that wasn’t noticed when Chromium was picked up for use by Edge.

Here’s what an Edge project manager wrote in an Is Edge browser a 32-bit browser? Microsoft Discussion (see the entry for June 10, 2020):

We are happy to confirm that MSFT Edge is indeed a 64-bit browser. (To make a long story short, there is an issue in the Chromium code that can make it appear like it’s 32-bit in the Program Files folder.)

Please let us know if there is anything else we can help answer!

Fawkes (they/them)
Project & Community Manager – Microsoft Edge

So, an error that wasn’t picked up 5 years ago and still hasn’t been corrected.

Hope this helps…

Reply | Quote

CWBillow wrote:

Why is x-64 nEdge installed in “C:\Program Files (x86)” instead of “C:\Program Files”?

it’s by “faulty” design of Microsoft, even on x64 based Windows
newer versions of x64 Google Chrome, on the other hand, no longer install in the “C:\Program Files (x86)” folder

Reply | Quote

Microsoft did not design Chromium. The problem is in the Chromium code – read the whole thread. Changing the installation folder now would be a big deal that would probably require a major change to the uninstall/install routine.

--Joe

Reply | Quote

EP wrote:

newer versions of x64 Google Chrome, on the other hand, no longer install in the “C:\Program Files (x86)” folder

Mine still do.

Reply | Quote

Alex,

Have you uninstalled Chrome, then downloaded the latest version and done a fresh install?

May the Forces of good computing be with you!

RG

PowerShell & VBA Rule!
Computer Specs

1 user thanked author for this post.

Alex5723

Reply | Quote

Alex5723 wrote:

Mine still do.

That happens if you replace the x86 version with the x64 version without first removing the x86 version and is because the x64 installer will use the existing path that’s stored in the registry as the install location for the new version.

BTW, it’s actually pretty common for this to happen when replacing x86 version S/W with x64 versions if the x86 version hasn’t been removed before the installer runs.

In fact, it’s so common, some installers are specifically configured to check for older versions of themselves and warn the user it must be “uninstalled” before the installation can proceed.

Also bear in mind…

As long as the path is correct in the registry and/or its shortcuts, a program (regardless of whether it’s x86 or x64) can be installed anywhere on any drive and will run just fine!

Heck, with some programs it’s even possible to compress the install location into an archive, completely uninstall the program, and then extract it to wherever you want and it’ll still run just fine (i.e. you’ve basically converted it into a portable program.)

I’ve done this with several different programs on my own PC and haven’t encountered any issues with them running just as if they were actually still installed.

1 user thanked author for this post.

Alex5723

Reply | Quote

RetiredGeek wrote:

Have you uninstalled Chrome, then downloaded the latest version and done a fresh install?

No.

Google should have taken care removing Chrome from (x86) and re-installing in (x64).

Reply | Quote