This message was deleted.

Are you injecting registry settings or are you using the policies in "Computer\Google Chrome\Extensions"? I use the policies in IWC and UWM to enable extensions needed for Ivanti browser management in sessions managed by any of these 2 products and that works like a charm. For enabling the Ivanti Browser Management extension in Edge-Chromium, Chrome and Firefox, we have that explained here: https://help.ivanti.com/ap/help/en_US/bm/2021/help/Content/Configure_Browser_Management.htm If you scroll down, almost at the bottom it describes what to do for Google Chrome

@Dennis van Dam, I'm using User Registry Policies (imported Chrome96 ADMX) to write the registry entries, but in the Computer\Software\Policies\Google\Chrome\ExtensioninstallForcelist not down in where the app keys are \Extensions. Taking a look at the article you linked now. Thanks!

it might just be a timing issue, what if you apply that policy at logon and not on the application level? it's just one registry entry, so applying that during logon shouldn't hurt the logon time

I was curious about that as well... our favorite two words, "race condition". Closing re-opening Chrome, while validating reg is in place before launch, yielded the same results.

I saw some strange behavior with those nasty apps that start several subprocesses of the same exe or even close the parent, had that with UWM and teams, moved the action to session in stead of application and that "solved" the issue that I ran into that time

I'll give it a go. I know Chrome can be particular sticky in that manner.

while we are at it, make sure to check if you need to change your User Settings configuration: https://www.avanite.com/blog/chromium-cookies-and-network-data

That's what prompted me putting eyes on it/importing the new Pol templates. In the process Help Desk let me know extension loading has been "inconsistent" for sometime.... I had no idea.

I sent you a DM with a Building Block