Forum Discussion
Solved
Edge Stable 103.0.1264.37 breaks group policy management of the browser - Critical
Going from version 102.0.1245.44 (June 16) to 103.0.1264.37 (June 23), we started experiencing the following issue. Our AD Domain Joined machines running Edge and being managed via Group Policy, ...
- AlexandrosAP Its a issue within Chromium its self. https://bugs.chromium.org/p/chromium/issues/detail?id=1338586&q=extensions&can=2
Looks like Chrome was updated today, so just need to wait for MS to do the same with Edge
The issue is caused by the changes on Microsoft Edge version 103.0.1264.37. Prior to that there was no race condition issue and the machines are the same.
Is there a fix on the way or should we find an alternate solution?
Is there a fix on the way or should we find an alternate solution?
I can confirm the same issue with this build and group policies, specifically extentions defined in the policy that are no longer working. A rollback to the 102 stable version has been the workaround for us until fixed. I have created a case with microsoft and am awaiting their solution. Still no word yet!
- Only extensions configured by ExtensionInstallForcelist policy are affected or also those by ExtensionInstallAllowlist policy ?
- I'm afraid we only have ExtensionInstallForcelist policies so don't know about the Allow policy.
Allowed extensions definitely are for us DanielJasiak
