Your Chrome Extensions Broke. Here's How to Fix Every Scenario.

Your Chrome extensions stopped working. Some show grayed-out icons. Others have disappeared from the toolbar entirely. The extension page says "This extension may have been corrupted," or gives no error at all while silently failing.

Full disclosure: I built these tools as part of Zovo, a collection of Chrome extensions I maintain at zovo.one. Take my perspective accordingly.

I maintain 16 Chrome extensions, so I have hit every flavor of extension breakage firsthand. The fix depends on why they broke, and Chrome 134 has at least six distinct failure modes.

Quick Diagnostic

Open chrome://extensions and check each broken extension:

Symptom	Likely Cause
"This extension is no longer supported"	MV2 deprecation
Toggle grayed out, cannot enable	Chrome policy block
"Errors" button visible	Code error or conflict
Icon missing from toolbar	Toolbar overflow (not broken)
All extensions disabled at once	Profile corruption
Extension works intermittently	Conflict with another extension

If an extension is enabled but its icon is missing, click the puzzle piece icon in the toolbar, find the extension, and click the pin icon. Chrome 134 unpins extensions during certain update scenarios. The extension is still running.

MV3 Migration Issues

This is the single biggest source of breakage in Chrome 134. Google's Manifest V3 replaces persistent background pages with service workers, swaps the webRequest API for declarativeNetRequest, and bans remote code execution.

The practical impact: background scripts now terminate after inactivity, ad blockers are limited to 330,000 static rules, and extensions cannot download and execute JavaScript from external servers.

Check if an extension is MV2 or MV3: Go to chrome://extensions, enable Developer mode (toggle top-right). Each card shows the manifest version.

What to do about disabled MV2 extensions:

1. Search the Chrome Web Store for an updated version. The developer may have published an MV3 release under the same or a similar name.
2. Check the last update date on the store listing. If it predates 2025, the extension is likely abandoned.
3. As a stopgap, you can re-enable MV2 extensions through the ExtensionManifestV2Availability enterprise policy set to 2. This is temporary. Google will remove MV2 support entirely.

For ad blockers specifically: uBlock Origin Lite is the MV3 replacement for uBlock Origin. AdGuard and Ghostery have also shipped MV3 versions.

Extension Conflicts

Two extensions modifying the same pages, intercepting the same requests, or registering the same keyboard shortcuts will interfere with each other.

The fastest diagnostic: disable all extensions, enable only the broken one, and test. If it works alone, re-enable others one at a time until it breaks again. The last enabled extension is the conflict.

Common patterns I have seen:

• Two ad blockers intercepting the same network requests
• Multiple new tab page extensions (only one can win)
• Two password managers fighting over the same login forms
• VPN extension plus proxy extension both trying to route traffic

Profile Corruption

If all your extensions disabled simultaneously with no explanation, you probably have profile corruption. This happens when Chrome crashes during a write, when disk space runs out, or when antivirus software quarantines profile files.

Fix 1: Clear extension state.

# macOS
rm -rf ~/Library/Application\ Support/Google/Chrome/Default/Extension\ State/

# Windows (PowerShell)
Remove-Item -Recurse "$env:LOCALAPPDATA\Google\Chrome\User Data\Default\Extension State"

Restart Chrome. It rebuilds extension state from installed files.

Fix 2: Reset Chrome settings. Go to chrome://settings/reset and click "Restore settings to their original defaults." This resets startup page, search engine, and pinned tabs, and disables all extensions, but does not delete bookmarks, history, or passwords. Re-enable extensions one at a time.

Fix 3: Create a new profile. Click your profile icon, click "Add," sign in with your Google account. Chrome Sync restores extensions, bookmarks, and passwords to the fresh profile.

Chrome Policy Blocks

Enterprise-managed Chrome installations and some security software block extensions through policies that override your preferences.

Open chrome://policy and look for:

• ExtensionInstallBlocklist (extensions explicitly blocked)
• ExtensionInstallAllowlist (only these extensions allowed)
• ExtensionManifestV2Availability (controls MV2 extensions)

On a personal computer, you can remove unwanted policies:

# macOS: remove all Chrome policies
defaults delete com.google.Chrome

On Windows, open Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome. Delete unwanted keys. Also check HKEY_CURRENT_USER\SOFTWARE\Policies\Google\Chrome.

On managed enterprise machines, contact your IT admin to get the extension allowlisted.

Developer Mode Debugging

When nothing else works, Developer mode gives you the actual error.

1. Go to chrome://extensions, toggle Developer mode on.
2. Click "Errors" on the broken extension.
3. Common errors and fixes:

Error	Fix
chrome.webRequest is undefined	Extension needs MV3 update
Service worker registration failed	Clear Extension State directory
Permissions not granted	Remove and reinstall
net::ERR_BLOCKED_BY_CLIENT	Another extension is blocking requests

For MV3 extensions, click the "service worker" link on the extension card to open DevTools. Check the Console for errors and the Network tab for failed requests.

Reinstall vs. Repair

Repair in place when the extension has complex settings or local data you do not want to lose. Click "Repair" on the extension card if the button appears.

Clean reinstall when you see "This extension may have been corrupted." Remove the extension, clear remnants from the Extensions directory, restart Chrome, and reinstall from the Chrome Web Store.

Before removing, back up extension data:

# macOS
cp -r ~/Library/Application\ Support/Google/Chrome/Default/Local\ Extension\ Settings/EXTENSION_ID ~/Desktop/extension-backup/

Restore the directory after reinstalling to recover your settings.

I build Chrome extensions at zovo.one. All 16 are free, open source, and collect zero data.