SOLVED
Home

"Stable" Edge revisited.

%3CLINGO-SUB%20id%3D%22lingo-sub-927476%22%20slang%3D%22en-US%22%3E%22Stable%22%20Edge%20revisited.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-927476%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20%22stable%22%20Edge%20version%20story%20is%20making%20the%20rounds%20again%2C%20release%20is%20supposed%20to%20be%20imminent%20and%20it%20will%20completely%20disable%20Edge%2Fclassic.%3CBR%20%2F%3ETrue%20or%20not%20I%20have%20a%20few%20questions%20about%20this%3A%3CBR%20%2F%3E-After%20installing%20Edge%2FCanary%20so%20many%20months%20ago%20existing%20pinned%20desktop%20shortcuts%20(Tiles)%20and%20sites%20pinned%20to%20the%20taskbar%20are%20still%20opening%20in%20Edge%2FClassic%20so%20far.%20Will%20all%20these%20be%20converted%20and%20installed%20as%20apps%20after%20installing%20the%20stable%20version%3F%3CBR%20%2F%3E-If%20yes%2C%20would%20it%20not%20be%20advisable%20to%20release%20a%20canary%20version%20for%20us%20to%20test%20this%20before%20committing%20to%20completely%20disabling%20E%2Fclassic%3F%3CBR%20%2F%3E-Has%20anybody%20installed%20the%20%22stable%22%20version%20that%20can%20enlighten%20me%3F%20Just%20curious.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-927610%22%20slang%3D%22en-US%22%3ERe%3A%20%22Stable%22%20Edge%20revisited.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-927610%22%20slang%3D%22en-US%22%3EThey're%20still%20not%20done%20yet%20implementing%20every%20required%20feature%20and%20sync%2Fimport%20is%20incomplete.%20Give%20it%20a%20few%20more%20months.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-927831%22%20slang%3D%22en-US%22%3ERe%3A%20%22Stable%22%20Edge%20revisited.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-927831%22%20slang%3D%22en-US%22%3EThis%20is%20the%20only%20official%20documentation%20regarding%20stable%20new%20Edge%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2FDeployEdge%2Fmicrosoft-edge-sysupdate-windows-updates%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2FDeployEdge%2Fmicrosoft-edge-sysupdate-windows-updates%3C%2FA%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%22-After%20installing%20Edge%2FCanary%20so%20many%20months%20ago%20existing%20pinned%20desktop%20shortcuts%20(Tiles)%20and%20sites%20pinned%20to%20the%20taskbar%20are%20still%20opening%20in%20Edge%2FClassic%20so%20far.%20Will%20all%20these%20be%20converted%20and%20installed%20as%20apps%20after%20installing%20the%20stable%20version%3F%22%3CBR%20%2F%3E%3CBR%20%2F%3EAccording%20to%20that%20article%2C%20Yes%3CBR%20%2F%3E%3CBR%20%2F%3E%22-If%20yes%2C%20would%20it%20not%20be%20advisable%20to%20release%20a%20canary%20version%20for%20us%20to%20test%20this%20before%20committing%20to%20completely%20disabling%20E%2Fclassic%3F%22%3CBR%20%2F%3E%3CBR%20%2F%3EYes%20of%20course%2C%20there%20will%20most%20likely%20be%20beta%20tests%20before%20anything%20becomes%20final%3CBR%20%2F%3E%3CBR%20%2F%3E%22-Has%20anybody%20installed%20the%20%22stable%22%20version%20that%20can%20enlighten%20me%3F%20Just%20curious.%22%3CBR%20%2F%3E%3CBR%20%2F%3EI%20haven't%20but%20if%20you%20wanna%20do%20it%2C%20better%20install%20it%20on%20Windows%20Sandbox%20just%20to%20be%20on%20the%20safe%20side%20%3A)%3C%2Fimg%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-927933%22%20slang%3D%22en-US%22%3ERe%3A%20%22Stable%22%20Edge%20revisited.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-927933%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F87405%22%20target%3D%22_blank%22%3E%40Jacques%20Van%20de%20Meerssche%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CEM%3E-After%20installing%20Edge%2FCanary%20so%20many%20months%20ago%20existing%20pinned%20desktop%20shortcuts%20(Tiles)%20and%20sites%20pinned%20to%20the%20taskbar%20are%20still%20opening%20in%20Edge%2FClassic%20so%20far.%20Will%20all%20these%20be%20converted%20and%20installed%20as%20apps%20after%20installing%20the%20stable%20version%3F%3C%2FEM%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20don't%20think%20that%20anyone%20knows%20the%20answer%20to%20this%20question.%20The%20so-called%20%22Stable%22%20version%20has%20not%20been%20officially%20released%2C%20and%20Microsoft%20(to%20my%20knowledge)%20has%20made%20no%20announcements%20or%20statements%20at%20all%20concerning%20the%20build%2C%20how%20deployment%20will%20work%2C%20or%20what%20will%20happen%20when%20Edge%20Chromium%20is%20released.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20leaked%20%22Stable%22%20version%20is%20a%20older%20than%20the%20current%20Beta%20version%20released%20some%20weeks%20ago%20(the%20current%20Beta%20build%20is%2078.0.276.17%2C%20and%20the%20%22Stable%22%20build%20is%2078.0.276.14)%2C%20so%20it%20seems%20unlikely%20that%20the%20leaked%20%22Stable%22%20version%20will%20be%20the%20version%20actually%20released%20by%20Microsoft.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EReports%20from%20folks%20who%20have%20installed%20the%20%22Stable%22%20suggest%20two%20things%3A%20(1)%20when%20the%20%22RTM%22%20version%20of%20Edge%20Chromium%20is%20released%2C%20it%20will%20effectively%20remove%20Edge%20(Classic)%20from%20Windows%2010%2C%20and%20(2)%20be%20somehow%20integrated%20into%20Windows%2010%20in%20a%20way%20that%20will%20not%20allow%20the%20user%20to%20uninstall%20it.%20That%20is%20not%20certain%2C%20but%20that%20is%20what%20seems%20to%20have%20been%20happening%20for%20those%20who%20download%20and%20install%20the%20leaked%20%22Stable%22%20build.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMy%20guess%2C%20for%20what%20it%20is%20worth%20and%20nothing%20more%2C%20is%20that%20Microsoft%20is%20using%20the%20leaked%20%22Stable%22%20version%20to%20test%20deployment%20in%20the%20wild%2C%20testing%20to%20make%20sure%20that%20deployment%20processes%20work%20correctly%20when%20the%20%22Stable%22%20build%20is%20released%20outside%20Microsoft.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20think%20that%20because%20(1)%20the%20leaked%20build%20deploys%20from%20non-public%20directories%20from%20two%20servers%20used%20by%20Microsoft%20to%20deploy%20software%20(go.microsoft.com%20and%20c2rsetup.officeapps.live.com)%2C%20(2)%20an%20early%20Beta%20build%20was%20leaked%20from%20the%20two%20servers%20about%20two%20weeks%20before%20the%20Beta%20Channel%20was%20opened%20to%20Insiders%2C%20and%20the%20leaked%20Beta%20version%20was%20not%20the%20version%20released%20through%20the%20Beta%20Channel%2C%20(3)%20the%20leaked%20%22Stable%22%20build%20is%20weeks%20behind%20current%20development%2C%20and%20(4)%20the%20%22to%20do%22%20list%20Microsoft%20has%20been%20publishing%20on%20this%20Forum%20suggests%20that%20Microsoft%20has%20a%20lot%20of%20work%20to%20do%20before%20Edge%20Chromium%20is%20ready%20to%20be%20released.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CEM%3E-If%20yes%2C%20would%20it%20not%20be%20advisable%20to%20release%20a%20canary%20version%20for%20us%20to%20test%20this%20before%20committing%20to%20completely%20disabling%20E%2Fclassic%3F%3C%2FEM%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIt%20would%20make%20lots%20of%20sense%20for%20Microsoft%20to%20release%20a%20Stable%20version%20that%20it%20actually%20intends%20to%20release%20to%20Edge%20Chromium%20insiders%20for%20testing.%20That%20is%20what%20Microsoft%20does%20with%20Windows%2010%20versions%2C%20and%20it%20would%20be%20very%20odd%20for%20Microsoft%20to%20release%20Edge%20Chromium%20without%20testing%20the%20release%20version%20beforehand%20using%20Insiders.%20Pre-release%20testing%20and%20four%20channels%20(Canary%2C%20Dev%2C%20Beta%2C%20Stable)%20is%20the%20practice%20with%20open%20source%20software%20in%20general%2C%20and%20it%20is%20the%20practice%20with%20Chromium.%20I%20assume%20that%20Microsoft%20will%20not%20deviate%20from%20standard%20practice.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CEM%3E-Has%20anybody%20installed%20the%20%22stable%22%20version%20that%20can%20enlighten%20me%3F%20Just%20curious.%3C%2FEM%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20not%2C%20because%20the%20%22Stable%22%20version%2C%20according%20to%20reports%2C%20cannot%20be%20uninstalled%20through%20the%20usual%20methods.%20And%20frankly%2C%20there's%20no%20point%20to%20installing%20it%20for%20me%2C%20since%20the%20current%20Beta%20version%20is%20a%20newer%20build%20than%20the%20leaked%20%22Stable%22%20version.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-928028%22%20slang%3D%22en-US%22%3ERe%3A%20%22Stable%22%20Edge%20revisited.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-928028%22%20slang%3D%22en-US%22%3E%3CBLOCKQUOTE%3E%3CHR%20%2F%3E%3CP%3E%3CSPAN%3EI%20don't%20think%20that%20anyone%20knows%20the%20answer%20to%20this%20question.%20The%20so-called%20%22Stable%22%20version%20has%20not%20been%20officially%20released%2C%20and%20Microsoft%20(to%20my%20knowledge)%20has%20made%20no%20announcements%20or%20statements%20at%20all%20concerning%20the%20build%2C%20how%20deployment%20will%20work%2C%20or%20what%20will%20happen%20when%20Edge%20Chromium%20is%20released.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CHR%20%2F%3E%3C%2FBLOCKQUOTE%3E%3CP%3EI%20put%20the%20link%20up%20there%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERead%20under%20%22Updates%20and%20the%20user%20experience%22%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2FDeployEdge%2Fmicrosoft-edge-sysupdate-windows-updates%23microsoft-edge-and-the-windows-release-cycle%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2FDeployEdge%2Fmicrosoft-edge-sysupdate-windows-updates%23microsoft-edge-and-the-windows-release-cycle%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhen%20all%20the%20updates%20are%20applied%20AND%20the%20Stable%20channel%20of%20the%20next%20version%20of%20Microsoft%20Edge%20is%20installed%20at%20the%20system-level%2C%20the%20following%20changes%20will%20take%20effect%20on%20the%20system%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CUL%3E%3CLI%3E%3CP%3E%3CSTRONG%3EAll%20start%20menu%20pins%2C%20tiles%2C%20and%20shortcuts%20for%20the%20current%20version%20of%20Microsoft%20Edge%20will%20migrate%20to%20the%20next%20version%20of%20Microsoft%20Edge.%3C%2FSTRONG%3E%3C%2FP%3E%3C%2FLI%3E%3CLI%3E%3CP%3E%3CSTRONG%3EAll%20taskbar%20pins%20and%20shortcuts%20for%20the%20current%20version%20of%20Microsoft%20Edge%20will%20migrate%20to%20the%20next%20version%20of%20Microsoft%20Edge.%3C%2FSTRONG%3E%3C%2FP%3E%3C%2FLI%3E%3CLI%3E%3CP%3EThe%20next%20version%20of%20Microsoft%20Edge%20will%20be%20pinned%20to%20the%20taskbar.%20If%20the%20current%20version%20of%20Microsoft%20Edge%20is%20already%20pinned%2C%20it%20will%20be%20replaced.%3C%2FP%3E%3C%2FLI%3E%3CLI%3E%3CP%3EThe%20next%20version%20of%20Microsoft%20Edge%20will%20add%20a%20shortcut%20to%20the%20desktop.%20If%20the%20current%20version%20of%20Microsoft%20Edge%20already%20has%20a%20shortcut%2C%20it%20will%20be%20replaced.%3C%2FP%3E%3C%2FLI%3E%3CLI%3E%3CP%3E%3CSTRONG%3EMost%20protocols%20that%20Microsoft%20Edge%20handles%20by%20default%20will%20be%20migrated%20to%20the%20next%20version%20of%20Microsoft%20Edge.%3C%2FSTRONG%3E%3C%2FP%3E%3C%2FLI%3E%3CLI%3E%3CP%3ECurrent%20Microsoft%20Edge%20will%20be%20hidden%20from%20all%20UX%20surfaces%20in%20the%20OS%2C%20including%20settings%2C%20all%20apps%2C%20and%20any%20file%20or%20protocol%20support%20dialogs.%3C%2FP%3E%3C%2FLI%3E%3CLI%3E%3CP%3E%3CSTRONG%3EAll%20attempts%20to%20launch%20the%20current%20version%20of%20Microsoft%20Edge%20will%20redirect%20to%20the%20next%20version%20of%20Microsoft%20Edge.%3C%2FSTRONG%3E%3C%2FP%3E%3C%2FLI%3E%3C%2FUL%3E%3CP%20class%3D%22alert-title%22%3E%26nbsp%3B%3C%2FP%3E%3CP%20class%3D%22alert-title%22%3E%3CEM%3ENote%3A%3C%2FEM%3E%3C%2FP%3E%3CP%3E%3CEM%3EUser-level%20installs%20won%E2%80%99t%20trigger%20these%20behaviors.%3C%2FEM%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Eso%20%3CSTRONG%3EMicrosoft%20has%3C%2FSTRONG%3E%20%3CSTRONG%3Emade%20their%20official%20announcements%3C%2FSTRONG%3E%2C%20it's%20just%20that%20their%20official%20stable%20Edge%20browser%20is%20not%20released%20yet.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Jacques Van de Meerssche
Contributor

