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 10 2020 02:01 AM
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.
Jan 10 2020 02:05 AM
@Michael Gibson Thanks Michael, it was worth a shot. Put it down to experience :smiling_face_with_smiling_eyes:
Jan 10 2020 02:08 AM
@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.
Jan 10 2020 02:19 AM
@Michael Gibson We look forward to next week then. The release is apparently the 15th :)
Jan 10 2020 02:41 AM
Jan 10 2020 02:50 AM
Jan 10 2020 03:00 AM
Jan 10 2020 03:00 AM
@Drew1903 Hi Drew, very true. the Devs really don't have much time left. I can see a lot of VERY late nights between now and then :)
Jan 10 2020 03:00 AM - edited Jan 10 2020 03:01 AM
@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.
Sent from Android mobile
Jan 10 2020 03:03 AM
Jan 10 2020 03:06 AM
Jan 10 2020 03:06 AM
@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.
Sent from Android Mobile
Jan 10 2020 03:10 AM
Fact is, version 79 has been feature locked for more than 1 month, its release would be overdue if compared with Google chrome 79.
the only logical explanation for the extra time they are taking is that they are fixing the remaining issues like the recent sync problems.
I hope the stable channel will be rolled out in waves so if something goes wrong, not everyone will be affected all at the same time.
Sent from Android Mobile
Jan 10 2020 03:18 AM
@Steven Sanders wrote: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/
and look for the "Profile path" parameter.
Jan 10 2020 03:39 AM
@k1ck3rtw I am also seeing Error code: STATUS_ACCESS_VIOLATION, after the upgrade.
Beta version works perfectly.
Jan 10 2020 04:42 AM
Jan 10 2020 04:47 AM
Jan 10 2020 04:48 AM