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
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"

5 Replies
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.

@HotCakeX 

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

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.

@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

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.
Related Conversations
Tabs and Dark Mode
cjc2112 in Discussions on
35 Replies
Extentions Synchronization
Deleted in Discussions on
3 Replies
flashing a white screen while open new tab
Deleted in Discussions on
14 Replies
Stable version of Edge insider browser
HotCakeX in Discussions on
35 Replies