Disable developer mode extensions pop up in Chrome

Question

Since the latest release of chrome (34.0.1847.116) last week, I have been receiving the “Disable developer mode extensions" when running automated tests using watir-webdriver.

This seems to be the offensive extension but it doesn't make sense to me that this is a potentially hazardous extension given its used by the chromedriver.

Anyone that has found a fix for this, as i am unable to roll back to the previous version or find an installer for an older version to roll back to and this is playing havoc with my tests.

Solution 1

The official way to disable the popup is this:

1. Pack your extension: go to chrome://extensions, check Developer mode and click Pack extension

2. Install the extension by dragging and dropping the .crx file into the chrome://extensions page.

You'll get an "Unsupported extensions disabled" popup if you try restarting Chrome at this point.

Then for Windows 7 or Windows 8:

3. Download Chrome group policy templates here
4. Copy [zip]\windows\admx\chrome.admx to c:\windows\policydefinitions
5. Copy [zip]\windows\admx\[yourlanguage]\chrome.adml to c:\windows\policydefinitions\[yourlanguage]\chrome.adml (not c:\windows\[yourlanguage])
6. In Chrome, go to the Extensions page: chrome://extensions
7. Check Developer Mode
8. Scroll down the list of disabled extensions and note the ID(s) of the extensions you want to enable.
9. Click Start > Run, type gpedit.msc and hit enter.
10. Click User Configuration > Administrative Templates > Google Chrome > Extensions
11. Double click Configure extension installation whitelist policy
12. Select Enabled, and click Show
13. In the list, enter the ID(s) of the extensions you noted in Step 7
14. Click OK and restart Chrome.

That's it!

EDIT: As of July 2018, this approach no longer works: it seems Google has stopped honouring the "whitelist".

EDIT 2: As of December 2018, this approach works in Chrome Version 69.0.3497.100 (Official Build) (64-bit):

1. Temporarily enable Developer mode in chrome://extensions

2. Uninstall the extension that causes the popup using the Load unpacked.

3. Click on Pack extension, and find and select the folder containing the extension files. Don't enter the private key file if you don't have it.

4. Click Pack extension. A .crx and .pem file will be created near the root directory of the extension. Install the extension using the .crx file and keep the .pem file safe.

5. Copy the .crx installed extension ID to the whitelist and restart Chrome.

The popup should be gone.

Solution 2

While creating chrome driver, use option to disable it. Its working without any extensions.

Use following code snippet

ChromeOptions options = new ChromeOptions();
options.addArguments("chrome.switches","--disable-extensions");
System.setProperty("webdriver.chrome.driver",(System.getProperty("user.dir") + "//src//test//resources//chromedriver_new.exe"));
driver = new ChromeDriver(options);

Solution 3

As of May 2015 Chrome beta/dev/canary on Windows (see lines 75-78) always display this warning.

• I've just patched chrome.dll (dev channel, 32-bit) using hiew32 demo version: run it, switch to hex view (Enter key), search for ExtensionDeveloperModeWarning (F7) then press F6 to find the referring code, go to nearby INC EAX line, which is followed by RETN, press F3 to edit, type 90 instead of 40, which will be rendered as NOP (no-op), save (F9).

• Simplified method found by @Gsx, which also works for 64-bit Chrome dev:

  1. run hiew32 demo (in admin mode) and open Chrome.dll
  2. switch to hex view (Enter key)
  3. search for ExtensionDeveloperModeWarning (F7)
  4. press F3 to edit and replace the first letter "E" with any other character
  5. save (F9).

• patch.BAT script

Of course this will last only until the next update so whoever needs it frequently might write an auto-patcher or a launcher that patches the dll in memory.

Solution 4

There is an alternative solution, use Chrome-Developer-Mode-Extension-Warning-Patcher:

1. Download the latest release from here from Github.
2. Close Chrome.
3. Unpack the zip archive and run ChromeDevExtWarningPatcher.exe as administrator.
4. Select your Chrome installation from the just opened GUI and then click on Patch button:

5. Enjoy Chrome without any DevMode pop-up!

Solution 5

