Forum Discussion
Bug: Edge Beta 101 on Start: This policy is blocked - its value will be ignored.
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!
- mkrugerApr 29, 2022
Microsoft
Thanks again for the further testing!
Ouch, I did test try testing out on Chrome at first and did not find a similar issue and thought it may be an Edge specific problem. On testing for Chromium, I found the problem did exist there. I reported the issue Chromium and it looks like they are merging the fix from that in the issue you linked.
My theory at the time was that some of the Cloud Based management code for Google Workplace was performing some initialization that was missed when it was disabled. If that is disabled in some manner in your environment, that may be what is causing this to be seen in Chrome too. Just a guess though, looks like Google will have a fix out soon for you.
For reference, here is the issue I filed:
https://bugs.chromium.org/p/chromium/issues/detail?id=1316052 - Gunnar-HaslingerApr 29, 2022Iron Contributor
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
- mkrugerApr 20, 2022
Microsoft
Thanks Gunnar-Haslinger and Joachim_T for the reports of the issue and help validating the fix. I really appreciate it!
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.
- Gunnar-HaslingerApr 20, 2022Iron Contributor
- mkrugerApr 20, 2022
Microsoft
Edge Dev just updated and should have the fix.
Edge Dev 102.0.1227.0 should be working for you. - josh_bodnerApr 19, 2022Silver ContributorSince Canary is currently fixed, this week's Dev update should also get that fix. Once you update to a newer version of Dev, can you make sure it also has the fix?
- Gunnar-HaslingerApr 19, 2022Iron Contributor
I can confirm Edge Beta 101.0.1210.19 works now.
So right now only Edge Dev 102.0.1220.1 is still affected.