Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Does anybody know how to re-enable your own extensions after they were disabled by the Chrome v35 update?
(Mostly greasemonkey scripts in my case, thus simple .js files previously drag-n-dropped in to the extension windows. )

When I started up Chrome today I got the warning that some non-ChromeWebStore extensions were disabled.

More info was giving on this link:

Extensions disabled by Chrome

You're seeing this notification because one or more of your Chrome extensions has been turned off to make Chrome safer. The extensions didn't come from the Chrome Web Store or were installed without your permission.

For your protection, you can only use Chrome extensions that you get from the Chrome Web Store.

To see a list of your extensions:

  1. Click the Chrome menu Chrome menu on the browser toolbar.
  2. Select Tools.
  3. Select Extensions.

Extensions that have been disabled are grayed out and you won't be able to re-enable them.

I was hoping I could still enable them by activating developer mode for my extensions but still no luck.. Any tips anyone?

P.s. this is not a duplicate from Activating a Chrome extension that is not from the Chrome Web Store as this is related to the chrome v35 update

share|improve this question

5 Answers 5

up vote 25 down vote accepted

There are really only a couple of options open to you as the ability to run the extensions has been programatically disabled with no plans to re-enable it (or at least none made public)

You can try installing from the canary channel or the developer channel releases which may allow you to still run these extensions as mentioned in Google Chrome help forum:

What if I want to run non-web store extensions?

Advanced users can continue to use our Dev & Canary channels to run any extension. Please note that these channels are updated very regularly, and may contain features and bug fixes that are actively being developed.

Alternatively, I have heard that quite a few people install Tampermonkey which then allows the running of user scripts.

Might be worth a look.

share|improve this answer
4  
Thanks. Tampermonkey was indeed the way to go for my use-case (manually added userscripts). I couldn't just re-enable it with tampermonkey though. I really had to find the .js file in %localappdata%\Google\Chrome\User Data\Default\Extensions and copy-paste the contents –  AardVark71 Jun 11 at 12:00
3  
I got TamperMonkey to work with my script by going to TamperMonkey Settings, and clicking the "New Script" tab (leftmost tab), and pasting the text of the script into the editor there. When I clicked the save button, my extension started working again. Thanks for the help! –  dacoinminster Jun 11 at 23:15
    
Am I the only one who was able to get userscripts to work by packing them into crx files and dragging them into the Extensions page. –  Cybertox Jun 12 at 9:44
    
My extensions were in a "Profile 1" folder, not a "Default" folder. %localappdata%\Google\Chrome\User Data\Profile 1\Extensions –  Matthias Dailey Jun 13 at 17:48
    
@Cybertox I got that to work briefly but periodically when I restart Chrome (usually on reboot) Chrome disables the crx extension again, forcing me to repeat the process. –  stevemidgley Sep 29 at 3:04

You can't re-enable them. You need to workaround this issue using any of these alternatives (I will list them for grade of difficulty):

Developer mode route

  1. Download the crx file and unpack the extension using your favorite decompresser. Take note of the directory where you placed it.
  2. Open the extension page, activate "Developer Mode"
  3. Click "Load unpacked extension..."
  4. Search trough your directory tree for the directory where you unpacked your extension and click OK. If your extension is called "my extension" then select "my extension" directory.

Advantages: You don't have to install anything else. Disadvantages: Chrome nags you to disable the extension each start up.

Moving from release channel

Install the Dev or Canary version of Chrome. Just go to the corresponding link and install the browser. Note that the Canary version will install a parallel version of Chrome which will be independent.

Advantage: No nagging, you get the most newest features earlier. Disadvantages: You also get all the bugs earlier. Installing Canary effectively uses the double disk space than a single installation of Chrome and also you have to migrate all your extensions over.

Install other Chromium-like browser

Since Chromium is opensource, there are several forks of the project. I'm not sure if Chromium has the restriction in place but other project may not.

Moving from Windows altogether

This restriction is put in place only for Windows due security concerns of the entire OS. Mac's and Linux builds are not affected. You could give any Linux distribution a try.

The "Developer mode route" is thanks to capetoide in the AllMangasReader Forum.

share|improve this answer
    
I am a little perplexed, 4 machines running 35.0.1916.153 m (standard non-Dev/Canary) and 2 of the machines do not disable the extensions with developer mode enabled, added by dragging the crx file (& not unpacking first), but the other 2 continue to disable them on re-launch. I have even tried the master_preferences and again only of the two computers does it disable on re-launch. –  Spero.ShiroPetto Jun 15 at 19:07
    
@Spero.ShiroPetto give it time... it will reach you, maybe in 36.0. –  Braiam Jun 15 at 19:22
    
@Braiam: +1 good answer, you should add the option of using Tampermonkey extension to manage all userscripts. –  Amro Jun 16 at 18:59
    
@Amro my answer is oriented to real extensions (those that comes in the .crx way) –  Braiam Jun 16 at 21:45
    
Note that to use the Developer mode installation with current CRX files, you have to delete _metadata (and potentially other folders/files starting with underscores) from the extracted folder –  Aurimas Oct 16 at 18:44

There's another option (at least on Mac) -- there's Google's own Chrome Apps & Extensions Developer Tool (https://chrome.google.com/webstore/detail/chrome-apps-extensions-de/ohmmkhmmmpcnpikjeljgnaoabkaalbgc/details) which allows you to re-enable any extension installed.

share|improve this answer
    
OSX is not affected. Only Windows. –  Braiam Dec 6 at 13:31
  1. Add the --enable-easy-off-store-extension-install flag when you start chrome (create shortcut, edit target, append the flag).
  2. Navigate to chrome://extensions/ in the browser.
  3. Drag 'n drop the .crx to the browser, installing the extension.

You'll need to do it every time you launch the browser.

share|improve this answer
2  
The --enable-easy-off-store-extension-install flag makes no difference on Chrome 36.0. The non-store extension I installed is still disabled. –  E M Aug 22 at 22:55

I used the procedure exactly as described here in a Google forum. permalink

https://productforums.google.com/d/msg/chrome/9NlMAr6uEVc/ambkrcKpi1cJ

It basically involves moving, whitelisting the extension ID into the Group Policy Editor.

share|improve this answer
1  
Doesn't work. After restarting chrome extensions are again disabled (Windows 7 Home Premium 64bit). Apparently this workaround doesn't stick for Windows Home editions. –  DavidPostill Sep 11 at 17:06

protected by Community Oct 16 at 18:48

Thank you for your interest in this question. Because it has attracted low-quality answers, posting an answer now requires 10 reputation on this site.

Would you like to answer one of these unanswered questions instead?

Not the answer you're looking for? Browse other questions tagged or ask your own question.