The "stable" Edge version story is making the rounds again, release is supposed to be imminent and it will completely disable Edge/classic.
True or not I have a few questions about this:
-After installing Edge/Canary so many months ago existing pinned desktop shortcuts (Tiles) and sites pinned to the taskbar are still opening in Edge/Classic so far. Will all these be converted and installed as apps after installing the stable version?
-If yes, would it not be advisable to release a canary version for us to test this before committing to completely disabling E/classic?
-Has anybody installed the "stable" version that can enlighten me? Just curious.

4 Replies
They're still not done yet implementing every required feature and sync/import is incomplete. Give it a few more months.
Solution
This is the only official documentation regarding stable new Edge
https://docs.microsoft.com/en-us/DeployEdge/microsoft-edge-sysupdate-windows-updates

"-After installing Edge/Canary so many months ago existing pinned desktop shortcuts (Tiles) and sites pinned to the taskbar are still opening in Edge/Classic so far. Will all these be converted and installed as apps after installing the stable version?"

According to that article, Yes

"-If yes, would it not be advisable to release a canary version for us to test this before committing to completely disabling E/classic?"

Yes of course, there will most likely be beta tests before anything becomes final

"-Has anybody installed the "stable" version that can enlighten me? Just curious."

I haven't but if you wanna do it, better install it on Windows Sandbox just to be on the safe side :)

