Or you can change group policy settings to allow the extensions you want to install. Bit more work to set it up, but I think it should update okay... Although I haven't tried that yet. TamperMonkey is probably easier. lol
Found the group policy fix here (page 25 of this thread, copied below so you don't have to search):
https://productforums.google.com/forum/#!topic/chrome/2yTVWdfC4Gg%5B1-25-false%5D
I am surprised Google did this... And they have ticked off a LOT of their users by doing this. Read through that forum and it's pretty obvious how people feel about this "safety update".
BTW, just wanna say... TW-DB ROCKS!!! Keep up the great work guys n' gals!!!
=-=-=-=
Bob Simmons56
12:13 AM (20 hours ago)
Caliban511 had it correct on Tuesday. You can use the Group Policy editor to get your disabled extensions back without crx files and without annoying messages popping up about suspicious extensions. I'm going to copy the instructions he provided and paste in a few more tips that hopefully will make it easier. This is going to be for Windows 7. It might work for other OS's, but I don't have time to verify that right now. You're going to be downloading the Chrome group policy templates that are normally used on a network, but they work just fine on a standalone PC too. You'll be copying two files from that download into the Windows PolicyDefinitions folders so the Chrome policy settings will show up in the Windows group Policy Editor. Changing one of those settings will allow you to re-enable third party extensions.
1) Download Chrome group policy templates here:
-
http://dl.google.com/dl/edgedl/chrome/policy/policy_templates.zip
2) Extract the contents of the zip file to a temporary location of your choosing.
3) The first file you need is
chrome.admx. It's
(in the ZIP file) under windows\admx\en-US. Copy the file to C:\Windows\policydefinitions. You'll know you're in the right place because there's lots of other admx files there. If you use a language other than US English, then alter the subfolders you use accordingly
4) The other file you need is
chrome.adml. It's
(in the ZIP file) under windows\adm\en-US. Copy the file to C:\Windows\policydefinitions\en-US. Again, you'll know you're in the right place because this folder is full of adml files. Again, use different subfolders if you use a different language
5) In Chrome, go to
Settings -> Extensions
6) Check the
Developer Mode checkbox at the top
7) Scroll down the list of extensions and note
(copy to Notepad) the ID's of the extensions you want to enable. LogMeIn, for example, is ID: nmgnihglilniboicepgjclfiageofdfj
8) In Windows, click
Start -> Run, and type
gpedit.msc. This starts the Windows Group Policy Editor, which will now include settings for Google Chrome since you added those two files.
9) In the left pane, expand
User Configuration (the lower section) -> Administrative Templates -> Google -> Google Chrome -> Extensions
10) Double-click to open "
Configure extension installation whitelist". The whitelist is the list of 'known good' extensions that you are approving for use within Chrome. Basically that's your third party approval action
11) Select "
Enabled", then click "
Show..."
12) In the list, enter all the ID's for the extensions you noted in Step 7. The top line is the entry line. The box below shows the current list of all entries, which should be blank to begin with. It may require a few clicks in the top line to get an ID entered. I had to open the window several times before it would let me actually enter the ID on the line.
13) Click OK as needed to complete the process, close the Windows Group Policy Editor and restart Chrome. You should now be able to go back to
Settings -> Extensions and enable the extensions that you entered into the Windows Group Policy Editor.
Good luck.