64-bit apps in Program Files x86 directory

Why does Edge 64-bit get installed in Program Files x86?

I deleted all the files in Program Files x86 but Edge went, so I had to download and reinstall.
The same for Sonos, but this is a 32-bit app.
I looked in Task Manager and MS Edge is 64-bit.
I have not altered any environment variables, nor changed any paths in the registry.

You did what?

Don't toutch Program Files folders.

Edge is a win32 64-bit Cromium based app...ofc it is put there.

I meant to write Program Files x 86!

I have corrected post 1

kelper said:

I meant to write Program Files x 86!

I have corrected post 1

Click to expand...

I made a mistake too...making the assumption that you printed out the correct folder.

Anyways...don't manually delete program files, you break things

Your question is very valid though...Edge should not be installed in the x86 programs folder.

Microsoft is not following its own conventions.

kelper said:

Why does Edge 64-bit get installed in Program Files x86?

Click to expand...

The answer: Why are there separate Program Files and Program Files (x86) directories? - The Old New Thing

I have 64-bit apps install in the X86 folder.. I'm "assuming" it's because I had 32-bit versions installed there - but maybe not.
I'm also "assuming" that when the app upgraded itself it found an install in x86 and updated vs deleting and reinstalling.
Personally, I would have wrote the install app to remove and reinstall, but ... doesn't alter that I have NOT installed 64-bit progs in the X86 folder but hey do exist there under Win11.
You can look in Task Mangler.. Details under Architecture column to determine 32 vs 64 bit.

x BlueRobot said:

The answer: Why are there separate Program Files and Program Files (x86) directories? - The Old New Thing

Click to expand...

That is the answer for why the two folders exist, but does not explain why a 64-bit app is in a 32-bit folder

Perhaps Edge has 32 bit components.
Perhaps they just couldn't be bothered to put the x64 bits of it in PF & the x86 bits in PF86???


Denis

Infrastructure, many components have to work in both environments.

Try3 said:

Perhaps Edge has 32 bit components.
Perhaps they just couldn't be bothered to put the x64 bits of it in PF & the x86 bits in PF86???


Denis

Click to expand...

Software does not work that way...either it is 32bit or it is 64bit. There is no in between. Unless they use Windows API in between which can run both bitness, but that would be ridiculous and over complicated.

SlicEnDicE said:

Software does not work that way...either it is 32bit or it is 64bit. There is no in between. Unless they use Windows API in between which can run both bitness, but that would be ridiculous and over complicated.

Click to expand...

Theoretically yes, but what if an App, from within it's own Runtime environment, has to interact with File Explorer?

Edwin said:

Theoretically yes, but what if an App, from within it's own Runtime environment, has to interact with File Explorer?

Click to expand...

File Explorer is 64bit and so is Edge...there is absolutely no issue.

SlicEnDicE said:

Software does not work that way

Click to expand...

I see.
Thanks for enlightening me.





All the best,
Denis

In the end, it is rather lazy programming by app developers who updated 32bit apps to 64bit apps but did not bother change default installation program/folders.

There are many examples of this. It really does not matter. Attempting to change folder is more likely to break things.

So ignore it and move on.

SlicEnDicE said:

File Explorer is 64bit and so is Edge...

Click to expand...

True, but there's still 32bit elements all over the place...,
Perhaps unnecessary residue?
Anyway, I'll take your word for it..., you probably know better than I do!

Try3 said:

I see.
Thanks for enlightening me.
View attachment 91544




All the best,
Denis

Click to expand...

It indeed does so it can run more efficiently on a 64 bit OS. 64-bit Office does not have 32-bit components though and everything is installed in Program Files. (Unless they install some Common Components which is not put under Office name itself, but I doubt this and have not checked what the installer sucks down from the interwebs)

kelper said:

Why does Edge 64-bit get installed in Program Files x86?

Click to expand...

A good question.

Happened some time ago with Chrome. I read there was a bug with the installer.
But now it gets it done properly. Not sure how it got fixed.

I assume Edge has the same issue Chrome had, since they're both Chromium clones.

cereberus said:

In the end, it is rather lazy programming by app developers who updated 32bit apps to 64bit apps but did not bother change default installation program/folders.

There are many examples of this. It really does not matter. Attempting to change folder is more likely to break things.

So ignore it and move on.

Click to expand...

Exactly.

In this case of Edge, the problem will have to be fixed by the developers, most likely through the installer.

If by any means a new installer fixes it, then case closed. If however the new installer detects a previous installation in Program Files (x86) and decides to keep it like this, then there's nothing to do there to 'fix' it.

It's installed in same place (C:\Program Files (x86)) for everyone, i think. On all my systems is the same for me - and didn't even noticed that - up till this point. Didn't really care - to be honest, since it's irrelevant in terms of functionality. I mean, you can install any 64 bit app in C:\Program Files (x86) and it won't make any difference. The only reason there's a folder called Program Files (x86) and Program Files - is tidiness. I do care about that (tidiness) - just for the sake of order - but only when it's an app i chose to install (it's important to know that app is still 32 bit so that's why i installed there - just in case they release a 64 version).

To me, this question sounds more like: Why is Microsoft Edge devs team still so lazy and disorderly after all this years?!

Which sounds more like a redundant question - taking into account the state of Windows as a whole - as in: a disorderly mess comprised of hundreds of thousands of folders and files - scattered in multiple locations. Not to mention you have folder, files, settings even GUIs from older versions of Windows - that nobody bothered to rename them and bring them up to date. Seriously, it's a billions of dollars company - they could hire 3 people to cover that part in probably less than a month. Yet, the core product managers don't seem to care. So hey, be glad that this HUGE pile of mess works - that this days we have powerful enough CPUs to decipher this mess of an OS while using minimum resources. Also helps that ram and storage is rather fast. Since the amount of background processes/services - pilled up as well - wasting resources meaninglessly. Which is actually the main reason why older hardware with limited raw power and resources - would struggle to run latest version of Windows.

And... by the looks of it - that won't change with Windows 12. Who knows, maybe Windows 20 will finally be reworked from the grown up - since by then - the whole dev team should be changed by younger generations. Then again, if A.I. takes over this jobs - might happen sooner (like Windows 14).