Apr 09 2022 08:21 AM
Apr 09 2022 08:21 AM
This Bug affects only Edge Beta 101.0.1210.10 as well as current Edge Dev and Canary.
Current Stable Edge 100.0.1185.36 ist NOT affected and works fine!
All Policies which are documented as "This policy is available only on Windows instances that are joined to a Microsoft Active Directory domain, Windows 10 Pro, or Enterprise instances enrolled for device management." do not work on Edge Beta 101 and above. All other Policies still work as expected, but Policies like HomepageLocation, DefaultSearchProvider, RestoreOnStartUpURLs etc... which need an MDM-Enrolled or AD-Joined Device don't work.
Edge Beta 101 shows on Browser-Start: ErrorThis policy is blocked - its value will be ignored.
When Pressing the "Reload Policies" Button after some seconds AFTER Browser-Start the MDM-Management seems to get detected correct, and after pressing "Reload Policies" those show up correct and work:
But: This problem comes again every Edge Browser start!
The "sensitive" Policies which need MDM-Management show up with Error. After manually reloading them by pressing the button they start working until the next Edge Browser restart.
This Bug is new in Edge Beta 101, on the same devices everything works fine with current stable Edge 100. It is not OS-Related, I tried it on different Windows 10 v21H2 Professional as well as Windows 10 v1909 Education Machines - they behave the same. It is just Edge v101 related.
Apr 12 2022 03:20 AM
Apr 13 2022 09:03 AM
Apr 14 2022 11:28 AM
If you are feeling adventurous, a fix to this issue is out in in April 14's canary channel build 102.0.1226.0 at Download Microsoft Edge Insider Channels.
I'd love any feedback you may have on this to be sure it fixes your issue or if there are any other problems this change causes. I'll will continue to work to get this into the beta channel.
Apr 15 2022 08:49 AM - edited Apr 15 2022 08:49 AM
Thank you @mkruger ... just checked, new Canary Version looks good - is fixed for me! Hope to see this in Dev and Beta soon.
Edge Stabe 100.0.1185.39 ... OK - not affected
Edge Beta 101.0.1210.14 ... ERROR (unchanged, not fixed)
Edge Dev 102.0.1220.1 ... ERROR (unchanged, not fixed)
Edge Canary 102.0.1226.0 ... OK - FIXED!
Apr 18 2022 09:41 PM
Apr 18 2022 11:02 PM
Apr 19 2022 10:44 AM
Apr 20 2022 09:02 AM
Apr 20 2022 09:37 AM
Apr 20 2022 09:51 AM
If either of you are supporting other Chromium based browsers (non-Chrome ones), you will want to check on those browsers as well. I found this issue was a Chromium code base one, but one that did not affect Google Chrome. I have reported the issue in Chromium's bug tracking and will follow up with helping get things fixed there as well, but other Chromium browsers using the policy system may be affected.
Apr 29 2022 01:10 AM - edited Apr 29 2022 01:19 AM
Edge v101.0.1210.32 is now offered as Stable-Release and I can confirm Policies work like expected.
Side-Note: Google Chrome v101 seems to be affected, seems Google didn't fix this in time like Microsoft did.
Link to Google-Chrome Issue: https://bugs.chromium.org/p/chromium/issues/detail?id=1320281
Apr 29 2022 09:45 AM