Google Chrome blockt neuerdings 3rd party extensions - wie überstimmen?

    -If it is an extension you wrote yourself, you can upload it to the webstore and publish it in a "hidden" state so that only people with the link, or people in a set of trusted tester users, can install it.
    -If it is an extension from a 3rd party software company, contact their support to point them at our blog post and ask them if they can migrate their extension to the webstore.
    -We are only enforcing this policy on Windows beta/stable channels, since that is where the problems are. More advanced users may wish to try out the chrome developer or canary channels (the canary can be installed side-by-side with other channels of chrome). Also I should note that we aren't enforcing this policy for chrome apps or themes, nor are we enforcing it for extensions on MacOS, Linux, or ChromeOS because we don't see anywhere near the same level of problems on those OSes (obviously switching OSes is a big deal and I don't mean to suggest that you should consider this, but I just wanted to make sure folks already running those OSes know that the policy doesn't affect them).


Anyway, seems that a workaround is to extract the extension (7zip does this job just fine), enable developer mode in Chrome's Extension page, and load the folder where you extracted the extension.

Of course, this disables extension auto updates, but at least you can use it.