Blocked browser extension: disabled, not deleted. What does that mean?

When you block an already installed extension with Chrome's blocklist policy, Chrome disables it and the user cannot re-enable it. It is not uninstalled, and if you later take it off the blocklist it turns back on automatically. For a confirmed malicious extension you usually want removal as well as a block.

What the sources say

The Chromium definition of ExtensionInstallBlocklist says installed extensions that are blocked "will be disabled" with no way for the user to enable them, and that an extension disabled this way is re-enabled automatically when it is removed from the list. Separately, the ExtensionSettings schema lists an installation mode called removed next to blocked, allowed, force_installed and normal_installed. Read the current policy page for exact behavior of removed, since we did not find a description of it in the schema text.

Microsoft Edge's documentation uses the same wording for its blocklist: blocking an extension already installed disables it and stops the user re-enabling it, and it is "not uninstalled, just disabled."

Why the difference matters

A disabled extension cannot run in the browser. For most incidents that stops the active harm. But three things remain:

• Local data. Any data the extension stored is still on disk until it is removed.
• Reversibility. A mistaken unblock, or a policy change that drops the entry, puts the extension back in service without anyone deciding to.
• Evidence. A disabled extension is still there to examine, which helps an investigation.

A response sequence

1. Block first. Add the extension ID to the blocklist, or set the blocked mode in ExtensionSettings, to stop it running quickly.
2. Preserve evidence. Record the extension ID, version, and which devices had it before removing anything.
3. Remove it. Use the mechanism your browser management tool provides for removal, then confirm on a sample device.
4. Rotate exposed secrets. If the extension could read sessions or tokens, treat those as exposed. See how to respond to a malicious extension.
5. Decide the long-term state. Keep it blocked permanently, and write down why.

Keep the block in place

Because unblocking re-enables, do not remove a malicious ID from the blocklist after cleanup. Leaving it costs nothing. Dropping it means a reinstall or a leftover copy could come back.

Edge cases to check

• Force-installed extensions. In Chrome the force list supersedes the blocklist, so remove the ID from the force list first.
• Multiple policy sources. ExtensionSettings can override per-extension configuration from legacy policies, so check that no other entry contradicts your block.
• Other browsers. Firefox uses its own ExtensionSettings policy, where a blocked mode prevents installation and removes an installed copy. See managing Firefox extensions with policy.

Quick check

Sources

• Chromium policy definition: ExtensionInstallBlocklist
• Chromium policy definition: ExtensionSettings
• Microsoft Learn: Manage Microsoft Edge extensions with policies
• Firefox Enterprise Admin docs: ExtensionSettings

Last reviewed: 19 October 2026.