Forum Discussion

Gunnar-Haslinger's avatar
Gunnar-Haslinger
Iron Contributor
Aug 12, 2022
Solved

Bug: Edge 104 on FirstRun: This policy is blocked - its value will be ignored.

With current Edge 104 (Win10 x64, Edge Version 104.0.1293.54) I realize there is a new Issue on FirstRun regarding the "sensitive Policies".   What do I mean with "FirstRun"? It affects both types...
  • Gunnar-Haslinger's avatar
    Gunnar-Haslinger
    Oct 04, 2022
    Today Edge 106.0.1370.34 released as stable and I can confirm this Issue is solved.
Gunnar-Haslinger's avatar
Gunnar-Haslinger
Iron Contributor
Aug 12, 2022

I found out what Edge is looking for to identify the Situation of a "FirstRun of Version 104.0.1293.54" (user already has an Edge UserProfile, but EdgeUpdate updated to this new Version and its the first run of this new version):

 

JSON-Settings in this File:

 %USERPROFILE%\AppData\Local\Microsoft\Edge\User Data\Local State

 

The affected User-Profiles before Updating have this settings configured:

"management":{"platform":{"azure_active_directory":0}}

 

And after FirstRun of Edge 104.0.1293.54 this ist changed to:

"management":{"platform":{"azure_active_directory":0,"enterprise_mdm_win":4}}

 

A workaround to avoid this bug when Updating Edge and the UserProfiles already exist is, to patch the "Local State" File and add "enterprise_mdm_win":4

 

But for New-Userprofiles I still have no workaround despite exiting Edge and starting it again.

 

mkruger's avatar
mkruger
Icon for Microsoft rankMicrosoft
Aug 12, 2022
Thanks Gunnar for this report and the details. The details are very helpful and we will look into this.
  • Gunnar-Haslinger's avatar
    Gunnar-Haslinger
    Iron Contributor
    Aug 17, 2022

    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.

    • mkruger's avatar
      mkruger
      Icon for Microsoft rankMicrosoft
      Aug 24, 2022

      Gunnar-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.

      • Gunnar-Haslinger's avatar
        Gunnar-Haslinger
        Iron Contributor
        Sep 02, 2022
        Checked the recently released new Stable 105.0.1343.25 today, Problem on FirstRun is still there.

Resources