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
got .37 here, and I can’t replicate the problem. Both mandatory and prefererred settings are working. Including a filter proxy on public-facing PCs. It might be worth mentioning that they are all user-policy settings.
- Eric_Lawrence
Microsoft
This 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.- 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?- Eric_Lawrence
Yes, the fix is checked in and awaiting the next respin/release (103.0.1264.44).
- For us they are all system hive policy settings.
