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

@josh_bodner I now see the Alt-Tab settings options to display none, some, all Edge tabs when pressing alt-tab but no matter which option I choose, I only see open windows and not all the open tabs.

The settings menu always appears on a different monitor in a multi-monitor setup. This bug has crept into stable even though I had formally reported it since I noticed it in the last dev before the break.



Nice to see the Tab Hover Card Images flag turn up that's been in Google Chrome for ages.


And it would have been nice that we finally got access to the edge:flags page in the last Android Edge release ... apart from the fact that it only shows ONE flag!


But ...


Still no History and Open Tabs sync in desktop or Android Edge. In a world where most people have a smart phone, and a lot of them also a desktop/laptop so likely to need syncing, it beggars belief you'd public release the software without all the syncs, and even more we'd be this many months along still without it.


The no-rubber-banding scrolling personality switch is still a flag, not a setting, and you are STILL saying in each of these Dev release posts that the ability to turn it off and keep normal scrolling is temporary. So long as that is the case I will never change to Edge.


And still no ability to pin chosen topsites to the new tab page or have 'darkified' web pages in Android Edge.


So I run each release of desktop Canary and Dev and Android Beta precisely once for about two minutes just to check for any development in any of these things, and week after week, month after month there's none, while the developers play around with adding more and more pretty bells and whistles I couldn't care less about.


The fact that there have been so many desktop and Android releases over so many months without a single one of the issues I care about progressed at all leaves me very depressed and ready to give up. And now your colleagues have screwed up the Microsoft Launcher for Android, while other of your colleagues have screwed up To Do. I'm thinking its time to give up on Microsoft software.



Not sure if this has been addressed but while using build 86.0.587.0 on Windows 10 version 2004, there seems be an issue with uploading pictures to Facebook. When I try upload pictures to Facebook, the dialog box appears behind the Edge window and full screen. This also freezes my computer for a few seconds. I have only noticed this strange behavior when I use Facebook. I often upload pictures to Weebly without any issue. 

@david-bell the Edge feature responsible for telling windows about all its open tabs so it can put them in the alt+tab menu had to be temporarily disabled (it was one of the causes of the fullscreen issues people have been seeing recently), so that's probably why it's not working at the moment.  

@tobassam900 We've got an engineer working on it!  A lot more people started reporting it over the past week for some reason, which helped bring it to our attention.  

@js123 when you say "behind", is it still usable, but just has to be brought to the foreground, or is it functionally broken when that happens?  



It is functionally broken when that happens. I can't use Alt-Tab or Windows-Tab to bring it forward.

@josh_bodner Hi! Just updated to this version and the "Display variable values inline while debugging" in DevTools is no longer working. 


I've tried deselecting the setting and selecting it again, computer restart and no luck.


Is there anything  I can provide you with ofr further analysis of the issue?





I still get a crash every time Edge updates if I click on the update window "Close" button after the browser has relaunched with the new version. The only way to not get the crash is to quit the browser, then click "Close" and relaunch the browser once again.

@js123 do you know if it's only happening in your profile?  Like, does it happen in Guest windows?  Or can you install Canary and see if it happens there too?  

@divosuplente can you file feedback from within the F12 tools?  That will both get the relevant logs as well as make sure it opens a bug in our database.  

@dejan008 is the crash any time you close the window after updating, or is it just if you close it very soon after the update happens?  


Update: For anyone interested, it's a bug in the chromium core, related to a change in the SVG engine. They meanwhile fixed it in Chrome Canary v 86.0.4226.0, so hopefully it will be included in Edge Dev and Canary within the next couple days. 

Since v 86.0.594.1 I can't login to discord anymore, on both Dev and Canary. I've tested on different machines, I always just get this error screen:


Screenshot (6).png


And yes, it definitely worked before the update to 86.0.594.1.

Please help!



@josh_bodner I do let the browser fully load (several windows open and probably 30-40 tabs total). Then I did wait another 10 seconds or so and only then pressed the "Close" button the last time. One of the previous upgrades when the crash happened I did send feedback using the Edge "Send Feedback" feature so you should have the relevant logs from that one.

I confirm the issue with Discord

@josh_bodner Hi! Never done it, but will try :) FYI, I've tried it in InPrivate mode, and the same is happening. Also, it doesn't happen in Canary.



@Neon01 We've pumped in the fix, but it's still in the process of being merged.  So unfortunately since it didn't make it into today's Canary, it likely also won't be in Dev until the week after next.  

@dejan008 Good to know, our system does look for crashes that happen around the same time as when feedback is sent, so we've definitely got it then.  One other thing to look out for if you've got Canary installed is if the same thing happens there.  If not, we've either already fixed it, or it's something about your specific Dev install or profile that's leading to it.