Fix Browser Extension Disabled Due to Security Risk – Chrome/Edge

Cybersecurity & Malware Beginner 👁 6 views 📅 Jun 19, 2026

Your browser disabled an extension claiming it's a security risk. The culprit is usually a manifest mismatch or a corrupted install. Here's the fix that works 95% of the time.

Yeah, that message is annoying. Let's kill it fast.

You see the yellow bar: "Disabled extension — likely a security risk." Or maybe Chrome/Edge just grayed out the icon. Either way, the fix is almost always the same. Don't waste time scanning for malware first — that rarely helps unless you actually downloaded a shady extension.

Step 1: Remove the extension completely

  1. Open Chrome (or Edge) and click the three-dot menu.
  2. Go to Extensions > Manage Extensions.
  3. Find the flagged extension. Click Remove. Yes, full remove, not just toggle off.
  4. Restart the browser.

This clears any corrupted files or bad registry entries the extension left behind. Don't skip the restart — it forces the browser to drop cached permission data.

Step 2: Reinstall from the official store

  1. Open the Chrome Web Store or Edge Add-ons site.
  2. Search for the exact extension. Make sure it's by the real developer — check the publisher name against the extension's support site.
  3. Install fresh.

Why this works: The browser flags extensions when:

  • The extension's manifest file gets corrupted (happens after a failed update).
  • It's an old Manifest V2 extension that Google started blocking in 2023. Reinstalling sometimes gets you the V3 version.
  • The extension was tampered with by malware or another extension. Yes, one bad extension can infect others.

Reinstalling from the official store overwrites that corrupted manifest and re-verifies the signature.

Step 3: Check for enterprise policies (only if Step 2 failed)

If the extension is still blocked after reinstall, your IT department or some security software pushed a policy. Here's how to check:

  1. Type chrome://policy in the address bar (or edge://policy for Edge).
  2. Press Enter.
  3. Look for entries that mention "ExtensionInstallBlocklist" or "ExtensionSettings".
  4. If you see your extension's ID in a blocklist, that's the cause. You can't override that unless you're an admin — call your IT team.

If you're a home user and see policies, it's usually a security suite like Malwarebytes or Norton that added them. Disable the security software's browser protection temporarily and test.

Less common variations of this issue

Variation A: Extension disabled after a browser update

Chrome 116+ started aggressively blocking Manifest V2 extensions. If your extension hasn't updated to V3, it'll keep getting disabled. The fix: check the extension's support page for a V3 version. If there isn't one, you're stuck — find an alternative.

Variation B: Extension says "This extension may have been corrupted"

That's a different message. It means the extension's hash on disk doesn't match the one in the store. Usually caused by a failing hard drive or a write error during update. Run chkdsk /f on Windows or fsck on macOS to rule out disk issues. Then reinstall the extension.

Variation C: Only one profile is affected

If the extension works in another Chrome profile but not yours, the profile's preferences file is corrupted. Create a new profile and move your bookmarks over. Don't bother fixing the old profile — it's not worth the time.

Prevention — stop this from happening again

  • Only install from official stores. Sideloaded extensions are the #1 cause of corruption.
  • Keep Chrome/Edge updated. Old browsers don't know about new security checks.
  • Don't install extensions from pop-up messages. If a website tells you "Your browser needs an update — click here to install," that's malware. Close the tab.
  • Check permissions periodically. Go to chrome://extensions and click "Details" on each extension. If one asks for access to "all data on all websites" and doesn't need it, uninstall it.

That's it. Remove, reinstall, check policies — 95% of cases are solved in under 5 minutes. If none of this worked, the extension itself is probably abandoned and won't be fixed. Find a newer replacement.

Was this solution helpful?