+Julian

Assuming that the force-install extension mechanism works fine (guess), could the differences between machines described above be due to group policy refresh behavior?

Does chrome attempt to re-read / get notified about group policy changes on Windows?
(I have no idea how GPO propagates to windows machines and if yes, if a running chrome is supposed to react immediately to GPO changes)

Thanks.

Chrome monitors GPO changes and reacts to them immediately in the usual case. This includes installing/removing force-installed extensions when the policy changes. It could be that something (OS config, thrid-party software) prevents Chrome from seeing the policy change or reacting to it or that the system is not getting the policy change.

Two follow up questions here:

1. How do you set your policy - through AD and propagating to clients or locally on the machine. If the second do you use the GPO editor or directly manipulate the registry?

2. Can you browse to chrome://policy when you believe chrome should have received the new policy but the extension is not yet installed. Do you see your new extension listed there? If not what is the last update timestamp listed. Lastly if you hit the refresh policy button on that page does this trigger the installation?

1. I set the policy through group policy editor locally on the machine .
2. Chrome receives the extension policy and listing under chrome://policy. Even after hitting the refresh button also extension remains Uninstalled. Extension is getting installed only when I restart the chrome. 

Thank you for providing more feedback. Adding requester "ranjitkan@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Please try running chrome from the command line with the following arguments 
--enable-logging and -v=2 and then reproduce the failure scenario. You will eventually find a log file called "chrome_debug.log" in the User Data directory in <profile>\AppData\Local\Google\Chrome. Please upload this file to the bug. I hope it will contain some information about what is going on with this instance.

Also, are you able to tell if the undesired behavior happens consistently on the same machines (while it consistently works on others), or if it sometimes works and sometimes doesn't work on all machines?
Thanks.

@ vijaymoorthi95-- Could you please respond to comment #7 & #8 and update the thread.

Thanks!

Closing issue as WontFix due to lack of feedback requested but not provided. If the issue still exists please open a new issue with the details requested.

Thanks..!