Hide Chrome's Disable developer mode extensions warning

Martin Brinkmann
Jul 4, 2017
Google Chrome

The warning "Disable developer mode extensions" is displayed in Chrome when you install non Chrome Web Store extensions in the browser.

This warning is displayed on each start of the browser, and it stays on the screen until you hit one of the available buttons (disable or cancel).

Google stated that it displays the warning because of malware that force-installed extensions to Chrome.

If you are a developer of Chrome extensions, or downloaded an extension from a reliable source, you probably want to do away with the warning as it can be quite annoying after some time.

Probably the easiest option is to use Chrome Canary. Unlike Chrome Stable, Canary does not display warnings for extensions installed from outside the Chrome Web Store. I did not try the Developer Edition of Chrome to find out if it omits the warning as well.

Google Chrome itself comes without any options to suppress the warning message about installed developer mode extensions. Windows, Linux and Mac administrators may use policies however to hide the warning so that it does not show up.  Note that this works only on Professional or Enterprise versions on Windows, as Home versions don't come with the Group Policy Editor.

Disable developer mode extensions warning in Chrome

disable develope rmode extensions

The very first thing you need to do is download the latest policy templates from the Google Support website. The following instructions are for Chrome installations on Windows. Instructions for the other operating systems similar.

The policy file is distributed as a zip archive that you need to extract.

  1. Once you have done so, move the file policy_templates\windows\admx\chrome.admx to c:\windows\policydefinitions, and the file policy_templates\windows\admx\[yourlanguage]\chrome.adml to c:\windows\policydefinitions\[yourlanguage]\chrome.adml
  2. Open chrome://extensions in the Chrome web browser afterwards, and locate the extension or extensions that you have installed from a source that is not the Chrome Web Store.
  3. Copy the ID of the first to the clipboard.
  4. Open the Group Policy Editor on Windows: tap on the Windows-key, type gpedit.msc, and hit the Enter-key. The Chrome policies should be loaded automatically.
  5. Go to User Configuration > ADministrative Templates > Administrative Templates > Google Chrome > Extensions.
  6. Double-click on the "Configure extension installation whitelist" policy.
  7. Set the policy to enabled.
  8. Click on the show button.
  9. Add the IDs of any non-Chrome Web Store extension to the listing.
  10. Click ok in the end.
  11. Restart the Chrome browser.

extension installation whitelist chrome

Second option: patching chrome.dll

Another option is highlighted on the Stackoverflow forum. It requires patching the chrome.dll file.

Word of warning: Since the script that is used for that patches a file that Chrome requires for running, it is recommended that you create backups before you continue. It may also be easier to just use Chrome Canary instead of stable Chrome.

You find the script on this page on Stackoverflow. Copy all of it and put it in a plain text file that you create anew. Rename the plain text file so that it has a .bat extension afterwards.

You find the chrome.dll file in the application folder. On Windows, this can be C:\Program Files (x86)\Google\Chrome\Application\[ChromeVersion] or C:\Program Files\Google\Chrome\Application\[ChromeVersion]

You have two options now: you can run the batch file so that it patches all chrome.dll files it finds, or drag and drop a chrome.dll file onto the batch file icon to have it processed only. I suggested you do the latter after verifying again that you have created a backup of the chrome.dll file.

The batch file patches chrome.dll to suppress the "disable developer mode extensions" warning in the web browser.


Now You: Have another tip on dealing with the popup?

Hide Chrome's Disable developer mode extensions warning
Article Name
Hide Chrome's Disable developer mode extensions warning
The guide describes three methods to suppress the "disable developer mode extensions" warning popup in Google Chrome for non-Store extensions.
Ghacks Technology News