Can't be disabled. Quoting: "Sorry, we know it is annoying, but you the malware writers..."

Your only options are: adapt your automated tests to this new behavior, or upload the offending script to Chrome Web Store (which can be done in an "unlisted" fashion).

View more solutions

Comments

[Admin]

Use external clicks to kill the popup: stackoverflow.com/a/29376532/285594

[artdias90]

I suggest stackoverflow.com/questions/30287907/…

[BadAtPHP]

@artdias90 doesn't work anymore, he also doesn't want to update anymore (which is understandable after 2 years of maintaining it).

[Abdullah Nurum]

after the popup shows, press esc button using robot type. Robot robot; try { robot = new Robot(); robot.keyPress(KeyEvent.VK_ENTER); // confirm by pressing Enter in the end robot.keyRelease(KeyEvent.VK_ENTER); } catch (AWTException e) { printStackTraceToString(e); }

[User]

Side note: Vivaldi browser is compatible with most chrome extensions and does not give this warning

[blade]

Another option is to use Chromium, it doesn't have the annoying popups or the "antivirus". There are good builds here or you can make your own build, which is not an easy process.

[Rob W]

You can also use the beta channel. It's more stable than dev. At the same time, it has more features than the stable channel.

[rsanchez]

@RobW asargent said that the popup is present in the beta channel too. Is that wrong? code.google.com/p/chromium/issues/detail?id=337734#c2

[Rob W]

@rsanchez Just tried on Windows, and you're correct. Thanks for the correction. I'm using Linux, so I don't experience this issue (:

[Xan]

This no longer works: blog.chromium.org/2015/05/…

[Xan]

@RobW Could you post an update on the bug? (it's Restrict-AddIssueComment-EditIssue)

[Gsx]

Hi, I am trying to patch it with hiew32demo but I haven't been able to do so. When I open chrome.dll I get Hiew Demo doesn't support NE/LX/LE/NLM/ELF/PE64 files, but I can skip that warning. Then I change the mode with F4 to decode and search ExtensionDeveloperMo since _ExtensionDeveloperModeWarning _ doesn't fit. After it finds it I press F6 but I get Target not found. Could you help me?

[Emerson]

I can't find '4578 7465 6e73 696f 6e44 6576' ('ExtensionDev') in chrome.dll. Does this method still work?

[wOxxOm]

Gsx, my method works for 32-bit Chrome on dev channel.

[wOxxOm]

Emerson, this change has landed in the Dev channel just a week ago, so it's not in Stable. You'll have to find the relevant place by analyzing the previous version of source code.

[Gsx]

Ah, ok. I am on 64-bit dev. I'll try to find another way.

[wOxxOm]

@Gsx, well, if you have a 64-bit disassembler, the procedure shouldn't be too different from the one I described. Example for dev 64-bit 44.0.2398 (not tested but looks plausible): search for hex 33 DB 84 C0 74 07 B8 01 00 00 00, repeat the search to confirm it's the only occurence, replace the last 01 00 00 00 with 00 00 00 00 (basically there was MOV EAX, true which we replace with false)

[Gsx]

@wOxxOm That failed also, but I have found a weird way XD. I searched for ExtensionDeveloperMo and changed that to EXtensionDeveloperMo and that seemed to work.

[nixda]

I switched from Beta to Dev channel (44.0.2403.9), I was able to search and find ExtensionDeveloperModeWa with hiew32 demo (admin mode). I changed Warning to Darling, saved it with F9, rechecked the changes and replaced the original chrome.dll with my modified one. But the warning still occurs. Grml

[wOxxOm]

@nixda, just tried it on 44.0.2403.9, the method is working. Maybe you have some background Chrome-apps running? Check the processes tab in Windows Task Manager.

[Admin]

There are thousands of reason why i cant use my extension/apps in webstore, i need to run it locally. This was a very EVIL implementation from Google Chromium team, very EVIL, someone with knowledge should debat with Chromium and get it fixed. Horrible issue and seriously not appreciated. All the answer to this problem is just over killing for people who is working on kiosks project. its nightmare. please inform / knock/ debat with chromium community to give a fix for this.

[Antony Hatchkins]

I got "Unsupported extensions popup" after using your method. See my answer for details how to disable it as well.

[İbrahim Özbölük]

where should we write this ?

[ghiscoding]

Added it to my Protractor conf.js file args list and that worked. Thanks a lot :)

[Ryan]

Your link points to a discussion in 2014 (which seems like a long time ago as far as software is concerned), and I don't see anything about it coming from Google as "official".

[Antony Hatchkins]

@Ryan The homepage of those policy templates seems to be chromium.org/administrators/policy-templates This site is updated regularly (last update 54 minutes ago). I used this method on Jun 24 and the configuration works with most recent Chrome version today. If you prefer «Can't be disabled» to be the official version - it's your choice ;)

