I use Chrome across 4 different workstations and I have my extensions synced across all of them.
The problem I have is that one of the extensions (Gestures for Chrome) works great if you've got an actual mouse, but on a trackpad on Ubuntu, it just gets in the way.
If I disable it on the Ubuntu machine, it gets disabled on all Chrome installations due to its internal sync mechanism.
Q: Can I selectively disable an extension on just a single machine?
May be this is not what you are looking for but you can try this. Open the settings menu within Chrome by clicking on tri-line/wrench icon on right corner. Now open the Advanced sync settings..
Now select the option choose what to sync and then unmark the Extensions option. Now your extension will not sync with other PC's.
You could install the extension you want as a Local extension.
Find the ID of the Extension you want from chrome://extensions with developer mode enabled.
Navigate to your Google installation directory. Windows: %localappdata%\Google\Chrome\User Data\Default\Extensions\{Extension_ID}\{Version_Number}
Save it somewhere.. User Directory maybe?
Return to chrome://extensions with developer mode enabled and press Load unpacked extension. And navigate to the new copy of the extension.
You should see you have the extension twice now.. Disable the real one.
I say Disable because there is a bad side to this approach and that is you lose automatic updates and you will need to repeat the above steps over and over again every time it updates.
If you are not sure which is the real and your new copy, look under the ID tag for Loaded from: {Path_To_Your_Copy}
Based on the security concern, Chrome doesn't sync any extension which contains an NPAPI plugin.
Code running in an NPAPI plugin has the full permissions of the current user and is not sandboxed or shielded from malicious input by Google Chrome in any way. You should be especially cautious when processing input from untrusted sources, such as when working with content scripts or XMLHttpRequest.
If we modify your extension in a way that Chrome recognize the extension using NPAPI, you should be fine.
First, you need a dummy .dll from any NPAPI extension like Screen Capture (by Google). The extension was removed from Google Play store in the meantime because Google decided to drop NPAPI support. But this doesn't matter for our scenario. Fortunately the official Screen Capture wiki still contains the source code. We don't need the complete extension, only the NPAPI .dll screen_capture.dll. Download it directly
Second, go to the extensions folder that should not be synced. In your case Gestures for Chrome.
..\profile\Default\Extensions\jpkfjicglakibpenojifdiepckckakgk\1.12.1_0
Modify the manifest.json file and add the NPAPI plugin as described on Stackoverflow or even better on developer.chrome.com
{
"name": "My extension",
...
"plugins": [
{ "path": "screen_capture.dll" }
],
...
}
Modify the background.html file of your extension you don't want to sync, also described on the Stackoverflow answer above.
<embed type="application/x-my-extension" id="pluginId">
<script>
var plugin = document.getElementById("pluginId");
var result = plugin.myPluginMethod(); // call a method in your plugin
console.log("my plugin returned: " + result);
</script>
It may be necessary to re-enable NPAPI support in the future via chrome://flags/#enable-npapi
From here you are on your own. I don't know enough about extension coding.
Thats why it's a theory :)
Another solution I've found is to use the policy mechanism included in Chrome. Google gives the possibility to manage extensions through group policies. By putting the unwanted extension on the blocklist we have effectively removed the sync for this PC. We can exploit this knowledge by setting these options manually.
Here is a short description for Windows PCs:
For a Linux OS:
/etc/opt/chrome/policies/managed/policies.json if it does not exist/etc/opt/chrome/policies/managed/policies.json with your preferred text editor{"ExtensionSettings": { "PUT EXTENSION ID HERE": { "installation_mode": "blocked" } }By doing this the extension will be removed the next time you start your Chrome. This only affects the PC you are on. I checked this by having a clean install of Chrome. After logging in all extensions were loaded - especially the one we put on the blocklist on the other PC.
The documentation for this Policy setting can be found here, also showing the settings for different operating systems:
https://chromeenterprise.google/policies/?policy=ExtensionInstallBlocklist
Edit 1: Added description for Linux (thanks to sherbang in the comments)
Edit 2: As indicated by Matt Scully the updated URL to the documentation: https://chromeenterprise.google/policies/?policy=ExtensionInstallBlocklist
Edit 3: ExtensionInstallBlacklist has been used here before. It has been discontinued after Chrome version 100. Use ExtensionInstallBlocklist instead. All occurences of the old value have been changed
One thing that works for me is manually killing off the process for the plugin each time Chrome starts using the Chrome Task Manager. This can be achieved as follows:
Then simply click on the extension that you don't want running and click "End Process".
At work I have two computers and I don't want google hangouts popping up on both. The only bad thing is you have to do this every time you start up chrome.
Here is a simple solution (considering you have 19 extensions and only have a problem with one or two): after first install in each individual computer:
This basically keeps all the extensions in your user and you can manually edit them for each individual computer.
Although I have to admit the previous answers were more interesting, this resolves your problem without much tech-savvyness.
Cheers!
This is not to be a resolute answer, but another prospective to examine the problem.
The Chrome sync system does not allow in any way, customizing the ratings by a single machine; And any solution with extra extensions that operates with the flag of disable/enable in your extention, will be fail!
Because another machine that is simultaneously using the same user account, will reflect the change.
A way to avoid this exchange of information is how well he proposed @avirk is disable the sync on extensions, but it seems that this solution is not appropriate for your environment.
Then I will propose two more ideas that can be adopted to obtain the required result:
The other proposal is a little less conventional and could be considered a bad hack, but I will describe it in every way, so that you have a wider choice.
.config/google-chrome/Default/Extensions/jpkfjicglakibpenojifdiepckckakgk/versionfolder
and clears the contents into the file "background_page.html" This generates an exception when loading a page, that will not allow to the event code in your extension run correctly. So we will have the local disablement for this extension.
Remember that any time you receive a new update for your extension,you must redo this operation in the new version folder.
This is an rather old question, but still something that have been bugging me. So here is my own two cents.
You might be able to use an another extension to do this. I myself have been switching between these two plugins: "Extensions Manager (aka Switcher)"
Handy extensions, applications & themes manager. Light popup manager to enable, disable, uninstall extensions, applications quickly and easy.
or "SimpleExtManager"
A simple menu to enable, disable and access options of extensions. Another addition to the 'Simple' series. This time its an extension manager.
Features include:
- basic function to enable/disable, access options and uninstall extensions via popup
- customize the popup
- ability to create extension groups
- enable/disable extension groups via popup and right-click menu
- event page enabled
I like both of the extensions, but haven't gotten to a point where I can say which one I like the most. Both of them are going through a lot of development and are updated frequently.
I was going to comment on Harry_Pootha's excellent answer that helped me a lot, but I am not very active here :)
So, there's an alternative approach that doesn't rely on navigating the registries through Regedit.
At https://support.google.com/chrome/a/answer/187202?hl=en, they offer a step by step guide on how to apply a large range of admin policies to Chrome, including the blacklist policy
To see the entire list of Chrome policies, see the common/ folder in the policy templates zip file (available in all supported languages).
The 2 most important steps, for Windows:
Step1: Download Chrome policy templates
The Windows templates, as well as common policy documentation for all operating systems, can be found here:
Zip file of Google Chrome templates and documentation.
Step 2: Open the ADM or ADMX template you downloaded
- Navigate to Start > Run: gpedit.msc. (Or run gpedit.msc in your terminal)
- Navigate to Local Computer Policy > Computer Configuration > Administrative Templates.
- Right-click Administrative Templates, and select Add/Remove Templates.
- Add the chrome.adm template via the dialog.
- Once complete, a Google / Google Chrome folder will appear under Administrative Templates if it's not already there. If you added the ADM template on Windows 7 or 10, it will appear under Classic Administrative Templates / Google / Google Chrome.
For Linux and Mac there are additional guides linked on Google's page, so it's best to follow through there.
The last step is to actually enable a policy and specify its contents. The best way to do it that I found is to go to chrome://policy/ in a new tab and tick "Show policies with no value set"; this will show all available policies that can be set using the Group Policy editor and each of them link to its documentation.
Note that, in the GP editor, the policy you're looking for uses the long name found in said documentation. Thus, set "Configure extension installation blacklist" to Enabled, click Show in the policy setting GUI and add there the desired ids.
You can easily find extension ids by going to chrome://extensions/ and ticking 'Developer mode' in the top right corner.
Thanks again to Harry_Pootha for his answer that helped me find all this and use it.
It seems that a long time ago it was possible trough extensions but now it seems an options in the settings (Manage what you sync etc.).
Well probably an handy extension that list the installed extensions (https://github.com/rbrahul/chrome-extension-manager not working anymore, indeed) and allows you to pick the one that you want to disable and keep that list on the browser storage would work. Yes it will disable globally but in another location the same extension will use a different list so enabling different extensions.
Well if you're using chrome at the same time on different machine (let's say on your desk you have a mac, a laptop, a desktop maybe with some virtual machine running) it could be a mess...
Maybe instead of disabling killing the processes but I'm not sure it is even possible to do programmatically.
To build on a few other answers from folks (e.g. Harry_Pootha & tiby):
The best way to do this is to use the built-in Chrome policy functionality.
To block an extension, you will need to know the extension ID. You can get this from the Google extensions download page (e.g. PopCart's ID is -- jdfepmcbhnhfamkbpgkedjleahidcbdd)
On macOS you can easily block one or more extensions locally by using the following command(s).
defaults read com.google.Chrome ExtensionInstallBlocklist
defaults write com.google.Chrome ExtensionInstallBlocklist -array jdfepmcbhnhfamkbpgkedjleahidcbdd ${another_extension} ${and_another_one} ...
If you restart Chrome after this and navigate to chrome://policy/ you should see that the extensions is blocked. It will not be loaded even if installed on the system.
The JSON representation of this as exported by Chrome, ends up looking something like this:
{
"chromePolicies": {
"ExtensionInstallBlocklist": {
"level": "recommended",
"scope": "machine",
"source": "platform",
"value": [ "jdfepmcbhnhfamkbpgkedjleahidcbdd" ]
}
}
}
The location of these policy files varies by OS and some loading precedence. Below are links to the Google pages that describe the extension policy procedure for each OS.
As mentioned above, more general policy details can be found here: https://support.google.com/chrome/a/answer/187202?hl=en
