Forum Discussion
Bug: Edge 104 on FirstRun: This policy is blocked - its value will be ignored.
- Today Edge 106.0.1370.34 released as stable and I can confirm this Issue is solved.
May I kindly ask mkruger if there are any news regarding this issue?
I see this Bug at least on all current Versions of Edge on Win10x64:
- Canary 106.0.1354.0
- Dev 106.0.1349.1
- Beta 105.0.1343.7
- Stable 104.0.1293.54, 104.0.1293.63
Those old Versions are affected too:
- Stable 103.0.1264.77
- Stable 102.0.1245.62
- Stable 102.0.1245.30 (which was the first v102 available)
This old Versions are NOT affected:
- Stable 101.0.1210.53 (which is the last v101 available)
- Stable 101.0.1210.39
=> so we can assume this Bug seems to exist since
- Stable 102.0.1245.30
As I service our Image for internal usage only once in 3 month I didn't notice this Bug appeared in v102 and see it now in v104. The JSON-Setting "enterprise_mdm_win":4" in "Local State" File seems to be a new property in v102, it wasn't there in v101.
MicrosoftGunnar-Haslinger sorry for delays in replying.
With your information, I was able to reproduce the problem and am testing a fix. When successful, I'll work to get it patched to the current releases.
- Checked the recently released new Stable 105.0.1343.25 today, Problem on FirstRun is still there.
- mkrugerThis should be fixed in 106.0.1365.0 and later.
There is a slight performance tradeoff to browser start time with the fix that we are investigating before we can port to 105.mkruger re-tested this on brand new, fresh installed Windows 11 v22H2, result as follows:
- Edge 105.0.1343.42 (Stable) ... Problem still there, so seems to be not backported yet
- Edge 106.0.1370.17 (Beta) ... Is fixed, works now even on FirstRun as expected
- Edge 107.0.1387.2 (Dev) ... Is fixed, works now even on FirstRun as expected
- Checked the recently released new Stable 104.0.1293.70 today, Problem on FirstRun is still there.