UPDATE: We pushed another update, which now brings the build number to 79.0.309.11. UPDATE: We just pushed an update, which now brings the build number to 79.0.309.7. Hello insiders, today we’re releasing build 79.0.309.5 to the Dev Channel! You may notice that this is only one build away from last week’s Dev, and that’s because this is our candidate for our next Beta release, so we want to make sure it’s extra polished before we release it there. However, that also means it’s a pretty light week this week in terms of notable changes. We do have one known issue right now, where Edge sometimes launches to a blank white window. There are two possible causes. If you launch another window and it’s fine, you shouldn’t ever see the issue again. However, if subsequent windows are also blank, you’ll have to disable Application Guard in order to get Edge back into a working state. We plan on releasing another update later this week in order to get us in sync with Chromium’s Beta, so the fix for that cause should be in the updated build. Fixed a crash when logging into the browser. Fixed an issue where typing in the address bar sometimes causes the browser to crash. Fixed an issue where the browser sometimes crashes after completing the first run experience. Fixed a hang during the first run experience. Fixed an issue where the theme sometimes changes unexpectedly after the first run experience. Fixed some issues with Application Guard windows not successfully opening. Disabled hardware acceleration in Application Guard windows to prevent them from hanging on certain machines. Fixed an issue where certain webpages don’t open in Application Guard windows even though they should. Fixed an issue where files that should be downloaded in Application Guard windows aren’t. Fixed an issue where an extra “Work” browser profile gets automatically created for some users (note that this may not remove the extra profile; a future fix will ensure that). Fixed an issue where the Mac Touch Bar sometimes doesn’t show the proper content. Fixed an issue where the Settings page constantly shows “looking for updates” without ever completing. Fixed an issue where certain settings are changeable even when they’re disabled. Fixed an issue where certain settings that are supposed to be enabled by default are disabled after performing a settings reset. Fixed an issue where the Delete button does not appear next to downloads that have been blocked by SmartScreen. Fixed an issue where the warning not to close the browser because a download is in progress appears even though the user isn’t downloading anything. Fixed an issue where websites that are blocked by SmartScreen aren’t removed from history. Improved scrolling behavior on the new tab page. Fixed some issues with the PDF toolbar’s hiding behavior. Fixed an issue where switching between IE mode tabs and non-IE mode tabs leaves webpages at the wrong zoom level on certain devices. Fixed an issue where no sites open in IE mode tabs when a certain combination of IE mode policies is applied. Fixed an issue where tooltips in Collections all say “collection content” instead of the actual content. Fixed an issue where certain print preview content is hard to read in dark theme. We’ll be back to normal next week, and it’s also Ignite! Will we see any of you there? In the meantime though, thanks to everybody who’s been using Edge and telling us everything you do and don’t like about it.

josh_bodner Unfortunately, multiple desktop support has become worse since last week's dev update. When you open a link from another app inside a virtual desktop where there is no Edge window, instead of opening a new window what happens is that you are thrown into an existing window inside one of the other desktops. I find this a pretty strong regression and think it should be fixed for a beta build. Apart from that, the only issue I have with Edge right now is how the taskbar icon and the start menu icon are strangely "disjoint" - i.e. they are not the same, so the one on the taskbar shows "pin to start" as an option and the one on start shows "pin to taskbar" as option, for some reason. This also means that their jumplists are out of sync. However, from what I can tell this is already an issue with the current beta. Apart from that, I find the new Edge to be a fantastic experience and it's been my default browser since the first dev build. Keep up the great work!

Yes add notes (or Web page inking) is now added in the list of the features being reviewed by the developers. more info:https://techcommunity.microsoft.com/t5/Discussions/Top-feedback-summary-for-October-29/m-p/963887

You're welcome!True that, I think it's more convenient to add a "last updated" date in the Edge about page to help situations like this.

josh_bodner Hi Josh,Reading view is, still, not showing all the photos/images in an article. It will show some from an article, maybe 1 or 2, but, not all that an article, actually, has. Reading view normally will show all the photos an article has.The caret browsing is cool. Having Add notes will be, even, cooler. Just a matter of time, to be sure, since, I, already, know it is coming.Cheers,Drew

Muschkin I think SSO stopped when the extra 'domain' profile was created. The creation has been removed with this build, but the side-effect of not having SSO has not.

josh_bodner

Former Employee

Oct 29, 2019

Dev channel update to 79.0.309.11 is live

UPDATE: We pushed another update, which now brings the build number to 79.0.309.11.

UPDATE: We just pushed an update, which now brings the build number to 79.0.309.7.

Hello insiders, today we’re releasing build 79.0.309.5 to the Dev Channel! You may notice that this is only one build away from last week’s Dev, and that’s because this is our candidate for our next Beta release, so we want to make sure it’s extra polished before we release it there. However, that also means it’s a pretty light week this week in terms of notable changes.

