01-08-2020 10:39 AM
01-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:
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!
01-14-2020 02:53 PM
@Obprg since you provided the Bucket ID in the crash you mentioned, I looked up what the crash was in our database and it looks like quite a few people have been hitting it over the past couple of days. I'll ask our reliability team if they've got a fix in place for it yet.
01-14-2020 03:22 PM
@ikjadoon as you and others have noticed, we've got quite a few issues with the behavior of installing websites and pinning them via the Windows context menu. The installation problem is something we inherited from upstream Chromium, so we'll also get the fix from them. Also as you've noticed, it only affects certain websites.
The pinning behavior is something that I personally experienced recently since I've been setting up a new machine over this past week, so we've already got a bug filed for that. I'm using a Windows Insider build though (19041), so to everybody who's seen the shortcut either not launch Edge correctly or not have the right icon after using the Windows context menu to pin it, which version of Windows are you using? Since it's possible there are multiple causes to these issues, it would be helpful to try to narrow down where it happens as much as we can.
01-14-2020 03:28 PM
@samuele2 Our investigation over the past week helped us figure out that some of the people hitting STATUS_ACCESS_VIOLATION have been running Forcepoint/Websense security software on their systems. By any chance, are you, and does disabling it make any difference?
01-14-2020 07:08 PM - edited 01-15-2020 12:33 AM
I have put this in Spanish for you, intentionally, as a courtesy
Si le pegas a ese problema, haz lo mismo que yo, como tenía que hacer. Es lo que Edge sugiere cuándo o si esto sucede. Desinstale el dev. Ve a tomar una nueva descarga de ella AQUI y reinstala. Instalará la compilación más reciente.
01-14-2020 07:18 PM
"it only affects certain websites", Josh
Josh, it only affects the icon for sites converted to apps. And only when they are pinned... initially, before telling to pin they are correct & morph into Edge icons as soon as pinned. Sites pinned via Pin to taskbar under More tools do not change to generic Edge icons.
Now, to answer your curiosity about behavior on an IB vs 18363. I run both. I have tried & tested all this stuff on both 18363 and 19541. It is identical. And is you writing 19041 a typo?
BTW, I like the Greeting thing, that becomes a basic weather notice, on the NTP.
01-14-2020 09:37 PM
@josh_bodner Thank you for the update. I'm glad the Canary bugs will get the patch from Chromium, as creating the apps has actually worked flawlessly on Dev.
All my machines are on 1909, so all my Dev/Canary tests were conducted on 18363.535.
I've done a quick test now on Dev 81.0.381.0 (this thread's build) and today's Windows 10 patch (18363.592) and the bug can still be produced.
And, yes: the conditions are tricky. Here's one that's mostly reproducible:
If you install a site & you get the correct icon -> pin it immediately -> default icon reset -> uninstall -> reinstall -> no "website-app" is created, just another Edge.exe shortcut. That is, now you have just another shortcut to Edge. It's not the website you installed, it's not the favicon of the website you installed, and no longer is named "Google.com" (example). It even says "Microsoft Edge (2)".
I'll test more soon and see if I can narrow down something 100% reproducible; thank you, @Drew1903 for following up as well. Others here may be better detectives than me, heh.
01-14-2020 11:01 PM
What would be the explanation and reason that I can't reproduce this pinning problem on a fresh Windows 10 installation be? I'm also running Windows 10 insider but fast ring build 19541
here are my reproducing steps on both Canary and Dev channels:
01-14-2020 11:05 PM
01-15-2020 01:07 AM
Yes, I didn't show the .xxx for 18363 as I was just distinguishing it from the Insider Build.
Now, this is interesting. I decided to try the scenario, again.
Canary: Turn a site into an app, pin its icon to the taskbar & it changes to an Edge icon; however, I didn't have MS Edge (2)... the app's name & thumbnail stayed correct.
Dev: One of the same sites tried in Canary DID/DOES keep its icon after pinning. I found a 2nd that holds. However, others do not. So, there you have it, some stay true & proper, some morph into generic Edge icons.
I may not have experimented with multiple sites previously. Just reckoned any or all would do the same as one did... apparently, not.
01-15-2020 03:59 AM
@HotCakeX Only select IT staff can turn it off.
We tried stopping it from the task tray which stops the service intercepting packets/redirecting traffic to the proxy (We use the Endpoint Proxy client) and this didn't fix it.
We then tried stopping the actual service (Websense SaaS Service) which didn't fix it.
The only other option would be to remove the client.
I can only presume there is some back end hook which is breaking Edge as traffic interception isn't the problem.
Hope this helps in some way
01-15-2020 11:27 AM
@HotCakeX @ikjadoon I guess I forgot to actually say why I was interested in knowing if you were seeing any buggy pinning behavior in Windows Insider builds! The issue is with Windows, not Edge, and we made a fix in all Windows Insider builds 19xxx and higher. That fix hasn't had a chance to be ported back to non-Insider Windows yet (18363 and lower), so it's not surprising if people are still seeing it there, but if you're seeing it on Windows versions that do have the fix, then it means the fix wasn't sufficient.
Also Drew, 19041 is the current Insider Slow build, which is due to be released this year. 195zz is the Insider Fast Windows, which is what used to be called Skip Ahead and is what will be released either later this year or next year. Both rings should have the pinning fix.
01-15-2020 02:11 PM