Group Policy and registry guide
How to block Chrome extensions with Group Policy and the registry
Any user can add an AI agent extension to Chrome without admin rights, and it then works inside every site they are signed in to. One Group Policy setting or one registry key stops that on every Windows PC. Here are the exact paths and values.
Next step
AI Agent Blocklist: AI extension IDs for your GPO
Chrome and Edge IDs of AI agent and assistant extensions, each with a risk grade, as lists you paste into Group Policy or a registry file, updated every day.
From $99 a month for one organisationOne company, school or district
What happens when Chrome extensions are left open
Chrome lets users install extensions into their own profile. No UAC prompt, no software request, no entry in your software inventory. That was a nuisance with coupon tools. With AI agents it becomes a data and access problem.
Without a Chrome extension policy
- Staff install AI sidebars and agent extensions in seconds
- Extensions with all-sites access read webmail, CRM and HR pages
- Agent extensions click and submit as the signed-in user
- Updates change what an extension does without a new prompt
- You learn about it from a help desk ticket, or an incident
With the GPO in place
- Listed extensions cannot be installed from the Chrome Web Store
- Installed copies are disabled and cannot be switched back on
- An asterisk blocks everything except your approved list
- Users see the block and can ask IT for an exception
- chrome://policy shows each PC's state in seconds
A colleague recommends an AI helper that "does the boring clicks".
Two clicks in the Chrome Web Store. No admin rights needed.
The user accepts access to all sites so the agent can work anywhere.
The agent reads pages and fills forms inside live, signed-in sessions.
Silent updates add features, permissions or a new owner later.
Agents that read web pages can be steered by text hidden in those pages. Researchers showed in 2025 that AI browsers and agents could be tricked this way into acting against their own users. A block on the extension removes that path on managed PCs.
Three ways to set the same Chrome policy on Windows
Chrome reads its policies from the Windows registry. Group Policy, a registry script and Intune all end up writing the same keys, so pick the tool that already manages your PCs.
Group Policy
Chrome ADMX templates in the central store, one GPO linked to the OUs with your PCs. Changes reach PCs at the next policy refresh.
For Active Directory domainsRegistry
A .reg file, a reg add command or your RMM script writes the keys directly. Google documents this route for PCs that are not joined to Active Directory.
For workgroup PCs and RMM toolsIntune
The Windows settings catalog includes the Google Chrome policies. See our guide to blocking Chrome extensions with Intune.
For cloud managed PCsAdd the Chrome ADMX templates
Windows does not ship with Chrome policy templates. Without them, the Google folder simply does not appear in the Group Policy editor.
Download the templates
Get the Google Chrome Enterprise bundle and open its Configuration folder, or download policy_templates.zip on its own. Use a current version so new policies show up.
Copy the ADMX files
Copy google.admx and chrome.admx into the central store, \\yourdomain\SYSVOL\yourdomain\Policies\PolicyDefinitions.
Copy the language files
Copy the matching google.adml and chrome.adml into the language subfolder, for example en-US, inside PolicyDefinitions.
Open the editor
In Group Policy Management, create or edit a GPO. The Chrome settings appear under Computer Configuration > Policies > Administrative Templates > Google > Google Chrome.
Single PC only
For a standalone PC, run gpedit.msc. The same folder sits under Local Computer Policy > Computer Configuration > Administrative Templates once the templates are installed locally.
Microsoft advises building a fresh PolicyDefinitions folder when you update templates, then swapping it in, so you can roll back if a newer file clashes with an older one.
Block Chrome extensions with Group Policy
All extension policies live in one folder: Administrative Templates > Google > Google Chrome > Extensions. They exist under Computer Configuration and under User Configuration. For a security block, use Computer Configuration.
Block named extensions
- Open Configure extension installation blocklist
- Select Enabled, then Show
- Add one extension ID per line
- Select OK, apply, link the GPO to a test OU
- Run gpupdate /force on a test PC
Block all, allow a few
- Enable Configure extension installation blocklist with one value: *
- Enable Configure extension installation allow list
- Add the IDs you approve, one per line
- Include sign-in, password manager and line of business extensions
- Test with a normal user account, not an admin
cecngibhkljoiafhjfmcgbmikfogdiko mokiolnliafiddobcgmmnmhbmimpccon hmdkfngkncmbgiehonfebecighedjiak
Example entries from our list: the Manus browser operator, Sider Operator and Genspark extensions. Each one is an agent or agent-style extension that works inside web pages.
The allow list only lifts entries from the blocklist. Building and maintaining it is a project in itself, covered on our Chrome extension allowlist page.
Block Chrome extensions in the registry
On PCs without a domain, or when your RMM tool pushes scripts, write the policy keys yourself. List policies use a subkey with numbered string values. JSON policies use one string value.
| Policy | Key | Value name | Type | Value |
|---|---|---|---|---|
| Blocklist | HKLM\SOFTWARE\Policies\Google\Chrome\ExtensionInstallBlocklist | 1, 2, 3 ... | REG_SZ | One extension ID each, or * in value 1 |
| Allow list | HKLM\SOFTWARE\Policies\Google\Chrome\ExtensionInstallAllowlist | 1, 2, 3 ... | REG_SZ | One approved extension ID each |
| Extension management settings | HKLM\SOFTWARE\Policies\Google\Chrome | ExtensionSettings | REG_SZ | JSON on a single line |
| User level copy | HKCU\SOFTWARE\Policies\Google\Chrome\... | same | same | Applies to one Windows user only |
Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome\ExtensionInstallBlocklist] "1"="cecngibhkljoiafhjfmcgbmikfogdiko" "2"="mokiolnliafiddobcgmmnmhbmimpccon" "3"="hmdkfngkncmbgiehonfebecighedjiak"
reg add "HKLM\SOFTWARE\Policies\Google\Chrome\ExtensionInstallBlocklist" /v 1 /t REG_SZ /d "*" /f reg add "HKLM\SOFTWARE\Policies\Google\Chrome\ExtensionInstallAllowlist" /v 1 /t REG_SZ /d "<approved extension ID>" /f
Keep the value names simple: 1, 2, 3 and so on, without gaps. When the list changes, rewrite the whole key from your current list instead of editing single values.
If a GPO also sets the same policy, Group Policy wins and rewrites the key at the next refresh. Google advises setting the GPO entry to Not Configured when the registry is your source of truth.
Extension management settings: the JSON policy
The GPO entry Extension management settings (registry value ExtensionSettings) takes one line of JSON. It does everything the two list policies do, plus removal, custom messages and permission limits.
{"*":{"blocked_permissions":["debugger"],"blocked_install_message":"Ask IT before adding extensions."},"cecngibhkljoiafhjfmcgbmikfogdiko":{"installation_mode":"removed"},"mokiolnliafiddobcgmmnmhbmimpccon":{"installation_mode":"blocked"}}
Removed blocks the extension and takes existing copies out of Chrome. Blocked keeps them installed but disabled.
Stops extensions that ask for a listed API permission. Installed extensions that need it stop loading.
Keeps allowed extensions away from sites such as finance or HR portals. No script injection, no cookies.
Added to the Chrome Web Store error. Tell users how to request an exception.
ExtensionSettings overrides the blocklist, allow list, allowed types and install sources policies when they conflict. Run one approach per fleet so nobody wonders which list is in charge.
Which setting wins: GPO, registry, machine or user
When the blocklist does not behave, the cause is almost always a second source of the same policy. Chrome takes the policy from the highest ranked source and ignores the others.
Group Policy rewrites its registry keys at every refresh. A manual edit to a key that a GPO controls lasts only until the next refresh.
Computer Configuration writes to HKLM. Machine level policy outranks user level policy for the same setting in Chrome.
User Configuration writes to HKCU. It applies only when no machine level value exists for that policy.
The Chrome policy Allow merging list policies from different sources can combine a named list policy from sources of the same scope and level. Without it, lists do not add up.
Older guides name the policies ExtensionInstallBlacklist and ExtensionInstallWhitelist. Chrome 86 introduced the current names. Use ExtensionInstallBlocklist and ExtensionInstallAllowlist in new work, and clean up old keys so two lists do not compete.
Close the side doors
A blocklist covers the Chrome Web Store. Users who are determined to run an agent extension may try other routes. These Chrome policies close them, all in the same Extensions folder.
Set it to disallow so users cannot switch on developer mode and load unpacked extensions from a folder. Chrome 128 and later.
Stops extensions that other software on the PC tries to add to Chrome from outside the browser.
Leave it unset unless you host your own extensions. Each URL pattern you add becomes an install route.
Limit installs to types you use, such as extension and theme. User scripts and hosted apps can then be refused.
With an asterisk in the blocklist, unpacked extensions stay blocked even if their ID is on the allow list. Only packed extensions can be allowed.
Check that the GPO or registry key works
Test on two PCs: one that only receives the GPO and one where a user had agent extensions installed before.
- Run gpupdate /force, then gpresult /r to see that the GPO applies
- Open chrome://policy and select Reload policies
- ExtensionInstallBlocklist shows status OK with your values
- The source column shows the platform as you expect
- A blocked extension that was installed is now disabled
- The Chrome Web Store refuses to add a blocked extension
- Approved extensions on the allow list still load
- Edge received its own policy, checked in edge://policy
Edge reads its policies from SOFTWARE\Policies\Microsoft\Edge and uses the Microsoft Edge templates. The setting names differ, for example Control which extensions cannot be installed. Our Edge extension blocklist page has the full map.
Roll the GPO out in stages
A Chrome extension block touches every user who opens a browser. A staged rollout keeps the help desk calm and gives you a clean record of what changed and when.
| Stage | What you do | What you check |
|---|---|---|
| 1. Inventory | Open chrome://extensions on a handful of typical PCs per department, or pull the list from your endpoint tools. Note every extension that people rely on. | You have the IDs of sign-in, password manager and business extensions before anything is blocked. |
| 2. IT pilot | Link the GPO to an OU with IT staff PCs only. Start with the AI agent IDs, not the asterisk. | chrome://policy shows status OK, blocked agent extensions are disabled, nothing else broke. |
| 3. Department pilot | Add one department through security filtering on the GPO, ideally a team with many AI helpers installed. | Requests for exceptions arrive through your process, not as complaints. Adjust the allow list. |
| 4. Everyone | Link the GPO to the OUs with all user PCs. Announce the change with the reason and the request route. | gpresult on random PCs shows the GPO. The help desk has a short answer ready. |
| 5. Tighten | If your policy calls for it, switch to the asterisk with an allow list, then close the side doors above. | Developer mode is off, only approved extensions run, and new AI extensions are blocked by default. |
Each list update after go-live is just an edit to the same GPO. Keep the previous list in your change record, so you can show an auditor what was blocked on any given day.
What to block, what to watch, what to allow
Every entry in our list has a category and a risk grade. That lets you write a GPO that matches your policy instead of a list typed from memory.
- Browser agent and operator extensions
- General autonomous agent extensions
- AI extensions with high risk grades
- Unknown AI extensions asking for all sites
- Summary and reading sidebars
- Meeting note and transcription helpers
- Writing assistants in webmail
- Matching AI domains in firewall logs
- The AI assistant your company licensed
- Single sign-on and password managers
- Your own line of business extensions
- Each with an owner and a review date
Write the rules down before you enforce them. Our AI agent acceptable use policy gives you wording to start from, and shadow AI agents explains how to find what is already in use.
Keep the GPO list current without the busywork
New AI agent extensions appear every week. The AI Agent Blocklist gives you the IDs, sorted by category and risk grade, ready for Group Policy and registry files.
- Chrome and Edge extension block lists for Group Policy, Intune and the Google Admin console
- Firefox extension IDs, macOS bundle IDs, Windows package IDs and process names
- 2,600+ AI agent domains as plain lists, CSV, JSON, hosts and firewall formats
- Updated every day; download access within one business day of your order
From $99 a month for one organisationMSP and product licences on the pricing page
See plans Ask a questionAsk us or order a plan
Tell us what you need to block and where your rules live. We reply within one business day.
- Files for firewalls, DNS filters, secure web gateways, MDM and browser policies
- Updated every day as new AI browsers, agents and extensions appear
- Plans for one organisation, for MSPs and for product makers, or a hosted filter we run for you
Group Policy and registry questions
How do I block Chrome extensions with Group Policy?
Add the Chrome ADMX templates to your central store, edit a GPO and go to Computer Configuration > Policies > Administrative Templates > Google > Google Chrome > Extensions. Enable Configure extension installation blocklist, select Show and add one extension ID per line.
Run gpupdate /force on a test PC and check chrome://policy.
How do I block all extensions in Chrome with GPO?
Enable Configure extension installation blocklist with a single value, an asterisk. That blocks every extension. Then enable Configure extension installation allow list and add the IDs you approve, such as your password manager and single sign-on extension.
How do I disable Chrome extensions in the registry?
Create the key HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome\ExtensionInstallBlocklist and add string values named 1, 2, 3 and so on, each holding one extension ID. A single value 1 set to an asterisk blocks everything. Then reload policies in chrome://policy.
Where is the Chrome extension allow list in the registry?
It is the key HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome\ExtensionInstallAllowlist with numbered string values, one extension ID each. It only has an effect when the blocklist blocks those extensions, usually through an asterisk.
Why does Chrome ignore my registry change?
A Group Policy setting for the same policy overwrites manual registry edits at the next refresh, so set the GPO to Not Configured if you manage it in the registry. Also check the key name, the value type, and whether Extension management settings override the blocklist.
Does the blocklist remove extensions that are already installed?
Blocked extensions that are already installed are disabled and users cannot switch them back on. To have Chrome remove them, use Extension management settings with the installation mode removed for those IDs.
Do these Chrome policies need a domain-joined PC?
No for the blocklist and allow list: Google documents the registry route for computers that are not joined to Active Directory. Force-installing an extension from outside the Chrome Web Store needs a PC joined to Active Directory or Microsoft Entra ID, or enrolled in Chrome Enterprise Core.
Running Macs as well? See blocking Chrome extensions on Macs with Jamf. Chromebooks and cloud managed browsers use the Google Admin console.
For the full picture across browsers, start at how to block AI browser extensions. AI browsers are separate apps, and removing AI browsers covers those.
Microsoft, Windows, Active Directory, Microsoft Edge, Microsoft Entra and Intune are trademarks of the Microsoft group of companies. Google, Chrome, Chrome Web Store, Chrome Enterprise and Google Admin console are trademarks of Google LLC.
Manus, Sider and Genspark are trademarks of their respective owners. Names are used only to identify the products discussed. AI Agent Blocklist is not affiliated with, sponsored or endorsed by these companies.