We do have one known issue right now, where Edge sometimes launches to a blank white window. There are two possible causes. If you launch another window and it’s fine, you shouldn’t ever see the issue again. However, if subsequent windows are also blank, you’ll have to disable Application Guard in order to get Edge back into a working state. We plan on releasing another update later this week in order to get us in sync with Chromium’s Beta, so the fix for that cause should be in the updated build.

Fixed a crash when logging into the browser.
Fixed an issue where typing in the address bar sometimes causes the browser to crash.
Fixed an issue where the browser sometimes crashes after completing the first run experience.
Fixed a hang during the first run experience.
Fixed an issue where the theme sometimes changes unexpectedly after the first run experience.
Fixed some issues with Application Guard windows not successfully opening.
Disabled hardware acceleration in Application Guard windows to prevent them from hanging on certain machines.
Fixed an issue where certain webpages don’t open in Application Guard windows even though they should.
Fixed an issue where files that should be downloaded in Application Guard windows aren’t.
Fixed an issue where an extra “Work” browser profile gets automatically created for some users (note that this may not remove the extra profile; a future fix will ensure that).
Fixed an issue where the Mac Touch Bar sometimes doesn’t show the proper content.
Fixed an issue where the Settings page constantly shows “looking for updates” without ever completing.
Fixed an issue where certain settings are changeable even when they’re disabled.
Fixed an issue where certain settings that are supposed to be enabled by default are disabled after performing a settings reset.
Fixed an issue where the Delete button does not appear next to downloads that have been blocked by SmartScreen.
Fixed an issue where the warning not to close the browser because a download is in progress appears even though the user isn’t downloading anything.
Fixed an issue where websites that are blocked by SmartScreen aren’t removed from history.
Improved scrolling behavior on the new tab page.
Fixed some issues with the PDF toolbar’s hiding behavior.
Fixed an issue where switching between IE mode tabs and non-IE mode tabs leaves webpages at the wrong zoom level on certain devices.
Fixed an issue where no sites open in IE mode tabs when a certain combination of IE mode policies is applied.
Fixed an issue where tooltips in Collections all say “collection content” instead of the actual content.
Fixed an issue where certain print preview content is hard to read in dark theme.

We’ll be back to normal next week, and it’s also Ignite! Will we see any of you there? In the meantime though, thanks to everybody who’s been using Edge and telling us everything you do and don’t like about it.

134 Replies

Bahro06
Copper Contributor
Oct 30, 2019
josh_bodner

Hello sir, the new update for Edge Dev doesn't seem to be working properly for windows 8 but the
Edge Beta works perfectly fine. The problem is that Edge Dev won't open for some reason unless I set the compatibility settings to windows vista but I use windows 8 which makes me very confuse and Edge Beta
works properly. How to fix this problem please because I prefer to use Edge Dev over Edge Beta.
Ancgon
Copper Contributor
Oct 30, 2019
josh_bodner when i open the option window by clicking the mouse right button, the [view page source] doesn't show an icon beside it. also the same thing happen when right click on any image the [copy image link] option doesn't have any icon next to it. and in google images [save link as] option doesn't also have any icon. also giving the option to add custom image to new tab would be grate. including those small stuff will make edge look more better I think.
anyway love this browser, already my default sins the first week. waiting for starting sync with android edge so can use it on android more often.
- Drew1903
  Silver Contributor
  Oct 30, 2019
  Ancgon josh_bodner
  
  Actually, there are a few missing (besides View source & Save as) and Dev/Beta & Canary differ a wee bit. Notice there are more in Canary, suggesting that evolution will find its way to Dev, et al in due course.
  
  Dev & Beta
  
  Canary
  
  Cheers,
  Drew
SOI_7
Iron Contributor
Oct 29, 2019
josh_bodner InPrivate icon in the InPrivate window is still rounded instead of square
- HotCakeX
  MVP
  Oct 30, 2019
  SOI_7
  SOI_7 wrote:
  josh_bodner InPrivate icon in the InPrivate window is still rounded instead of square
  Yeah, pretty much everything is square except for that button
- Drew1903
  Silver Contributor
  Oct 29, 2019
  SOI_7
  
  Same as Canary & Beta; at least there's consistency across Channels... just not from day to day
  
  Remember, "Fun with computers"?
  
  Welcome to "Fun with beta Builds"
  
  Cheers,
  Drew
DavidGB
Iron Contributor
Oct 29, 2019
josh_bodner

