Dev channel update to 86.0.594.1 is live


Hello Insiders!  Today we’re releasing build 86.0.594.2 to the Dev channel.  Outside of the Dev channel, we’re excited to announce that Collections are now available for mobile users!  See for what to expect.  As for everything that’s new and noteworthy in the product: 


Added features:


  • Added the ability to install themes from the Google web store. 
  • Added a flag to that will allow the Backspace key to navigate a webpage back (or forward when combined with Shift).  This flag is currently disabled by default and needs to be manually enabled.
  • Added an option in settings to turn off suggestions from history and favorites when searching in the address bar. 
  • Added website permissions for virtual and augmented reality. 
  • Added a link between the Passwords Settings page and the Password Monitor Settings page. 
  • Added a management policy to Save Cookies When Microsoft Edge Closes.  Note that this policy is intended to be used in conjunction with policies to clear data when the browser is closed, and administrative templates will be updated later. 


Improved reliability: 


  • Fixed an issue where typing into the address bar sometimes crashes the browser. 
  • Fixed an issue where closing a tab sometimes crashes the browser. 
  • Fixed an issue where switching tabs sometimes crashes Edge on Insider versions of Windows. 
  • Fixed an issue where visiting certain sites in IE mode tabs sometimes crashes the browser.
  • Fixed an issue where tabs sometimes crash upon loading. 
  • Fixed an issue where logging into a site with a password saved in Edge sometimes crashes the tab. 
  • Fixed an issue where using System Restore causes Edge to no longer be able to launch.   
  • Fixed an issue where pinning a website to the Taskbar sometimes fails. 
  • Fixed an issue where the certificate viewer doesn’t work. 


Changed behavior: 


  • Fixed an issue where fullscreen videos sometimes don’t display properly.  Instead of entering fullscreen, they just zoom in and take up most of the browser window. 
  • Fixed an issue where the address bar sometimes stays in the “translating” state after translation of the webpage is complete.  
  • Fixed an issue where not all passwords are migrated from IE to Edge on versions of Windows older than 10. 
  • Fixed an issue where websites pinned to the Taskbar don’t have their badging when they’re supposed to.  (The badging is the text/number that sometimes appears on shortcut to tell the number of unread messages, etc.) 
  • Fixed an issue where items sometimes aren’t added to Collections correctly. 
  • Fixed an issue where ctrl + F sometimes leave highlighting on a page. 
  • Improved the UI when installing PWAs. 
  • Removed the keyboard shortcut for Save As on PDFs (ctrl + shift + S). 
  • Removed the ability to use Collections in Guest windows. 
  • Obsoleted the Safe Browsing Allow List Domains management policy since it’s been superseded by the SmartScreen Allow List Domains. 


Known issues: 


  • Mac users may see an issue signing into the browser or syncing their data.  We’ve identified the cause and are working to get a fix into next week’s Dev build. 
  • Users with certain hardware are seeing changes in scrolling behavior that are unintended.  For example, pages scroll much faster than they used to.  We’re currently investigating. 
  • Users of certain ad blocking extensions may experience playback errors on Youtube.  As a workaround, temporarily disabling the extension should allow playback to proceed.  See for more details. 
  • Users of the Kaspersky Internet Suite who have the associated extension installed may sometimes see webpages like Gmail fail to load.  This failure is due to the main Kaspersky software being out of date, and is thus fixed by making sure the latest version is installed. 
  • Some users are seeing favorites get duplicated after we made some previous fixes in that area. The most common way this is triggered is by installing the Stable channel of Edge and then signing into it with an account that has already signed into Edge before.  Fixing this should be easier now that the deduplicator tool is available.  However, we’ve also seen duplication happen when running the deduplicator on multiple machines before either machine has a chance to fully sync its changes, so while we wait for some of the fixes we’ve made to come to Stable, make sure to leave plenty of time in between runs of the deduplicator. 
  • After an initial fix for it recently, some users are still experiencing Edge windows becoming all black.  Opening the Browser Task Manager (keyboard shortcut is shift + esc) and killing the GPU process usually fixes it.  Note that this only appears to affect users with certain hardware and is most easily triggered by resizing an Edge window.  For users with discrete GPUs, updating graphics drivers may help. 
  • Some users are seeing “wobbling” behavior when scrolling using trackpad gestures or touchscreens, where scrolling in one dimension also causes the page to subtly scroll back and forth in the other.  Note that this only affects certain websites and seems to be worse on certain devices.  This is most likely related to our ongoing work to bring scrolling back to parity with Edge Legacy’s behavior, so if this behavior is undesirable, you can temporarily turn it off by disabling the edge://flags/#edge-experimental-scrolling flag. 
  • There are some issues where users with multiple audio output devices sometimes don’t get any sound from Edge. In one case, Edge becomes muted in the Windows Volume Mixer and unmuting it fixes it.  In another, restarting the browser fixes it. 


As always, we couldn’t do this without you, and a special thanks to our Collections users for their help in getting the feature onto mobile! 


47 Replies

@sdmmr Oh and in the meantime, there are plenty of extensions that let you assign a keyboard shortcut to tab duplication, not to mention middle-clicking the refresh button!  


@josh_bodner To close the loop here, the recent update to 86.0.601.1 has "fixed" whatever was causing the cookies not to be set, and the behaviour has gone back to normal.


Thanks for the help in the interim.




@josh_bodner Thanks for your suggestion! On the other hand, do you have any update about the HTTP_ACCEPT_LANGUAGE issue?


@sdmmr Where else can you get it to happen?  Specifically, does Chrome Canary or Chrome Dev do the same thing?  That will help us narrow down where to start looking.  


@josh_bodner Yes, Chrome Canary and Chrome Dev do the same thing.

For a clear result, I changed Chrome UI to English (United States) in Settings and attached screenshots for your reference.
You can see that the HTTP_ACCEPT_LANGUAGE field from Normal window returns Preferred Language, but in incognito mode returns UI Language.
I also attached an example to show that websites cannot detect Preferred Language in incognito mode.

Edge Stable (Edge 84) does not have this issue.


@sdmmr I had a feeling this was something that we inherited from Chromium!  Thanks for confirming, I'll let the right people know!  


@sdmmr The InPrivate Accept-Language behavior was inherited from upstream Chrome: We're still discussing whether we should keep this behavior.


@ericlaw Thanks for reporting! I understand the concern about privacy issue.
I think that users should be able to select which language(s) can be preferred in InPrivate mode. For example, Edge can add a "Allow in InPrivate" checkbox in "More actions …" next to a language, just like Extensions.