@Jacques Van de Meerssche 

 

-After installing Edge/Canary so many months ago existing pinned desktop shortcuts (Tiles) and sites pinned to the taskbar are still opening in Edge/Classic so far. Will all these be converted and installed as apps after installing the stable version?

 

I don't think that anyone knows the answer to this question. The so-called "Stable" version has not been officially released, and Microsoft (to my knowledge) has made no announcements or statements at all concerning the build, how deployment will work, or what will happen when Edge Chromium is released.

 

The leaked "Stable" version is a older than the current Beta version released some weeks ago (the current Beta build is 78.0.276.17, and the "Stable" build is 78.0.276.14), so it seems unlikely that the leaked "Stable" version will be the version actually released by Microsoft.

 

Reports from folks who have installed the "Stable" suggest two things: (1) when the "RTM" version of Edge Chromium is released, it will effectively remove Edge (Classic) from Windows 10, and (2) be somehow integrated into Windows 10 in a way that will not allow the user to uninstall it. That is not certain, but that is what seems to have been happening for those who download and install the leaked "Stable" build.

 

My guess, for what it is worth and nothing more, is that Microsoft is using the leaked "Stable" version to test deployment in the wild, testing to make sure that deployment processes work correctly when the "Stable" build is released outside Microsoft.

 