Just as a note for the next Edge Dev, Edge Canary has been seriously messed up and unusable for me since the first one after last weeks Edge Dev release. In Canary, every version since last Tuesday: (1) right clicking on a page - anywhere on a page - does not produce a context menu; (2) it causes lsass.exe to start running taking 11% cpu continuously; (3) closing it leaves two msedge.exe's still running in Task Manager and lsass.exe STILL taking 11% cpu, and Canary can't be restarted; (4) if I kill the leftover msedge.exes, then lsass.exe goes to normal 0% cpu and I can restart Canary, but with all the same problems every time. No Canary update since this started a week ago has changed anything. This latest Edge Dev does not show these problems, just Canary.

I reported it with Send Feedback, but just thought I'd mention it here.
- HotCakeX
  MVP
  Oct 30, 2019
  DavidGB
  DavidGB wrote:
  josh_bodner
  
  Just as a note for the next Edge Dev, Edge Canary has been seriously messed up and unusable for me since the first one after last weeks Edge Dev release. In Canary, every version since last Tuesday: (1) right clicking on a page - anywhere on a page - does not produce a context menu; (2) it causes lsass.exe to start running taking 11% cpu continuously; (3) closing it leaves two msedge.exe's still running in Task Manager and lsass.exe STILL taking 11% cpu, and Canary can't be restarted; (4) if I kill the leftover msedge.exes, then lsass.exe goes to normal 0% cpu and I can restart Canary, but with all the same problems every time. No Canary update since this started a week ago has changed anything. This latest Edge Dev does not show these problems, just Canary.
  
  I reported it with Send Feedback, but just thought I'd mention it here.
  
  Hi,
  try updating your canary if you still have it installed, a new updated was released for it few hours ago
  
  Version 80.0.317.1 (Official build) canary (64-bit)
- Drew1903
  Silver Contributor
  Oct 29, 2019
  DavidGB
  
  Hi David,
  
  We'll see what Josh may have to say, but... I, certainly, do not have what you describe. Please, fully remove Canary. Next, go grab a fresh DL of it https://www.microsoftedgeinsider.com/en-us/download. then, re-install with the new DL. Please, let us know if this helps, improves or changes anything for you. Thanks.
  
  Cheers,
  Drew
  - HotCakeX
    MVP
    Oct 30, 2019
    Drew1903
    Spoiler
    Drew1903 wrote:
    DavidGB
    
    Hi David,
    
    We'll see what Josh may have to say, but... I, certainly, do not have what you describe. Please, fully remove Canary. Next, go grab a fresh DL of it HERE. then, re-install with the new DL. Please, let us know if this helps, improves or changes anything for you. Thanks.
    
    Cheers,
    Drew
    
    a new update for canary was released, it's no longer needed to uninstall it, specially when users disabled their sync because of the .316 issue, so suggesting that to them could make them lose data. instead better hold on to .316 and update it to 3.17.1
adrianghc
Iron Contributor
Oct 29, 2019
Am I mistaken or is the overlay scrollbar the default now and its flag gone?
- tgienger
  Brass Contributor
  Nov 01, 2019
  My overlay scrollbars are gone and I can't turn them back on...
  - HotCakeX
    MVP
    Nov 01, 2019
    Just a reminder that the scrollbar availability can be down to the designer of the web page or ad.
- Drew1903
  Silver Contributor
  Oct 29, 2019
  adrianghc
  
  Adrian, it does not seem like you are mistaken.
  
  Cheers,
  Drew
  - adrianghc
    Iron Contributor
    Oct 31, 2019
    Drew1903 Actually, it appears that I was mistaken. The flag for the overlay scrollbars was removed from Chromium dev builds v78 and up. The reason the overlay scrollbar appears to be the default for you and I is simply that we had the flag set when we updated to the version where the flag is removed from edge://flags. However, the default behavior seems to be in fact to the old-school scrollbars, not the overlay scrollbars.
sudokai
Brass Contributor
Oct 29, 2019
josh_bodner It's been a few releases, I hope this is a known bug. If I actually open Microsoft AutoUpdate and check for updates from there, it is able to find the newest update and download it.
sudokai
Brass Contributor
Oct 29, 2019
josh_bodner After the update I'm not getting any search suggestions in the address bar, not from Google nor Bing.
Cohas
Copper Contributor
Oct 29, 2019
josh_bodner Love the new edge y'all keep up the good work.
Waaiez
Copper Contributor
Oct 29, 2019
josh_bodner When is the next beta expected to drop?
- HotCakeX
  MVP
  Oct 29, 2019
  I think the next beta update (version 79) will be around November 6th, because the last one (version 78) was released around September 25th and since the update cycle for beta channel is every 6 weeks, I assume that should be the correct date 🙂
  - Waaiez
    Copper Contributor
    Oct 29, 2019
    Ahh thank you. I completely lost track of when updates were pushed because of this 6 week cycle
HotCakeX
MVP
Oct 29, 2019
josh_bodner
I assume the next version will be on Edge80?

Forum Discussion

Dev channel update to 79.0.309.11 is live

134 Replies

Resources