Previous Post: «
Next Post: «


  1. a said on November 10, 2020 at 9:35 am

    i can not find Configure extension installation whitelist policy. ?

  2. jack said on November 10, 2020 at 9:11 am

    there is no chrome.adml file to be found

  3. Darthagnon said on June 18, 2020 at 6:48 pm

    There’s a patch script on SourceForge that has been updated recently (03-2020) that will patch out the Developer Mode Extensions warning: https://sourceforge.net/projects/devwarningpatchgen-bat/

    1. Sam said on June 20, 2020 at 8:51 am

      Ha. That’s fine and dandy that such a “thing” exists but I imagine it’s for one of those covidiots code monkeys to use because I see no option to download the .bat file.

  4. Kamal said on May 27, 2020 at 12:55 pm

    Thanks Martin! I worked!

  5. David S said on May 16, 2020 at 4:18 pm

    I found something that will load user-packed extensions and works beautifully:


    Note: I’m not from their team, I’ve just been looking for an elegant solution for this for years.

  6. Anonymous said on April 18, 2020 at 2:48 pm

    I can’t find the dll file from the link. Can someone post a direct link to it?

  7. jan said on April 15, 2020 at 6:58 pm

    release 3.2 just pushed out Added auto-updating patterns (see patterns.xml) and fixed Edge 81

  8. VST said on February 14, 2020 at 9:19 pm

    I found that opening subsequent sessions of Chrome don’t show the popup as long as the first session is still open. Next step was to hide the initial session in the notification area using the free tool RBTray found here http://rbtray.sourceforge.net/

    I know it’s not perfect but I don’t think the Chromium devs will allow any way to block this going forward so hiding is our best bet. This will work on any Chromium version and practically all Windows versions.

    CPU/RAM usage seems negligible.

  9. Dave said on December 22, 2019 at 2:53 am

    Never mind the above. I downloaded the .bat fie yochaim pointed to. It didn’t take though. Should I have moved it to a specific folder first? Thanks.

    1. TxRedneck said on December 30, 2019 at 6:17 pm

      Hey Dave, right click the batch file and RunAs Admin will do what you seek.

  10. Dave said on December 22, 2019 at 2:44 am

    User Configuration > ADministrative Templates > Administrative Templates > Google Chrome > Extensions. doesn’t exist. They must have changed it to avoid end users from fixing their bull hockey!

  11. aa said on October 14, 2019 at 9:13 am

    “ID of the first”
    ID of the phuqing what?

    1. CoffeeAddict said on October 19, 2019 at 9:18 am

      I’m pretty sure he meant the ID of the first extension you want to add to the whitelist, though he wrote it in an ambiguous manner. Often times, though, you only want load to load a single extension in which case the first is also the last ;) But don’t waste your time with the Group Policy method as it doesn’t work in its current state. Try the patch method instead…

      However, while most here have commented that the Group Policy settings were ignored, the Group Policy changes in my case gave me an error on every subsequent attempt to manually load an extension. And I could only solve it by deleting the “chrome.adm*” files that were added. So, this method does apparently change *something* – just not the right thing. Oh, and I should add that these errors only started appearing once I had logged off and then logged on again on my Windows account. So it must be affecting some setting that’s not instantaneously applied.

  12. yochaim said on August 23, 2019 at 6:28 am

    updated version of the stackoverflow script for all chromiums is available from https://sourceforge.net/projects/devwarningpatchgen-bat/

    1. CoffeAddict said on October 13, 2019 at 4:31 am

      @yochaim: Thanks for this neat little script! Works great with the Brave browser! However, unfortunately not with the Dissenter browser. When trying to patch the Dissenter browser’s “chrome.dll” file, the batch file simply goes into an endless loop. Any idea why? The Dissenter browser is a Brave fork so there shouldn’t be any issue in theory?

      1. CoffeeAddict said on October 13, 2019 at 12:44 pm

        Here’s the download page for the Dissenter browser, by the way, if anyone wants to troubleshoot this: https://dissenter.com/download

    2. ShintoPlasm said on August 29, 2019 at 1:46 pm

      @yochaim: Amazing, thank you so much. Chrome ignoring its own group policies (on W10 Pro) has been driving me insane.

  13. FierceNinja said on June 29, 2019 at 9:30 pm

    I have windows professional and I carried out all the steps to whitelist the extensions IDs. Did not work. Turns out there is a reason behind this. Follow this thread: https://support.google.com/chrome/forum/AAAAP1KN0B0NtVb8mWPidA/?hl=en&gpf=%23!topic%2Fchrome%2FNtVb8mWPidA

    This guy figured it out. But I am guessing (am not too technically bright here) it would only work if the extension is your own given the steps involved. If anyone can figure out how to repack and get new IDs for extensions that are not your own, please share. It would be very helpful.

  14. Anonymous said on May 19, 2019 at 3:56 am

    This is why I hate new tech. Bunch of overpaid code monkeys. I can only dream that their weekly forced updates on everything I own were next to useless… instead they’re detrimental to my user experience. Why the solution to this isn’t a setting I can disable, and is instead a four page blog post that involves patching a dll is fucking beyond me. When you can’t even include a button that says “Don’t show this again”, or have a security setting that allows running in dev mode, forcing me to interact with a popup every time I open chrome, you’re the fucking problem. Fuck you.

    1. Anonymous said on October 4, 2019 at 3:12 pm


    2. ShintoPlasm said on August 11, 2019 at 6:42 pm


  15. Griff said on April 25, 2019 at 3:19 am

    Either the whitelist doesn’t work (anymore?) for developer mode addons, or Chrome now just outright ignores the policy. Using Win7 Pro.

  16. Dee said on April 23, 2019 at 3:34 am

    Doesn’t work for me either, but seeing at the warning message is about “developer mode” being on, not the fact that there is an add-on that requires it, I am not surprised.

    Whitelisting the add-on is a different thing from turning on/off Developer mode.

  17. Robert Ghafoor said on October 12, 2018 at 12:07 pm

    Group policy will not work for anyone with a “Home” edition must be professional as google ignores the policy rules for windows home editions…

  18. RoySeberg said on July 15, 2018 at 2:28 pm

    I tried both the Group policy and the dll patch and the annoying popup keeps appearing.

  19. Ants said on May 3, 2018 at 6:14 pm

    Googles Group policy files do not honor the whitelist. Getting really annoyed at Google.

  20. renatototo said on March 5, 2018 at 2:53 am

    Group Policy didn’t worked for me.
    Chrome Version 64.0.3282.186 (Official Build) (64-bit)
    I have customized an extension and I keep on getting this warning.
    I don’t like patching dll’s but, I’ll have to try it.

  21. Nick Ellis said on December 6, 2017 at 1:43 am

    Yeah, I’m going to go ahead and quit Chrome. They do this to discourage extensions that don’t fit their “agenda”, like using the Coincidence Detector plugin. The more I learn about (((Google))) the more I want to run away from (((them))).

    1. Steven Papier said on December 19, 2017 at 2:30 pm

      If Google’s “agenda” is to make it more difficult for anti-Semites to promote THEIR agenda, then anyone who can see how ugly and hateful the alt_right is would support it. (Google “Coincidence Detector”).

      1. Ron said on November 14, 2019 at 11:59 pm

        It’s not “ugly and hateful” to wish not to be ruled by (((the ugly and hateful people))) who rule us now. Think about it… tribe-owned google and facebook got FUNDED by (((the big banks,))) while NON-tribe-owned alta vista and MySpace got memory-holed. The more you know, the more you realize that the screeching (((anti-white communists))) calling people “haters” are THEMSELVES the hateful ones, and always have been.

      2. Anonymous said on January 5, 2020 at 1:13 am

        Cool story bro. Why don’t you (((fuck off))).

      3. Mark said on February 12, 2018 at 1:59 am

        Not just extensions, but certain searches, like “American Inventors” or “White American Couple” clearly pushes Google’s not-so-hidden endgame. Even Google Home has censored searches for Jesus Christ.

      4. Anonymous said on February 22, 2018 at 5:30 am

        Are you literally pushing your delusional conspiracy theories about white oppression on a ghacks guide? Google has their problems for sure, and yet you’ve managed to skip right past all of them to proselytize the virtues bigotry.

        I just… where did your life take this turn? What went wrong to produce you?

      5. Anonymous said on August 8, 2019 at 4:34 pm

        Is it a conspiracy, if you can do the search yourself, and get the same result?

      6. Doug Rowland said on May 29, 2019 at 1:29 am

        When you search for American Inventors, you will see that out of the first 20 results, 18 are black. The two whites are Thomas Edison and Alexander Graham Bell. Kind of hard to forget about them. Seriously Google, WTF?. 90% for 12% of the population.

      7. anon said on August 29, 2018 at 10:43 pm

        This guy must be REAL fun at parties!!!!

      8. Anon2 said on January 16, 2019 at 8:46 am

        He has a point. If the 1st guy was at my party, I would invite him for sure!

  22. THGhost said on August 6, 2017 at 8:25 pm

    “Once you have done so, move the file policy_templates\windows\admx\chrome.admx”

    Move what file exactly? That file does not exist in the zip file!

    Neither version works for me.

  23. vdg said on July 25, 2017 at 3:30 pm

    First option didn’t work here. Second option disables Netflix :/

  24. gerardo said on July 6, 2017 at 5:09 pm


    With the first option, after an update, i have to do it again?

  25. I K said on July 4, 2017 at 10:33 pm

    Thank you very much for posting this information, it solved a minor but annoying problem for me!

    The second option (patching chrome.dll) worked for me when I ran the batch file as administrator.

    You may find it worth trying this option if your Windows 10 Home edition prevents you from modifying group policies and you want to continue using the stable version of Chrome.

  26. James T. said on July 4, 2017 at 9:48 pm

    http ://bugs(.)chromium(.)org/p/chromium/issues/detail?id=491689
    http ://stackoverflow(.)com/a/38011386

  27. Maelish said on July 4, 2017 at 3:52 pm

    @Martin I tried those policy templates months ago but they didn’t work. Did they work for you?

  28. Curtis K said on July 4, 2017 at 12:41 pm

    How about uninstall Google Chrome? That is not hard to do (posting on VirtualBox Ubuntu) I have it uninstalled on the host.

    1. Eric Bostrom said on December 11, 2019 at 6:05 pm

      I use Arch btw

      1. Anonymous said on March 28, 2020 at 8:25 am

        Linux users are just as bad as Crossfit people.

    2. MGM said on September 9, 2019 at 10:59 pm

      Linux users always let you know they use Linux

      1. Anonymous said on January 1, 2020 at 1:03 am

        thanks for this random funny comments.. fuck linux users (specifically those who always have to “brag” about using linux)

      2. Anonymous said on March 11, 2020 at 1:11 am

        Fuck windows and mac users.

      3. Forge said on September 28, 2019 at 3:31 pm

        No I don’t. ;)

      4. Anonymous said on December 31, 2019 at 4:23 am

        you just did

    3. patr said on June 24, 2019 at 5:06 am

      no one really cares that you are “posting on virtualbox ubuntu”

Leave a Reply

Check the box to consent to your data being stored in line with the guidelines set out in our privacy policy

We love comments and welcome thoughtful and civilized discussion. Rudeness and personal attacks will not be tolerated. Please stay on-topic.
Please note that your comment may not appear immediately after you post it.