Jan 15 2020 10:39 AM - edited Jan 15 2020 10:42 AM
Hello Insiders, today we’re releasing build 81.0.389.2 to the Dev Channel. It’s a smaller update this week since we’re focusing on our other channels, including our very first Stable channel update: https://blogs.windows.com/msedgedev/2020/01/15/upgrading-new-microsoft-edge-79-chromium/! As part of that, we also announced a fun opportunity coming up later today to talk directly to some members of our development team. For details, see https://techcommunity.microsoft.com/t5/discussions/updated-a-chance-to-talk-directly-with-microsoft-....
Additionally, we’ve started a discussion about the future of the Fluent Design Language and how it’s utilized in Edge: https://techcommunity.microsoft.com/t5/discussions/discussion-updating-our-interface-with-fluent-tou.... As for the most noteworthy features and fixes this week:
Added features:
Improved reliability:
Changed behavior:
Known issues:
For those using the Beta channel, we're also releasing the first update to major version 80 to it this week. Thank you for all your feedback and bug finds that got us there!
Jan 18 2020 01:58 PM
Jan 18 2020 07:16 PM
@Jeffrey Thorpe it seems to be a sort of incompatibility with Forcepoint One Endpoint software. I have the same issue and in fact my organization is using it. Stopping FP services doesn't help, as it didn't help other people having the same issue. However, the problem may be related to QIP.sys driver (which is part of Forcepoint): if you manage to stop it, Edge will eventually work again. In alternative, for me running Edge with parameter "--no-sandbox" fixes it.
Cc: @josh_bodner
Jan 18 2020 08:51 PM
Jan 18 2020 09:18 PM
Best version ever. Really cool and stable
Jan 19 2020 09:32 AM
@samuele2 , thanks for the tip. I added the no sandbox parameter to my shortcut and it Edge Dev is working again. I do get a little warning about the unsupported command line flag but I can live with that until there is a fix for the root cause.
Jan 20 2020 04:24 AM
@DatabaseJase Replying to myself to note that running Edge Dev with parameter "--no-sandbox" fixes this issue too. SEP is most likely the issue because on another PC without SEP this issue doesn't occur.
Jan 20 2020 01:06 PM
I use this extension - https://chrome.google.com/webstore/detail/last-tab/nggjcpipkefkgldicofgmealjndjnhba
Jan 21 2020 01:05 PM
I know about that extension, that's not the point. I'm using 3-5 extensions (trying to have a few as possible) and I'm not going to use one for such a basic feature.
Jan 21 2020 04:24 PM
@josh_bodner What time does the Microsoft edge 80 update for the stable and beta version come out?
I've been waiting all day since they said it came out this week and it's always Tuesdays
Jan 21 2020 06:38 PM
The "Enabled integration of the Windows built-in spellchecker" feature, does not seem to be fully supporting Hardware Keyboard - Autocorrect misspelt words as I type feature from Windows 10?
@Thomaszko I wonder if this is something we also don't support yet for the onscreen keyboard, or is just specific to the hardware keyboard. Either way, could you file in-product feedback about this so we can get it in our bug database just in case it's not already?
Jan 21 2020 06:44 PM
Spoiler3. Why do you keep opening the old Edge after updates to new Win 10 builds, even though EdgeDev is the default browser?
3. Go to Windows settings => Apps => Default Apps and then set the Edge Dev as default browser.
@HotCakeX I think he means the fact that, after you upgrade to a new build of Windows, we auto-launch Edge Legacy. That behavior is hard-wired and has nothing to do with the default browser. We're working on replacing that behavior so that Edge Stable (once it's installed) will be able to auto-launch itself, but since Edge Stable isn't going to be auto-installed on peoples' machines for a while, you'll probably want to just install Edge Stable yourself if you want to stop seeing Edge Legacy.
Jan 21 2020 06:47 PM
@HotCakeX wrote:
@ViniciusFonseca wrote:
Hello guys! Why isn't sign in supported when running Edge as administrator? What's the reasoning behind this limitation? Is there a policy to change this behavior? Thanks!!
Hi,
this is my problem too. Google chrome works and allows sign in when it's run as administrator but Edge has the problem
@HotCakeX I'm curious why you want to run Edge as administrator? Doing so defeats a lot of the security that the sandboxes provide, so it's not a state we want people to be in. (It also caused people whose machines were configured in a certain way to not be able to load any webpages; see https://textslashplain.com/2019/09/27/aw-snap-every-tab-crashes/. That's why we put in the warning when you're running Edge as an administrator!)
Jan 21 2020 06:53 PM
I'm using 3-5 extensions (trying to have a few as possible) and I'm not going to use one for such a basic feature.
@stark I'd like to know more about why this feature that's easy to implement as an extension shouldn't be. Is it just a principled thing, like that the browser should do as much as it can natively? (Which also has counter-arguments that a browser should be as simple as possible.) Or is it because of fears of performance penalties? Personally, I find it very helpful that we now have access to the Chrome extension store since there are lots of features that can be implemented as extensions now instead of having to wait for us to get around to building them in natively.
Jan 21 2020 06:55 PM
What time does the Microsoft edge 80 update for the stable and beta version come out?
@ZeroUserr The update to bring Beta up to version 80 happened last week, so if your Beta isn't at 80 yet, something's probably wrong. It and Stable will never be at the same version, which means that 80 will come to Stable once 81 hits Beta (although they were both technically at 79 together before we officially released Stable since we were just publishing the same bits to Beta and Stable back then in order to test our Stable publishing pipeline).
Jan 21 2020 06:57 PM
Replying to myself to note that running Edge Dev with parameter "--no-sandbox" fixes this issue too. SEP is most likely the issue because on another PC without SEP this issue doesn't occur.
@DatabaseJase just remember to remove that flag once we get it fixed! No update on the fix yet, but I've asked the devs if there's anything we should expect for next week.
Jan 21 2020 08:12 PM - edited Jan 21 2020 08:13 PM
@josh_bodner wrote:
@HotCakeX wrote:
@ViniciusFonseca wrote:Hello guys! Why isn't sign in supported when running Edge as administrator? What's the reasoning behind this limitation? Is there a policy to change this behavior? Thanks!!
Hi,
this is my problem too. Google chrome works and allows sign in when it's run as administrator but Edge has the problem
@HotCakeX I'm curious why you want to run Edge as administrator? Doing so defeats a lot of the security that the sandboxes provide, so it's not a state we want people to be in. (It also caused people whose machines were configured in a certain way to not be able to load any webpages; see https://textslashplain.com/2019/09/27/aw-snap-every-tab-crashes/. That's why we put in the warning when you're running Edge as an administrator!)
Hi thanks for the reply,
well the thing is I don't want to deliberately run Edge as admin, sometimes the situation enforces it.
like when I use Edge on Windows server or in Windows Sandbox.
those are not rare situations at all. in those cases we can't use sign in.
I understand it's a security risk but at least for users that know what they are doing, there needs to be a way to go around it..
the de-elevate on launch flag doesn't help
Jan 22 2020 11:21 AM
Jan 23 2020 04:03 PM
well the thing is I don't want to deliberately run Edge as admin, sometimes the situation enforces it.
like when I use Edge on Windows server or in Windows Sandbox.
@HotCakeX ah, that makes sense, those local admin accounts launch everything as an admin. I'll see if we've got any plans around getting that auto-de-elevate to work in those contexts.