You’ll Be Able to Run New Edge and Edge Legacy Side-by-Side

A Microsoft support document explains how you’ll be able to run the old Edge and the new Edge together if you want. The bad news? It requires it requires Group Policy, which leaves out Windows 10 Home users. (There are Registry-based workarounds, of course, so I’m sure we’ll find out what that is before the new Edge launches.)

“Installing the Stable channel of the next version of Microsoft Edge at system-level will cause the current version (Microsoft Edge Legacy) to be hidden,” the support document notes. “If you want to let your users to see both versions of Microsoft Edge side-by-side in Windows, you can enable this experience by setting the Allow Microsoft Edge Side by Side browser experience group policy to ‘Enabled’.”

Windows Intelligence In Your Inbox

Sign up for our new free newsletter to get three time-saving tips each Friday — and get free copies of Paul Thurrott's Windows 11 and Windows 10 Field Guides (normally $9.99) as a special welcome gift!

"*" indicates required fields

This field is for validation purposes and should be left unchanged.

To enable this, open the Group Policy Editor, navigate to Computer Configuration > Administrative Templates > Microsoft Edge Update > Applications and select “Allow Microsoft Edge Side by Side browser experience.” Then, click the Edit policy setting link, and in the window that opens, select Enabled and then click OK.

Microsoft also notes that the Allow Microsoft Edge Side by Side browser experience should be enabled before the new version of Microsoft Edge is deployed for the best experience. If you don’t do it ahead of time, you’ll have a few issues to deal with. For example, you’ll need to run the new Edge installer again before you can both versions side-by-side. You’ll have to re-pin Microsoft Edge Legacy to Start or the taskbar. And any sites that were pinned to Start or the taskbar for Microsoft Edge Legacy will be migrated to the new Edge.

Given this, I expect a simpler solution for consumers to appear as well, so stay tuned.

Share post

Please check our Community Guidelines before commenting

