Note: I’ve previously blogged about interop issues between Edge18 and Chrome. We expect there will be some behavioral deltas between Edge79+ and its Chrome-peer versions, so I’ll note those here too. When comparing Edge and Chrome behavior, be sure to compare against the corresponding Chrome Stable, Beta, Dev and Canary channels Edge 80 vs Chrome 80, etc. In general, Edge79+ will behave very similarly to Chrome. Compatibility DeltasĪs our new Edge Insider builds roll out to the public, we’re starting to triage reports of compatibility issues where Edge79+ (the new Chromium-based Edge, aka Anaheim) behaves differently than the old Edge (Edge18, aka Spartan, aka Edge Legacy) and/or Google Chrome. If they log off the first machine, edge then starts working on the second one.Note: I expect to update this post over time.

It has been narrowed down to being an issue if the user is logged onto more than one machine, edge will not launch, which i presume it because the first login is locking some files that stops it launching on the second machine. However, reports were revived of edge not launching at times. I have therefore using GPO set the appdata location to the users home directory so that it doesnt pull down/save at each logon/logoff and if have to reset a roaming profile, the favourites will still remain as stored on the network.

If the profile variable is used to store the settings in the appdata oaming then the folder gets too large slowing down logins. Edge chromium ignores the policy setting of sync favourites between IE and EDGE By default the favourites database is stored in the local profile so it doesnt roam Multiple tested resulted in the following: Reports came in that favourites in Edge Chromium were not saving after a logoff.

So we have deployed edge Chromium across the site via MSI and implement the included GPO templates.

Microsoft edge chromium sso not working