Forum Discussion
Edge Stable 103.0.1264.37 breaks group policy management of the browser - Critical
- 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
MicrosoftThis issue is caused by a race condition.
Group Policy update works by
1) Deleting the old policies from the registry
2) Writing the current policies to the registry
3) Chromium reloading new policy data out of the registry
In v103, a regression was introduced by new registry-monitoring code. This code would detect that the keys had changed at [point 1] and the browser's in-process policy would be refreshed before the current policy data had been fully written to the registry by the GP Update. As a consequence, the browser process could end up with a "partial" (or empty) set of policies applied.
The problem's reproducibility will vary depending upon how short the time gap is between old policies being deleted from the registry and new policies being written. The visibility of the problem also varies-- only policies that support Dynamic Refresh are impacted, and many policies do not have side-effects that are immediately user-visible.
The fix is to stop monitoring the registry keys directly.
Is there a fix on the way or should we find an alternate solution?
- Eric_Lawrence
Yes, the fix is checked in and awaiting the next respin/release (103.0.1264.44).
- The issue is solved in the stable version 103.0.1264.44 and newer, but I still have the issue in DEV 105.0.1300.0... Anybody else seeing this?
- Eric_Lawrence
It appears that the rollout has started: https://twitter.com/ericlaw/status/1542593747766083585. I'm afraid I do not myself know the specifics about the rate at which rollout occurs, but the team does understand the importance of getting broad deployment quickly.
- thanks for the info Eric, looking forward to the prompts not appearing on every gpupdate 😉
- 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.
