Access Microsoft Edge Legacy after installing the new version of Microsoft Edge
Learn how to access Microsoft Edge Legacy after installing the new version of Microsoft Edge.
While most organizations will want to replace Microsoft Edge Legacy with the new version, there are some situations where users will need access to both versions. For example:
- Helpdesk and support staff who interact with users who are using either or both versions of Microsoft Edge.
- Developers who support customers who are using either or both versions of Microsoft Edge.
This article applies to the Microsoft Edge Stable channel.
The procedures in this article apply to systems that have been updated with the latest security updates. When the new version of Microsoft Edge is installed, the old version (Microsoft Edge Legacy) will be hidden. By default, all attempts to launch the old version will redirect the user to the newly installed version of Microsoft Edge. This article describes how you can keep using Microsoft Edge Legacy after you install Microsoft Edge.
When using Windows Update deployment there is a known issue with the Allow Side by Side policy that produces a broken shortcut to Microsoft Edge Legacy in the all apps list. We recommend that you do not deploy with these methods or enable the AllowSxS policy until this issue can be resolved.
Quickstart: Side-by-side experience with Microsoft Edge Beta Channel and Microsoft Edge Legacy
Before using the detailed instructions in this article, consider the following 2 steps to let your users run Microsoft Edge Legacy and the Microsoft Edge Beta channel side-by-side.
Prevent the automatic install of the Stable Channel of Microsoft Edge by Windows Update.
Use the Blocker Toolkit to disable automatic delivery of Microsoft Edge.
Install the Beta channel of the new version of Microsoft Edge.
Read Additional information for information about Registry Key settings.
This side-by-side solution is less complex and requires less management than the detailed solution described in this article. However, this does mean that you'll be running the Beta Channel rather than the Stable Channel.
Side-by-side experience with Microsoft Edge Stable Channel and Microsoft Edge Legacy
Installing the Stable Channel of the next version of Microsoft Edge at the system-level will cause the current version (Microsoft Edge Legacy) to be hidden. If you want to let your users 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.
This group policy is documented here
To set up the side-by-side browser experience policy:
Install the Policy Definitions from Microsoft Edge for Business.
- Pick the CHANNEL/BUILD and PLATFORM you want to use, and then click GET POLICY FILES.
- Extract the zipped files.
- Copy msedge.admx and msedgeupdate.admx to the
- Copy msedge.adml and msedgeupdate.adml (from the appropriate language/locale directory) to the
Open the Group Policy Editor (gpedit.msc).
Under Computer Configuration, go to Administrative Templates>Microsoft Edge Update>Applications.
If you don't see the Microsoft Edge Update folder, verify that step 1 was completed correctly.
Under Applications, double-click "Allow Microsoft Edge Side by Side browser experience". See our best practice guidance before continuing to the next step.
By default, this group policy is set to "Not configured", which results in Microsoft Edge Legacy being hidden when the new version of Microsoft Edge is installed.
Select Enabled and then click OK.
Setting this policy will set the following Registry Key to '00000001':
- Value Name:
- Value Type:
Best practice guidance
For the best experience, the Allow Microsoft Edge Side by Side browser experience should be enabled before the new version of Microsoft Edge is deployed to your users' devices.
If the group policy is enabled after Microsoft Edge is deployed, there are the following side effects and required actions:
Allow Microsoft Edge Side by Side browser experience won't take effect until after the installer for the new version of Microsoft Edge is run again.
The installer can be run directly or automatically when the new version of Microsoft Edge updates.
Microsoft Edge Legacy will need to be re-pinned to Start or the Taskbar because the pin is migrated when the new version of Microsoft Edge is deployed.
Sites that were pinned to Start or the Taskbar for Microsoft Edge Legacy will be migrated to the new version of Microsoft Edge.
After the systems are fully updated and the Stable channel of the next version of Microsoft Edge is installed, the following registry key and value is set:
This key is over-written every time the Microsoft Edge Stable channel is updated. As a best practice, we recommend that you DO NOT delete this key to allow users to access both versions of Microsoft Edge.