Microsoft Details Its Migration Plans for the New Microsoft Edge

Posted on December 17, 2019 by Mehedi Hassan in Microsoft Edge, Web browsers with 14 Comments

Microsoft quietly released some new documentation recently, detailing how the company plans to launch its new Chrome-based Microsoft Edge browser. The company has been working on this new browser for a little while, and we are less than a month away from the public release.

Microsoft’s new Edge browser is set to launch publicly on January 15, 2020. The company is now detailing how it plans to migrate the older Microsoft Edge browser to the next-gen Edge in Windows 10.

In a support document, Microsoft notes that the company will actually deliver the new Edge browser through an automatic update for Windows 10 users running version 1803 or newer. Those who don’t want to get the new Edge browser automatically through a Windows update can use a script that will prevent Windows from automatically installing the new Edge browser itself.

As for the migration process, Microsoft has detailed exactly how the new Edge browser will take the old Edge’s place. The changes here are pretty obvious, but it is still important to understand exactly how Microsoft is going to replace the older Edge browser on a technical level. Microsoft says it has already made changes to Windows 10 and the older Edge browser to support the migration.

  • 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.

January 15 is going to be a big day for the Microsoft Edge team. They have so far done a great job with this new browser, so if they nail the public launch, it’s only going to get better from here onwards.

Tagged with ,

Join the discussion!


Don't have a login but want to join the conversation? Become a Thurrott Premium or Basic User to participate

Comments (14)

14 responses to “Microsoft Details Its Migration Plans for the New Microsoft Edge”

  1. Daekar

    I can't wait to see how our IT department handles this. I'm pretty sure it will be "just don't deploy this update for a year or two" but you never know.

  2. Nischi

    I'd glady switch over if they just implemented all the sync settings for open tabs and the rest.

  3. Lauren Glenn

    Now, can we get a native Edgium component for .NET so we don't have to go spend $1000+ on a component to just use a web browser? Sure there are free ones, but they're complicated to install sometimes. The old one worked great until you needed HTML 5 or something. i hope that we get a real component in .NET embedded so we don't have to buy those expensive apps to do a simple web browser.

  4. codymesh

    can the beta remain installed aside the final release?

  5. spacein_vader

    I don't mind new shortcuts replacing the old but surely if the old have been removed it should respect that decision and not put new ones in? No other browser does so without asking in the setup first.

    • t-b.c

      In reply to spacein_vader: Agreed, though this is a small complaint. It takes all of two seconds to delete a desktop icon. I'm thinking they should permit users to run the older version if they find that some services will not work. For instance, I am a Comcast subscriber and streaming TV does not work in Chredge, or Chrome. It does work in Edge. My workflow involves watching news channels in a window.
  6. zeratul456

    How do we migrate from beta to stable?

  7. jlv632

    I wonder if "Windows 10 in S Mode" will be a barrier of any sorts? I've been waiting for it on my Surface Go which is still in S Mode. Here is hoping.

  8. dsamuilov

    Will MSIE 11 be finally removed along with old Edge? Given that new Edge provides a special compatibility layer for MSIE? Or are we still going to have to deal with this anachronistic eyesore?

    • IanYates82

      In reply to dsamuilov:

      IE is hanging around for quite some time. The rendering engine is embedded into probably tens or hundreds of thousands of apps from well-known apps to little line of business apps.

      The same with the EdgeHTML engine, except the embedding was mainly UWP apps so probably a thousand apps affected? Unlike Internet Explorer though, they're removing the Edge "wrapper" around that engine completely from Windows.

      For IE though, It's already hard to find in Windows. You're not launching it by accident.

  9. Awhispersecho

    Will bookmarks migrate as well or will I once again lose them? (Not that they work with current Edge but ya know.)