Home

Edge Dev installing to incorrect directory

%3CLINGO-SUB%20id%3D%22lingo-sub-801532%22%20slang%3D%22en-US%22%3EEdge%20Dev%20installing%20to%20incorrect%20directory%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-801532%22%20slang%3D%22en-US%22%3E%3CP%3EEdge%20Dev%20on%20x64%20bit%20hardware%3C%2FP%3E%3CP%3ETarget%3A%20%22C%3A%5CProgram%20Files%20(x86)%5CMicrosoft%5CEdge%20Dev%5CApplication%5Cmsedge.exe%22%3CBR%20%2F%3EStart%20in%3A%20%22C%3A%5CProgram%20Files%20(x86)%5CMicrosoft%5CEdge%20Dev%5CApplication%22%3C%2FP%3E%3CP%3ECorrect%20path%20should%20be%3C%2FP%3E%3CP%3ETarget%3A%20%22C%3A%5CProgram%20Files%5CMicrosoft%5CEdge%20Dev%5CApplication%5Cmsedge.exe%22%3CBR%20%2F%3EStart%20in%3A%20%22C%3A%5CProgram%20Files%5CMicrosoft%5CEdge%20Dev%5CApplication%22%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-803118%22%20slang%3D%22en-US%22%3ERe%3A%20Edge%20Dev%20installing%20to%20incorrect%20directory%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-803118%22%20slang%3D%22en-US%22%3EI'm%20pretty%20sure%20the%20Edge%20developers%20are%20aware%20of%20that%20and%20are%20doing%20that%20intentionally%20for%20their%20Internal%20purposes%20or%20some%20future%20plans%20we're%20not%20aware%20of.%20so%20that's%20not%20really%20incorrect%2C%20just%20unconventional%2C%20and%20honestly%20for%20a%20software%20that%20is%20in%20alpha%20(dev)%20and%20pre-alpha%20(canary)%20state%20i%20think%20it's%20normal.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-803308%22%20slang%3D%22en-US%22%3ERe%3A%20Edge%20Dev%20installing%20to%20incorrect%20directory%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-803308%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F310193%22%20target%3D%22_blank%22%3E%40HotCakeX%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMicrosoft%20is%20not%20following%20there%20own%20best%20practice%20in%20directory%20install%20path.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-803366%22%20slang%3D%22en-US%22%3ERe%3A%20Edge%20Dev%20installing%20to%20incorrect%20directory%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-803366%22%20slang%3D%22en-US%22%3EI'm%20sure%20they%20know%20that%20better%20than%20you%20and%20me%20lol.%20they%20probably%20considered%20the%20fact%20that%20there%20will%20be%20a%20time%20when%204%20different%20channels%20of%20the%20Edge%20will%20be%20out%2C%20they%20can't%20all%20go%20to%20the%20same%20directory.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-803530%22%20slang%3D%22en-US%22%3ERe%3A%20Edge%20Dev%20installing%20to%20incorrect%20directory%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-803530%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F310193%22%20target%3D%22_blank%22%3E%40HotCakeX%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThey%20do%20not%20have%20to%20go%20to%20the%20same%20directory%2C%20just%20a%20more%20sensible%20one%20like%3A%3C%2FP%3E%3CP%3E%3CSPAN%3ETarget%3A%20%22C%3A%5CProgram%20Files%5CMicrosoft%5CEdge%20Dev%5CApplication%5Cmsedge.exe%22%20-%20Dev%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3ETarget%3A%20%22C%3A%5CProgram%20Files%5CMicrosoft%5CEdge%20Canary%5CApplication%5Cmsedge.exe%22%20-%20Canary%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3ETarget%3A%20%22C%3A%5CProgram%20Files%5CMicrosoft%5CEdge%5CApplication%5Cmsedge.exe%22%20-%20Beta%2FRetail%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-803950%22%20slang%3D%22en-US%22%3ERe%3A%20Edge%20Dev%20installing%20to%20incorrect%20directory%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-803950%22%20slang%3D%22en-US%22%3EGoogle%20Chrome%20Canary%20goes%20to%20the%20Appdata%20for%20a%20reason%2C%20Microsoft%20decided%20to%20keep%20it%20that%20way%20and%20made%20their%20Canary%20chromium%20based%20one%20to%20go%20to%20that%20folder%20as%20well.%20i%20understand%20it%20is%20more%20sensible%20to%20You%20but%20to%20the%20actual%20Developers%20of%20the%20Edge%2FGoogle%20chrome%2FChromium%20etc%2C%20AppData%20was%20more%20appropriate.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1117940%22%20slang%3D%22en-US%22%3ERe%3A%20Edge%20Dev%20installing%20to%20incorrect%20directory%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1117940%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F310193%22%20target%3D%22_blank%22%3E%40HotCakeX%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EStable%20version%20is%20out%2C%20it%20still%20incorrectly%20installs%20in%20x86%20folder.%3C%2FP%3E%3CP%3EForgive%20me%20if%20I%20just%20think%20that%20nobody%20noticed%20and%2For%20nobody%20cared%20from%20the%20beginning%2C%20that%20cannot%20be%20because%20%22they%20did%20it%20on%20purpose%20cause%20they%20know%20better%22.%20It's%20just%20plain%20wrong.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1118136%22%20slang%3D%22en-US%22%3ERe%3A%20Edge%20Dev%20installing%20to%20incorrect%20directory%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1118136%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F525335%22%20target%3D%22_blank%22%3E%40Paolo_DelRe%3C%2FA%3E%26nbsp%3BI%20agree.%20This%20is%20not%20good.%20It%20is%20wrong%20and%20makes%20the%20installer%20developer%20look%20a%20fool.%20It%20is%20completely%20against%20Microsoft%20installer%20path%20conventions.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EReg%2C%20Henno%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1147826%22%20slang%3D%22en-US%22%3ERe%3A%20Edge%20Dev%20installing%20to%20incorrect%20directory%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1147826%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20is%20very%20confusing%2C%20especially%20since%20I'm%20running%20on%20ARM.%26nbsp%3B%20The%20release%20channel%20does%20not%20support%20ARM%20(it%20doesn't%20mention%20it%2C%20it%20just%20runs%20as%2032-bit%20and%20incredibly%20slow%20due%20to%20emulation).%26nbsp%3B%20I%20assumed%20it%20was%20running%20x86%20code%20since%20it%20was%20installed%20to%20%22C%3A%5CProgram%20Files%20(x86)%5C%22.%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3EAfter%20some%20searching%2C%20I%20find%20out%20that%20the%20release%20channel%20does%20not%20yet%20support%20ARM.%26nbsp%3B%20So%20I%20hunt%20down%20the%20BETA%20channel%20and%20install%20it%2C%20only%20to%20see%20that%20it%20too%20installs%20to%20%22Program%20Files%20(x86)%22.%26nbsp%3B%20After%20even%20more%20googling%2C%20I%20realize%20that%20since%20it's%20now%20running%20as%2064-bit%2C%20that%20it's%20indeed%20running%20ARM64%20(and%20is%20performing%20much%20better%20due%20to%20lack%20of%20emulation).%26nbsp%3B%20But%20how%20confusing%20to%20install%20that%20to%20%22C%3A%5CProgram%20Files%20(x86)%5C%22%20instead%20of%20%22C%3A%5CProgram%20Files%20(Arm)%5C%22.%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3ETo%20make%20matters%20more%20confusing%2C%20Windows%20Task%20Manager%20only%20shows%20you%20bitness%20in%20the%20platform%20column%2C%20so%20you%20only%20ever%20see%20%2232-bit%22%20and%20%2264-bit%22%2C%20but%20have%20no%20idea%20if%20it's%20running%20native%20ARM%20code%20or%20x86%20code%20via%20emulation.%26nbsp%3B%20I%20usually%20fall%20back%20to%20looking%20at%20the%20installation%20path%2C%20which%20Edge%20is%20violating.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Deleted
Not applicable

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"

8 Replies
Highlighted
I'm pretty sure the Edge developers are aware of that and are doing that intentionally for their Internal purposes or some future plans we're not aware of. so that's not really incorrect, just unconventional, and honestly for a software that is in alpha (dev) and pre-alpha (canary) state i think it's normal.
Highlighted

@HotCakeX 

Microsoft is not following there own best practice in directory install path.

Highlighted
I'm sure they know that better than you and me lol. they probably considered the fact that there will be a time when 4 different channels of the Edge will be out, they can't all go to the same directory.
Highlighted

@HotCakeX 

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

Highlighted
Google Chrome Canary goes to the Appdata for a reason, Microsoft decided to keep it that way and made their Canary chromium based one to go to that folder as well. i understand it is more sensible to You but to the actual Developers of the Edge/Google chrome/Chromium etc, AppData was more appropriate.
Highlighted

@HotCakeX 

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.

Highlighted

@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

Highlighted

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.