Dev channel update to 82.0.425.3 is live


Hello Insiders, today we’re releasing build 82.0.425.3 to the Dev Channel.  As anticipated last week, this is the first build for major version 82.  Because this is the first Dev Channel build in a new version, we don’t have too much new to talk about, although we do have another opportunity for you to talk to us next week.  See for the details! 


Additionally, we made some new blog posts about some of the performance improvements we’ve been working on:, and some of the Mac manageability improvements we’ve been making:  Also, one of our engineers made a detailed post about how the ability to choose a default profile to open links in works:  And as some users have noticed, we’ve begun rolling out Extension sync in Canary, so look for that soon in Dev!  Now, for what’s new: 


Added feature: 


  • Added a management policy to allow the deletion of browsing data from Edge Legacy when it’s replaced by the installation of Edge’s Stable channel. 


Improved reliability: 


  • Fixed an issue where importing favorites from another browser sometimes causes a browser crash. 
  • Fixed an issue where importing settings from other browsers sometimes causes a browser crash. 
  • Fixed an issue where adding an item to a Collection via the context menu sometimes causes a crash. 
  • Fixed a crash when using Collections. 
  • Fixed a browser crash when closing a window for Collections users. 
  • Fixed a crash when closing the browser. 
  • Fixed a crash when closing a window on Mac. 
  • Fixed an issue where printing a PDF sometimes causes a browser crash. 
  • Fixed an issue where attempting to log into a webpage that uses the Windows login dialog sometimes causes a browser crash. 
  • Fixed an issue where deleting form autofill suggestions sometimes crashes the browser. 
  • Fixed an issue where users signed into the browser with a work or school account may see sync stop working. 
  • Fixed an issue where deleted Collections and deleted items in a Collection sometimes reappear when Collections sync is enabled. 
  • Fixed an issue where deleting a Collection sometimes crashes the Collections pane. 
  • Fixed an issue where importing certain data from other browsers like Chrome sometimes fails. 
  • Fixed a memory leak when viewing many Collections. 


Changed behavior: 


  • Fixed an issue where on-premises work or school profiles (profiles with a DOMAIN\NAME format instead of a NAME@COMPANY.COM format) are not removable.  Note that we’ve also got more changes coming to stop creating these types of profiles by default.  See for details. 
  • Fixed an issue where scrolling on a trackpad using the two-finger gesture sometimes causes webpages to jump straight to the top or bottom on certain devices. 
  • Fixed an issue where attempting to install a website as an app or pin it to the taskbar sometimes fails because the UI to finish the action never appears. 
  • Fixed an issue where address bar history is sometimes not properly deleted when the browser is set to delete browsing data on close. 
  • Fixed an issue where enabling Tracking Prevention prevents logging in on certain websites. 
  • Fixed an issue where video that uses Dolby Vision sometimes flashes or stutters. 
  • Fixed an issue where video playing on certain websites like Apple TV sometimes freezes. 
  • Improved performance of playing certain DRM-protected video on ARM64 devices. 
  • Fixed an issue on Mac where extensions that use native messaging don’t work properly. 
  • Fixed an issue on Mac where the Touchbar sometimes isn’t responsive when playing fullscreen video. 
  • Fixed an issue where using IE mode tabs in multiple windows sometimes causes dialogs to appear over the wrong window. 
  • Fixed an issue where the update notification on the … menu fails to appear when there’s a pending Edge update.  
  • Fixed an issue where editing a Collection in one window sometimes doesn’t cause the Collection to be updated in other windows that are open. 
  • Fixed an issue where changing a setting doesn’t update the Settings UI, even though the setting is successfully changed. 
  • Changed the microsoft-edge: protocol evaluation to more closely match Edge Legacy’s behavior of not decoding URLs before navigating to them. 


Known issues: 


  • Some users are seeing favorites get duplicated after we made some fixes in that area last month. The most common way this is triggered is by installing a new channel of Edge or installing Edge on another device and then signing into it with an account that has already signed into Edge before. 
  • Users of certain security software packages will see all tabs fail to load with the error STATUS_ACCESS_VIOLATION. The only supported way to prevent this behavior is to uninstall that software. We’re currently engaging with the developers of that software to try to find a fix. 
  • After an initial fix for it recently, some users are still experiencing Edge windows becoming all black. UI popups like menus are not affected and opening the Browser Task Manager (keyboard shortcut is shift + esc) and killing the GPU process fixes it.  Note that this only appears to affect users with certain hardware.
  • 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. 
  • At certain zoom levels, there is a noticeable line between the browser UI and the web contents.


We plan on updating Beta to major version 81 this week thanks to all your testing and feedback.  We couldn’t have done it without you! 


46 Replies
the flag is still on Canary which is higher version: 82.0.435.0

Show block option in autoplay settings
If enabled, block will appear as an option in media autoplay settings. – Mac, Windows

@HotCakeX sorry, we probably should have been a little more explicit that starting these discussions about all these features in Edge Legacy that we haven't ported over yet wasn't also implying that we were immediately starting to work on them.  We certainly haven't forgotten about it; it's just that sometimes, doing things right takes time, and these discussions are merely one part of our journey to gather user feedback and iterate on a solution.  It doesn't help that downloads is a particularly complex feature with many possibilities for how we could achieve the many things users are asking for.  

Hi HotCakeX,
You are correct about having the block flag enabled, which I do. At least on , it doesn't seem to have much if any effect. By the way, I'd have to agree with what you had stated in one of your replies concerning your default browser. My default is currently firefox beta, especially now since the dns over https has been made available.

Media Autoplay limit or block does not work. When enabled, Youtube still autoplays the video. Serious issue should be added since the old Edge does work well.

@Sundeep Basra 


Does it work in Google Chrome 

"block" option of auto play blocking is hidden behind the flags for a reason and it's because it's still not ready. also media auto blocking isn't so useful alone if it doesn't prevent media preloading.
so for example YouTube video won't start playing for you but it still uses your Internet bandwidth to preload all the contents in the background.
Yes it's still experimental