Welcome to the new year! Today we’re releasing build 81.0.381.0 to the Dev Channel, which as you can see is the first new build from major version 81. We haven’t been completely asleep during the holidays though; we’ve been slowing turning favorites sync back on for most Canary and Dev users, with the last of them coming back online a couple of days ago. As sync is re-enabled, some machines may experience duplication-like behavior as the machines get back into a clean state, but that behavior shouldn’t persist, and any changes you make to your favorites should now sync properly (but please let us know if that’s not the case!)
Added a feature to suggest URLs to visit that are similar to typed URLs that result in a failed navigation due to the fact that no webpage at the typed URL exists.
Added a keyboard shortcut for starting Read Aloud (ctrl + shift + U).
Added the ability to paste multiple items into a Collection at the same time.
Added a dialog to tell users when a new data type is available to sync.
Added support for Guided Switch to suggest going back to a personal profile when visiting links to certain non-work or school resources in a work or school profile.
Added support for the Chromium management policy to disable web payment APIs in webpages.
Added a management policy for disabling Microsoft Search for Business.
Improved reliability:
Fixed a crash when syncing favorites.
Fixed an issue where favorites that are synced between multiple machines sometimes get deleted from one machine when they’re edited on another.
Fixed a crash when syncing Collections.
Fixed a crash when sync is enabled.
Fixed a crash when syncing with Edge mobile.
Fixed a crash when clearing browsing data.
Fixed an issue where Collections don’t sync properly.
Fixed a crash when importing certain data from other browsers.
Fixed an issue where Edge fails to install due to a crash in the installer.
Fixed an issue where uninstalling Edge and re-installing the same channel with a lower version number causes Edge to no longer launch.
Fixed an issue where enabling Tracking Prevention prevents some pages from ever loading, regardless of the level Tracking Prevention is set at.
Fixed an issue where certain videos don’t load when Tracking Prevention is enabled.
Fixed an issue where Tracking Prevention prevented users from logging into certain websites.
Fixed an issue where navigation in new tabs sometimes fails, either showing an error that the connection is closed or crashing the tab, but subsequent navigations are sometimes okay.
Fixed an issue where typing in the address bar sometimes causes a crash.
Fixed an issue where Edge is no longer able to launch after uninstalling and reinstalling it.
Fixed a crash for users who have certain anti-virus programs installed.
Fixed an issue where Amazon Music fails to play.
Fixed an issue where sharing a local file (for example, a PDF that’s been downloaded onto the machine) fails.
Fixed a crash during shutdown.
Fixed an issue where the policy to enable/disable printing headers and footers doesn’t work.
Improved the reliability of installation.
Changed behavior:
Fixed an issue where downloading files in IE mode tabs sometimes prevents the browser from being closed even after the downloads are completed.
Fixed an issue where the user can’t remove pages from the list of pages to open when the browser first starts.
Fixed an issue where removing a search provider in Settings sometimes results in the inability to add that same search provider again.
Fixed an issue where the second page of the print preview dialog doesn’t render properly.
Fixed an issue where unselecting categories to be synced during the First Run Experience sometimes results in those data types still being synced.
Fixed an issue where the Office New Tab Page is broken.
Fixed an issue where creating a new Collection sometimes fails.
Fixed an issue where some images can’t be dragged and dropped into a Collection.
Fixed an issue where using Collections sometimes causes error reporting dialogs to appear.
Fixed an issue where certain suggested sites in the Pinning Wizard don’t get pinned to the taskbar.
Fixed an issue where the toggle to sync open tabs isn’t functional.
Fixed an issue where login details appear as autocomplete candidates for text fields that aren’t used for logging in.
Fixed an issue where signing into the browser sometimes fails to properly set the profile picture.
Fixed an issue on Mac where websites installed as apps don’t open and instead show an error if Edge isn’t already running.
Fixed an issue on Mac where the update page spins forever or eventually shows an error after a successful update.
Improved how much content is blocked by SmartScreen’s dangerous content blocker.
Fixed an issue where highlighting text in the address bar then clicking on webpages sometimes causes black-on-dark text when the browser is in Dark Theme.
Fixed some graphical flickering when switching between IE mode tabs and non-IE mode tabs.
Fixed a white flash when entering Reading View.
Improved the PDF reader’s background area color in Dark Theme.
Fixed an issue where Application Guard windows sometimes don’t use the proper theme.
Improved performance when opening Application Guard windows for the first time.
Changed the name of the window that appears when you hover over a running instance of Edge on the Task Bar to only be the name of the active tab in that window instead of also containing the name of the profile and browser.
Changed the behavior of “deprecated” management policies to still apply properly, which differs from Chrome’s definition of “not supported” policies. Both “not supported” in Chrome and “obsolete” in Edge are policies which are no longer supported and just show an error instead of being applied.
Known issues:
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.
Some users are still not seeing Collections being enabled by default on Canary and Dev. For users who want to try Collections, enabling the flag at edge://flags/#edge-collections should still work to turn on the feature.
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’re looking forward to the release of the Stable channel soon, and thank you for all the help you’ve given us in getting to that point!
Hi Dave. I tried the non-safe mode process you advised for @samuele2 and this made no difference. I confirmed Edge had no processes running, renamed the profile, ran Edge again and then nothing happened except for multiple processes starting in Task Manager. After a few minutes, I ended the processes and ran Edge again. This time it displayed the UI with an Edge closed unexpectedly dialog, still had white browser pages with "This page is having a problem". We can't even get into the Help -> about or Settings pages.
@davequail No, thank you for the suggestion :) The sooner we can get this sorted/worked around, the better for us :) Hopefully the full release will drop soon and we'll be switching to that.
Michael, I'm sure there are a few of us hoping / expecting that some issues won't be seen when and once it's the or an actual, true, non-beta browser. And, fully in step with the OS.
@Drew1903 wrote: Just pointing out that the behavior is not hitting everyone. That, too, is good info for the Team.
To be honest, I don't see how it's useful/helpful to say you don't have a problem.
in this thread alone, you've said more than 3 times that you don't have a bug or problem, right after someone says they have a problem or bug.
it feels like when we say we are experiencing a problem. we are lying.
imagine if everyone came here and said they don't have problem.
so like:
"person1: I don't have problem.
person2: I don't have problem.
person 3: I don't have problem.
.
.
"
soon the thread would be filled with hundreds of posts that are just not doing anything.
the default expected thing is that everyone has no problem and so they work with their browser or software normally, but when there is a problem, it should be mentioned and we all help to fix it.
@Drew1903 wrote: I'm sure there are a few of us hoping / expecting that some issues won't be seen when and once it's the or an actual, true, non-beta browser. And, fully in step with the OS.
Even if some issues remain, it's not the end.
the release of stable channel is just the beginning, any issue can be easily fixed by minor updates. that's how Google does it after releasing each Chrome stable version.
I too am experiencing this STATUS_ACCESS_VIOLATION error. When you roll back, are settings retained including collections?
You can manually backup your collection.
all you have to do is copy this file and keep it in a safe location, then copy it back to the same place once you're done reinstalling your Edge browser.
it's an unencrypted .json file
located in: "\User Data\Default\Collections\collections.json"
to find the location of \User Data\
simply paste this into your browser address bar: edge://version/