Conversation 25 comments

  • hrlngrv

    Premium Member
    19 December, 2019 - 4:34 pm

    <p>Will there be any more updates to legacy Edge? I haven't been paying attention: when was it last updated, with 1909? If it won't be updated going forward, how long until it becomes unsafe to use?</p>

  • wbhite

    Premium Member
    19 December, 2019 - 4:53 pm

    <p>Out of curiosity, why would anyone need or want legacy Edge? It's not like IE, where thousands of corporate LOB/Intranet applications relied on it. I doubt anything has been developed specifically for Edge, and other than a "screw you" to the Chromium project and slightly better scrolling, I don't see the benefit of having this.</p>

    • gmj

      19 December, 2019 - 5:45 pm

      <blockquote><em><a href="#499898">In reply to wbhite:</a></em></blockquote><p>For those using legacy Edge, there may be some features in legacy Edge not yet available in new Edge ( …</p>

      • Paul Thurrott

        Premium Member
        20 December, 2019 - 8:29 am

        We’ve written about this. Legacy Edge is being kept around to run the components that app makers rely on.

    • JCerna

      Premium Member
      20 December, 2019 - 2:12 am

      <blockquote><a href="#499898"><em>In reply to wbhite:</em></a><em> the main thing for us is inking, old edge has good inking tools for pdf and websites that works great for presenting. New edge has nothing that does this yet.</em></blockquote><p><br></p>

    • craigb

      20 December, 2019 - 6:49 pm

      <blockquote><em><a href="#499898">In reply to wbhite:</a></em></blockquote><p>Sometimes when using SAAS browser based applications, often the back end server sees your browser and account as one in the same so you can't have 2 accounts open in the one browser or it confuses the server. One work around is to use different browsers so that the server sees two different instances. Another work around is to use an InPrivate mode in a new window. However there have been numerous times that having Credge and Edge has come in really handy. Poor old IE cant render a lot of modern pages so isn't of any use here unfortunately. So this is why it would be handy to have Credge and Edge side by side.</p>

  • Pommster

    19 December, 2019 - 6:02 pm

    <p>Does that basically mean there will be three web browsers in Windows 10 – Internet Explorer, Legacy Edge and new Edge?</p>

  • kcnewf

    19 December, 2019 - 7:54 pm

    <p>I am sure that all 2 users running Legacy Edge on Windows 10 Home are anxiously waiting for this critical work around.</p>

  • jblank46

    19 December, 2019 - 9:53 pm

    <p>New Edge is literally so much better than old Edge this would definitely be something for extreme edge cases.. no pun intended!</p>

  • remc86007

    20 December, 2019 - 5:58 am

    <p>When are they going to implement real smooth scrolling? Old edge is still infinitely smoother to use than new edge and chrome and somewhat better with touch support still. </p>

  • rufusw

    20 December, 2019 - 9:36 am

    <p>I have Windows 10 Pro 1903 and don't appear to have access to "Computer Configuration &gt; Administrative Templates &gt; Microsoft Edge Update &gt; Applications" group policy. The support document is under "Microsoft Edge in the enterprise" – is this an Enterprise only group policy?</p><p><br></p><p>Edit: It looks like you need 1909 installed – the support document states "<span style="color: rgb(23, 23, 23);">The procedures in this article apply to systems that have been updated with the latest security updates, up to and including November 2019."</span></p>

    • keegan

      29 January, 2020 - 7:46 pm

      <blockquote><em><a href="#500265">In reply to rufusw:</a></em></blockquote><p> I'm running Win 10 Pro 1909 (build 18363.628) and still don't see it in the policy editor. </p>

  • mjdamron

    20 December, 2019 - 3:15 pm

    <p>Who wants to run the old Edge?</p>

  • IanYates82

    Premium Member
    21 December, 2019 - 3:52 am

    <p>I'll enable this. As a Web-based line of business app user, I'll have customers still using legacy edge for a while so I need it around for testing purposes. </p><p><br></p>

  • Fuller1754

    11 January, 2020 - 3:21 pm

    <p>There ought to be <em>no</em> way at all of running both of these side by side. Once installed, the new version of Edge should completely replace and override the old version in every case, with no workaround. Alas, Microsoft has always been overly sensitive to legacy concerns. Should Mozilla have let Firefox 57 (the new "Quantum" version), run alongside Firefox 56 after the update installed? What a mess that would be. Microsoft kept IE available in Windows due to legitimate compatibility issues for some LOB applications that depended on it. With the built-in IE mode, the new Edge should also trigger an irreversible uninstall of IE (it probably won't though, and IE will linger to collect dust in the ever-growing attic of Windows code). In the case of legacy Edge, what possible compatibility concerns could there be? Just get rid of it, for goodness' sake! Those (and look, I'm one of them) who liked features like Set Tabs Aside and Ask Cortana will just have to move on. The new Edge is way better.</p>

  • IanYates82

    Premium Member
    15 January, 2020 - 12:49 am

    <p>I've just gone to enable this on my domain. Had some trouble getting the group policy editor to display it so I read the docs…</p><p><br></p><p>Visit here for the official Microsoft docs page about the policy: <a href="; target="_blank"></a></p><p>It literally says the registry key that needs to be set to make this work. It ought to behave for Windows Home too</p><p><br></p><p>Here's the relevant bit extracted from the docs…. (sorry for dodgy cut/paste formatting)</p><p><br></p><h5>Windows Registry Settings</h5><ul><li>Path: HKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftEdgeUpdate</li><li>Value Name: Allowsxs</li><li>Value Type: REG_DWORD</li></ul><p>And the value should be <span style="background-color: rgb(46, 46, 46); color: rgb(227, 227, 227);">0x00000001</span></p>

    • IanYates82

      Premium Member
      15 January, 2020 - 12:49 am

      <blockquote><em><a href="#513180">In reply to IanYates82:</a></em></blockquote><p>I hope this is handy for someone :)</p>

Windows Intelligence In Your Inbox

Sign up for our new free newsletter to get three time-saving tips each Friday

"*" indicates required fields

This field is for validation purposes and should be left unchanged.

Thurrott © 2023 Thurrott LLC