"Some extensions are not allowed" after last update

[lexcyn]

Hi all - after the latest version of the Edge stable channel update, multiple users in our org are reporting seeing an erroneous message saying "Some extensions are not allowed", even though the extensions are forced installed through policy and are on our "allow list".  Clicking on the "OK" button dismisses the message and the extensions continue to work as normal.

We're not sure what's causing this - the only policy I can think of is "BrowserLegacyExtensionPointsBlockingEnabled" which we have as "enabled".

Is anyone else seeing this or can point to another policy that may be causing this issue? The only thing I can think of is possibly the latest update caused a policy refresh inside Edge, but that still doesn't explain this erroneous message showing allowed extensions as being blocked.

[#2]

@lexcyn Hello!  Can you share what version of MS Edge this issue started?  Also, if there is no private information can you share a screenshot of the policy page (edge://policy/)?  Thanks! 

-Kelly

[#3]

@Kelly_Y sure - it seemed to have started with version 103.0.1264.37 and here is a screencap of our policy page with some personal details filtered out:

[#4]

@Kelly_Y reporting the same issue.  Users started to get the same message today after the latest update to the Stable channel:

Microsoft Edge
Version 103.0.1264.37 (Official build) (64-bit)

[#5]

@StuartJohnson25 @lexcyn Thanks!  I've reached out to the team about the issue and will follow up once we have more information.  

-Kelly

[#6 · Accepted solution]

@lexcyn @StuartJohnson25 Hi!  Quick update, the issue was inherited upstream from Chromium.  (More information here if you want details : 1338586 - Force-Installed Extensions (via Group Policy) are Re-installed on each Gpupdate - chromium)

We have a fix and it should be going out in the next release of each channel.  Please keep us updated if you are experiencing problems after updating.  Thanks! 

-Kelly

[#7]

Awesome, thank you!

[#8]

Thank you for this. We also had some users in the enterprise report these issues all of a sudden. We thought it was a misconfigured policy. Glad to see we are not crazy. By when is the next release expected?

-We are also using Edge Version 103.0.1264.37 (x64)

[#9]

@CG1980 @Kelly_Y yes that would be good to know the timeline - Google released their update this week which patched the issue already. This is impacting a lot of our users who rely on being signed into an extension for help desk support, and this bug is causing them to be repeatedly signed out.

[#10]

@lexcyn @CG1980 Hello!  The fix should be included in our next Stable release which is planned for this week.  If there are any unexpected delays, we can update this thread.  Thanks!

-Kelly

[#11]

@Kelly_Y thank you, appreciate it!

[#12]

@lexcyn @CG1980 @StuartJohnson25 MS Edge v103.0.1264.44 has released to Stable Channel and contains the fix.  Thanks! 

-Kelly

[#13]

@Kelly_Y We are on version.49 and we are still getting extension blocked errors. This is only happening on Edge.

[#14]

@mmyers1414 Hello - I was not able to find other reports of the issue still reproducing after updating.  

If you are on MS Edge Stable version 103.0.1264.49 and are still affected, have you reached out to Support?  Support - Microsoft Edge Developer  They should be able to gather logs and help investigate your specific case.  Thanks! 

-Kelly