Jan 08 2020 10:39 AM
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!)
We also have a couple of informational updates. First, we’ve proposed our security baseline configuration for when organizations install the Stable channel of Edge: https://blogs.windows.com/msedgedev/2019/12/18/security-baseline-draft-edge-79/. There’s an accompanying discussion over on the Security Baselines forum. Second, we started a discussion around the value proposition of Reading List and how users would like to see us evolve it moving forward: https://techcommunity.microsoft.com/t5/discussions/reading-list-discussion/m-p/1070553. As for the most noteworthy product changes:
Added features:
Improved reliability:
Changed behavior:
Known issues:
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!
Jan 09 2020 07:04 AM
Jan 09 2020 07:09 AM
Jan 09 2020 07:13 AM
You mentioned that Favorites Sync has been enabled for all Canary and Dev builds, as of a few days ago. I have the Dev version installed on two PC's, yet the Favorites Sync is still disabled and grayed out on both of them.
I've tried removing my profile, and signing back in on both systems. It takes a while for all the [currently] available options to enable again, but the favorites sync remains disabled and grayed out.
Do I need to reinstall? Or is it something that will eventually become enabled on it's own?
Jan 09 2020 07:14 AM
@David Hurst This new version runs flawlessly on my 3x Win 10 1909 64-bit machines. Do you perhaps have any custom Administrator settings in place in Windows?
Jan 09 2020 07:21 AM
@davequail No custom settings. I have 15 users testing and all have same issue. Any page we try to open eventually fails with message "This page is having a problem" and error code STATUS_ACCESS_VIOLATION. I saw a few others in this post mention same issue. I am seeing this on Win 10 ver 1903 and 1909. It only happens after it updates to this newest version. We can install Beta version (79.0.309.60) and it works.
Jan 09 2020 07:29 AM
@David Hurst Does the Status Access Violation bluescreen the PC's or does it happen only in Edge Dev 81? Is there any error code after Status Access Violation?
Jan 09 2020 07:32 AM
Jan 09 2020 07:42 AM
I see the same thing with the DEV build where Favourites sync is off and grayed out. I have even uninstalled with removing all data then reinstalled to fix it, but it remains the same.
Is there a trick to turn this ON? It is on in Canary and Beta just fine on my system.
Jan 09 2020 07:47 AM - edited Jan 09 2020 07:50 AM
I'm also receiving STATUS_ACCESS_VIOLATION. From Event Viewer, I see the following:
Faulting application name: msedge.exe, version: 81.0.381.0, time stamp: 0x5e0eac60
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000000001d7fe2
Faulting process id: 0x4630
Faulting application start time: 0x01d5c702a60d0ed2
Faulting application path: C:\Program Files (x86)\Microsoft\Edge Dev\Application\msedge.exe
Faulting module path: unknown
Report Id: 001aab9f-8642-4513-a4da-d6e0fcdc29bc
Faulting package full name:
Faulting package-relative application ID:
Jan 09 2020 07:51 AM
@Chris Childerhose wrote:
I see the same thing with the DEV build where Favourites sync is off and grayed out. I have even uninstalled with removing all data then reinstalled to fix it, but it remains the same.
Is there a trick to turn this ON? It is on in Canary and Beta just fine on my system.
Trick? yes, use a VPN from another country like US as it's common in Microsoft products to enable new features in the US first.
I've tried this trick many times and it works. though you need to restart your browser once or twice for it to take effect. if it still doesn't, clear cookies and site data from here: edge://settings/clearBrowserData
also please have a look at this topic:
Jan 09 2020 07:52 AM
@TanvirArjel wrote:
Okay fine! But it really looks ugly to me. Then there should be an option to enable or disable it. This would be a perfect implementation.
Yes an option to turn it off/on would be great 🙂
Jan 09 2020 07:52 AM
@davequailI only see this in Edge Dev 81. No blue screen. Not other error code
Jan 09 2020 07:58 AM
@C-los wrote:I'm also receiving STATUS_ACCESS_VIOLATION. From Event Viewer, I see the following:
Faulting application name: msedge.exe, version: 81.0.381.0, time stamp: 0x5e0eac60
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000000001d7fe2
Faulting process id: 0x4630
Faulting application start time: 0x01d5c702a60d0ed2
Faulting application path: C:\Program Files (x86)\Microsoft\Edge Dev\Application\msedge.exe
Faulting module path: unknown
Report Id: 001aab9f-8642-4513-a4da-d6e0fcdc29bc
Faulting package full name:
Faulting package-relative application ID:
Hi@C-los
It could be related to DEP, not 100% sure
You can try turning it off to see if it changes anything
https://www.minitool.com/data-recovery/dep-data-execution-prevention-windows-10.html
Jan 09 2020 08:41 AM
@David Hurst There was a bug a few months back with this same error "This Page is having a problem". I and many others had it through a couple of Canary and Dev updates. It was eventually a bug fix that sorted it out. Not sure yet if it is related. I tried for 30 minutes or so just now to reproduce it using the same sequences I used last year, but so far this Dev is solid.
Jan 09 2020 09:01 AM
@HotCakeX I tried turning off DEP following the instructions in the links you provided. It did not fix the issues I am seeing. Thanks for the response and information,
Jan 09 2020 09:04 AM
@davequail Thanks for the information. I have tried several other suggested things to fix issue without success. It must be some setting(s) in our environment since all of our testers are having this issue. I guess we will wait for the next Dev update or switch to Beta until then.
Jan 09 2020 09:09 AM - edited Jan 09 2020 09:09 AM
A few updates ago a decent number of pages have started to get this privacy error screen. i think some people had mentioned it in recent update posts. not sure if there was a fix for this but i don't think there was. When i hit advanced i can get into most of them but some of them don't work and won't give me the option to get to the site.
on current build 81.0.381.0
Jan 09 2020 09:33 AM
@davequail I hit this same bug at least 1-2 times a week. I can most often replicate it on imgur.com: the tab will just suddenly die with "This page is having a problem." Not sure why (maybe the page bloat).
I report it each build with the Smiley, but it keeps happening...hopefully, the Edge launch isn't mired with lots of headlines "off to a rocky start", "Why have a buggier version of Chrome?", and, "4th time's not the charm".
//
Also, my right-click menu shows a capital "S" under "Search"