I think that because (1) the leaked build deploys from non-public directories from two servers used by Microsoft to deploy software (go.microsoft.com and c2rsetup.officeapps.live.com), (2) an early Beta build was leaked from the two servers about two weeks before the Beta Channel was opened to Insiders, and the leaked Beta version was not the version released through the Beta Channel, (3) the leaked "Stable" build is weeks behind current development, and (4) the "to do" list Microsoft has been publishing on this Forum suggests that Microsoft has a lot of work to do before Edge Chromium is ready to be released.

 

-If yes, would it not be advisable to release a canary version for us to test this before committing to completely disabling E/classic?

 

It would make lots of sense for Microsoft to release a Stable version that it actually intends to release to Edge Chromium insiders for testing. That is what Microsoft does with Windows 10 versions, and it would be very odd for Microsoft to release Edge Chromium without testing the release version beforehand using Insiders. Pre-release testing and four channels (Canary, Dev, Beta, Stable) is the practice with open source software in general, and it is the practice with Chromium. I assume that Microsoft will not deviate from standard practice.

 

-Has anybody installed the "stable" version that can enlighten me? Just curious.

 

I have not, because the "Stable" version, according to reports, cannot be uninstalled through the usual methods. And frankly, there's no point to installing it for me, since the current Beta version is a newer build than the leaked "Stable" version.


