Aug 12 2019 02:32 PM
Aug 12 2019 02:32 PM
Edge Dev on x64 bit hardware
Target: "C:\Program Files (x86)\Microsoft\Edge Dev\Application\msedge.exe"
Start in: "C:\Program Files (x86)\Microsoft\Edge Dev\Application"
Correct path should be
Target: "C:\Program Files\Microsoft\Edge Dev\Application\msedge.exe"
Start in: "C:\Program Files\Microsoft\Edge Dev\Application"
Aug 13 2019 10:34 AM
Aug 13 2019 12:18 PM
Microsoft is not following there own best practice in directory install path.
Aug 13 2019 12:48 PM
Aug 13 2019 03:25 PM
They do not have to go to the same directory, just a more sensible one like:
Target: "C:\Program Files\Microsoft\Edge Dev\Application\msedge.exe" - Dev
Target: "C:\Program Files\Microsoft\Edge Canary\Application\msedge.exe" - Canary
Target: "C:\Program Files\Microsoft\Edge\Application\msedge.exe" - Beta/Retail
Aug 14 2019 12:08 AM
Jan 20 2020 03:40 AM
Stable version is out, it still incorrectly installs in x86 folder.
Forgive me if I just think that nobody noticed and/or nobody cared from the beginning, that cannot be because "they did it on purpose cause they know better". It's just plain wrong.
Jan 20 2020 06:04 AM
@Paolo_DelRe I agree. This is not good. It is wrong and makes the installer developer look a fool. It is completely against Microsoft installer path conventions.
Reg, Henno
Feb 03 2020 06:27 AM - edited Feb 03 2020 06:28 AM
This is very confusing, especially since I'm running on ARM. The release channel does not support ARM (it doesn't mention it, it just runs as 32-bit and incredibly slow due to emulation). I assumed it was running x86 code since it was installed to "C:\Program Files (x86)\".
After some searching, I find out that the release channel does not yet support ARM. So I hunt down the BETA channel and install it, only to see that it too installs to "Program Files (x86)". After even more googling, I realize that since it's now running as 64-bit, that it's indeed running ARM64 (and is performing much better due to lack of emulation). But how confusing to install that to "C:\Program Files (x86)\" instead of "C:\Program Files (Arm)\".
To make matters more confusing, Windows Task Manager only shows you bitness in the platform column, so you only ever see "32-bit" and "64-bit", but have no idea if it's running native ARM code or x86 code via emulation. I usually fall back to looking at the installation path, which Edge is violating.