[kriegaex]

The warning message is still displayed whenever I start a Chrome browser via Selenium. I do not have the problem when I start Chrome manually. Any ideas?

[kriegaex]

I found out it is the Chrome Automation Extension, extension ID aapnijgdinlhnhlmodcfapnahmbfebeb. I added it to the white list, but to no avail.

[kriegaex]

I solved the problem via Selenium Chrome Driver options, see here.

[Ryan]

@AntonyHatchkins Thanks!

[kirbycope]

This worked great. In C# the code is: options.AddArgument("--disable-extensions");

[Alessandro Da Rugna]

Works like a charm (C# WebDriver 2.53.1.0, ChromeDriver 2.20.353145, Win7 x64)

[KajMagnus]

Is this Java? It's not Protractor (a Javascript e2e test lib) right? It'd be good if you mention what framework & language you have in mind.

[tube-builder]

@Antony Hatchkins Upvote this because I used this myself and it did help for some time. From Chrome v. 55 however it stopped working..

[Antony Hatchkins]

@tube-builder Thanks! I'm on 55.0.2883.87 m (win7 x64). The message doesn't show up as yet. What are the symptoms on your side?

[tube-builder]

@Antony Hatchkins I used the updated code from this answer stackoverflow.com/questions/30287907/… and it started working again. thanks for reacting!

[Antony Hatchkins]

@tube-builder I had used to patch chrome after every update using that answer before I found this solution. I was hoping it would be permanent.

[Vinz]

It will only be a matter of time until you can't develop anything anymore using Chrome :)

[Lucas Bustamante]

My Windows is Home Premium, I don't have gpedit.msc :/

[Anders Lindén]

Today, I had to use options.AddArguments("chrome.switches", "--disable-extensions --disable-extensions-file-access-check --disable-extensions-http-throttling"); instead of just `--disable-extensions. I think one of the additional switches can be omitted, but not both.

[Jimadine]

Works for me in Chrome 58.0.3029.81, Win 7 x64 :) Hoping this solution will last!

[Antony Hatchkins]

@Jimadine happy to hear that :)

[Jimadine]

@Antony Hatchkins: Step 5 won't work in Chrome 59, hence my (attempted) edit. It should be: 3 dots > More Tools > Extensions, or chrome://extensions now.

[T.Todua]

can you explain it a bit for mortal humans? what is that script, or where to put it...

[Joshua]

Thank you very much! It works on 61.0.3163.100 and Win 10. Google won't let me publish my only fork of extension. At least, I can now use it myself.

[Daniel Leach]

Extension installed but then gave a different warning: Unsupported extensions disabled

[Steve Staple]

Thanks Panther. Added the "chrome.adm" template via the dialog, and got this error: The following entry in the [strings] sectin is too long and has been truncated. This is followed by a page of Cyrillic?

[Steve Staple]

Anthony Hatchkins: You lost me at 'Pack your extension'

[Antony Hatchkins]

@SteveStaple I thought that if you happened to create an extension, packing it won't be a big issue for you ;) I've updated the instructions.

[Antony Hatchkins]

Use @ to automatically notify other user about your post (like @Panther).

[Panther]

@SteveStaple Sorry, but I don't know what would be the cause of such an issue. :( I'm not an expert at this, just followed the instructions from the page I linked. Fortunately it worked for me.

[EAX]

I think the .bat patch doesn't work anymore because of Chrome updates. It says that it's already patched but I can still see the popup. Version 66.0.3359.139 (Official Build) (64-bit)

[D Adams]

This answer is under-rated because it can be adapted to automate other annoying unavoidable GUI button clicking tasks.

[jkdev]

(Bonus tip 1) When using Selenium you can immediately open a new window, wait for the popup in the new window, and then close the new window to dismiss the popup. stackoverflow.com/a/36507179/3345375

[jkdev]

(Bonus tip 2) You could also try this: Add the flag --enable-automation to avoid getting the popup.

[freginold]

This didn't work for me. Win 10, Chrome up to date. After following the steps, the popup remained.

[jkdev]

@freginold To figure out what worked, I had to experiment with various sequences of opening and closing tabs/windows. The sequence might be different for other OS’s and browser versions.

[Mike]

about the 2018 update you posted, I tried on Version 70.0.3538.77 (Official Build) (64-bit) but it's not working. If it is, could you explain more steps 4 (installing) and 5 (whitelisting)? Thanks

[Altimus Prime]

"Then copy the crx installed extension ID to the whitelist and restart chrome. The popup should be gone" - How do you do this?

[johny why]

i got "Apps, extensions, and user-scripts cannot be added from this website".

[George]

@jkdev The command line switch --enable-automation has its own obnoxious side effect: a div appears at the top of each page until dismissed (then it stops appearing). The Developer Mode popup can be dismissed by hitting ESC when it first appears. Annoying in either case!

[Aindriú]

@Aunt Jemima You need to use the new .crx file that you created from packing. After packing the original extension you can delete it. Drag & drop the .crx file into the Chrome extensions, then get the unique ID of the .crx extension and add it to the white list in Local Group. Also remove the old ID in the white list. It should work.

[Cardin]

OP asks how to disable the popup, you instead decided to disable his extensions instead. :/

[Cardin]

OP isn't using WebDriverIO. Moreover OP is asking to disable the popup, but you went to disable extensions instead.

[Elijah]

If Windows is telling that it cannot find gpedit.msc, look at this article itechtics.com/enable-gpedit-windows-10-home

[gp.]

unpacked extension works with developer mode warning. but with crx, the extension is disabled always. google requires the extension to be published on web store and installed from there.

[Chris_F]

Right, it's because of the malware... we aren't trying to annoy people who use extensions we blocked from our store like Dissenter...

[Harshit Juneja]

Chrome doesn't let users install packaged extensions and says, package is invalid: CRX_REQUIRED_PROOF_MISSING.

[Haritsinh Gohil]

@HarshitJuneja may be you have to whitelist the extension id, and restart chrome.

[Steve Smith]

@momomo Obviously it can be set in a config or something, but this is just example code.

[林果皞]

I need to add custom manifest key and upload to web store is not an option.

[xyz]

Drag-and-dropping a .crx file just popup a save as window, and will not install it. Chrome version 80.0.3987.163.

[JinSnow]

Could not find the registry key for edge chromium

[Burak Gök]

@xyz Drag-and-dropping a .crx file installs the extension in version 81.0.4044.122. @JinSnow Look at Microsoft Edge - Policies - ExtensionInstallAllowlist

[user5305519]

If I am not mistaken, @amanpreet-kaur's answer is for people who are automating something using Chrome driver. In the snippet, Java was probably used to automate a Chrome driver. This answer does NOT apply for you if you yourself are just using Chrome as-is from your desktop. See: chromedriver.chromium.org

[robe007]

If under Administrative Templates you not see Google, go and follow this instructions to make it visible. Tested on Chrome 83.0.4103.97 and works perfectly.

[abhijit]

This was the best solution. This works even for portable installations.

[Nicola]

Already described here: stackoverflow.com/a/61572593/940974

[tkit]

I think something changed on win10, I used to be able to just drag the packed extension to the extensions screen, and now it shows CRX_REQUIRED_PROOF_MISSING message.

[JinSnow]

Why keeping an answer depreciated then an history of "edit" from 2018? (And it does not work anymore). This answer should be updated, cleaned or removed.