I don't think that anyone knows the answer to this question. The so-called "Stable" version has not been officially released, and Microsoft (to my knowledge) has made no announcements or statements at all concerning the build, how deployment will work, or what will happen when Edge Chromium is released.

 


I put the link up there,

 

Read under "Updates and the user experience"

https://docs.microsoft.com/en-us/DeployEdge/microsoft-edge-sysupdate-windows-updates#microsoft-edge-...

 

When all the updates are applied AND the Stable channel of the next version of Microsoft Edge is installed at the system-level, the following changes will take effect on the system:

 

  • All start menu pins, tiles, and shortcuts for the current version of Microsoft Edge will migrate to the next version of Microsoft Edge.

  • All taskbar pins and shortcuts for the current version of Microsoft Edge will migrate to the next version of Microsoft Edge.

  • The next version of Microsoft Edge will be pinned to the taskbar. If the current version of Microsoft Edge is already pinned, it will be replaced.

  • The next version of Microsoft Edge will add a shortcut to the desktop. If the current version of Microsoft Edge already has a shortcut, it will be replaced.

  • Most protocols that Microsoft Edge handles by default will be migrated to the next version of Microsoft Edge.

  • Current Microsoft Edge will be hidden from all UX surfaces in the OS, including settings, all apps, and any file or protocol support dialogs.

  • All attempts to launch the current version of Microsoft Edge will redirect to the next version of Microsoft Edge.

 

Note:

User-level installs won’t trigger these behaviors.

 

so Microsoft has made their official announcements, it's just that their official stable Edge browser is not released yet.

Related Conversations
Tabs and Dark Mode
cjc2112 in Discussions on
46 Replies
Extentions Synchronization
Deleted in Discussions on
3 Replies
Stable version of Edge insider browser
HotCakeX in Discussions on
35 Replies
How to Prevent Teams from Auto-Launch
chenrylee in Microsoft Teams on
29 Replies
flashing a white screen while open new tab
Deleted in Discussions on
14 Replies
Security Community Webinars
Valon_Kolica in Security, Privacy & Compliance on
13 Replies