15 min read 3520 words By Michael Lip
| Written by Michael Lip | Last tested: March 2026 | Chrome 134 stable |
Last verified: March 2026 – All steps tested on Chrome 134 (latest stable). Extension compatibility data verified against Chrome Web Store.
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 worse, gives no error at all while silently failing.
When Chrome extensions are not working, the fix depends on why they broke. Chrome 134 enforces Manifest V3 (MV3) as the required extension platform, and extensions that have not migrated from the older Manifest V2 architecture are being actively disabled. But MV3 migration is only one of at least six distinct causes for extension failures, and each requires a different repair approach.
This guide walks through every documented reason extensions stop working in Chrome 134, gives you targeted fixes for each scenario, and shows you how to diagnose the root cause so you apply the right fix on the first attempt.
Before applying fixes, determine which category your problem falls into. Open chrome://extensions and check each broken extension for these indicators:
| Symptom | Likely Cause | Jump To |
|---|---|---|
| “This extension is no longer supported” banner | MV2 deprecation | MV2 to MV3 Migration |
| Extension toggle is grayed out, cannot enable | Chrome policy block | Chrome Policy Blocks |
| “Errors” button visible on extension card | Code error or conflict | Developer Mode Debugging |
| Extension icon missing from toolbar | Toolbar overflow or disabled | Quick fixes below |
| All extensions disabled simultaneously | Profile corruption or update | Corrupt Chrome Profile |
| Extension works intermittently | Memory or conflict issue | Extension Conflicts |
If an extension is enabled on chrome://extensions but its icon does not appear in the toolbar:
Chrome 134 unpins extensions from the toolbar during certain update scenarios. This is not a malfunction – the extension is still running, its icon was just removed from the visible toolbar area.
The transition from Manifest V2 to Manifest V3 is the single largest source of extension breakage in Chrome 134. Google began this migration in 2023 and has progressively disabled MV2 extensions through a phased rollout documented on the Chrome Extensions developer blog.
MV3 replaces persistent background pages with service workers, changes how content scripts inject code, and modifies the permissions model. Key changes affecting end users:
chrome://extensionsOption 1: Find an MV3 alternative. Many popular extensions have released MV3 versions. Search the Chrome Web Store for the extension name – the developer may have published an updated version under the same name or a slightly different one.
Option 2: Wait for the developer to update. Check the extension’s Chrome Web Store listing for recent reviews and update dates. If the last update was before 2025, the extension is likely abandoned and will not receive an MV3 update.
Option 3: Temporarily re-enable MV2 extensions. Chrome 134 still allows MV2 extensions to be force-enabled through enterprise policies (see Chrome Policy Blocks section). This is a stopgap measure – Google will eventually remove MV2 support entirely.
Ad blockers were the most affected extension category in the MV2-to-MV3 transition. The declarativeNetRequest API limits that replaced webRequest reduced the number of filter rules available. uBlock Origin responded by releasing “uBlock Origin Lite” as its MV3 version, while the original uBlock Origin remains MV2-only.
If your ad blocker stopped working, install the MV3 version:
Two or more extensions can interfere with each other when they modify the same web pages, intercept the same network requests, or register the same keyboard shortcuts.
The fastest way to find a conflict is to disable all extensions and re-enable them one at a time:
chrome://extensionsExtensions that inject JavaScript into web pages (content scripts) can collide. If two extensions modify the same DOM elements, both may break. Check chrome://extensions and click “Details” on each extension to see which URLs they have permission to access. Extensions with broad permissions like “All sites” are more likely to conflict.
Profile corruption can disable all extensions simultaneously. This happens when Chrome crashes during a profile write operation, when disk space runs out while Chrome is updating extension data, or when antivirus software quarantines files inside the Chrome profile directory.
# macOS: Remove extension state (keeps extensions installed)
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 after removing this directory. Chrome will rebuild the extension state from the installed extension files.
Go to chrome://settings/content and scroll to the bottom. Click “Additional content settings” and review each permission category. Corrupted permission data can prevent extensions from accessing the resources they need.
Alternatively, reset all settings: Go to chrome://settings/reset and click “Restore settings to their original defaults.” This resets the startup page, new tab page, search engine, and pinned tabs, disables all extensions, and clears temporary data. It does not delete bookmarks, history, or saved passwords.
If the corruption is severe, create a fresh profile:
The old corrupted profile remains on disk. You can manually copy specific files from it if needed.
Enterprise-managed Chrome installations and some security software can block extensions through Chrome policies. These policies override user preferences and cannot be changed through Chrome’s settings UI.
Open chrome://policy in Chrome. This page shows all active policies affecting your browser. Look for these extension-related policies:
ExtensionInstallBlocklist – Extensions explicitly blocked by policyExtensionInstallAllowlist – Only these extensions are allowedExtensionSettings – Granular per-extension policy controlsExtensionManifestV2Availability – Controls whether MV2 extensions can runIf you see policies listed here that you did not set, your IT department, antivirus software, or a browser hijacker has installed them.
On macOS:
# List all Chrome policies
defaults read com.google.Chrome
# Remove a specific policy
defaults delete com.google.Chrome ExtensionInstallBlocklist
# Remove all Chrome policies
defaults delete com.google.Chrome
On Windows:
# Open Registry Editor (regedit)
# Navigate to: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome
# Delete unwanted policy keys
# Also check: HKEY_CURRENT_USER\SOFTWARE\Policies\Google\Chrome
On Linux:
# Chrome policies are stored in:
# /etc/opt/chrome/policies/managed/
# /etc/opt/chrome/policies/recommended/
# Remove or edit the JSON files in these directories
sudo ls /etc/opt/chrome/policies/managed/
After removing policies, restart Chrome and check chrome://policy again to verify they are gone.
If your computer is managed by an organization, you typically cannot remove Chrome policies yourself. Contact your IT administrator and request that the specific extension you need be added to the allowlist. Provide the extension’s Chrome Web Store URL and explain the business need.
When an individual extension breaks, you need to decide between repairing it in place or doing a clean reinstall.
Repair in place when:
Clean reinstall when:
chrome://extensionschrome://extensions# macOS: Remove leftover extension data
find ~/Library/Application\ Support/Google/Chrome/Default/Extensions/ -name "EXTENSION_ID" -type d -exec rm -rf {} +
# Replace EXTENSION_ID with the actual extension ID from chrome://extensions
Some extensions store data in Chrome’s local storage. Before removing the extension:
chrome://extensions and find the extension ID# macOS: Back up extension data before reinstall
cp -r ~/Library/Application\ Support/Google/Chrome/Default/Local\ Extension\ Settings/EXTENSION_ID ~/Desktop/extension-backup/
After reinstalling, restore the backed-up data directory.
When standard fixes do not resolve the issue, Developer mode provides detailed error information that pinpoints the exact cause.
chrome://extensionsClick the “Errors” button on the broken extension. Chrome displays a log of runtime errors with:
Common error patterns and their fixes:
| Error Message | Cause | Fix |
|---|---|---|
Uncaught TypeError: chrome.webRequest is undefined |
MV2 API used in MV3 | Update extension or find MV3 alternative |
Service worker registration failed |
Corrupt service worker cache | Clear extension state (see Fix 1 above) |
Permissions not granted |
Missing permissions after update | Remove and reinstall extension |
net::ERR_BLOCKED_BY_CLIENT |
Another extension blocking requests | Disable other extensions to find conflict |
For MV3 extensions, the service worker is the background process:
If an extension’s Chrome Web Store version is broken but the developer has published a fix:
chrome://extensions and enable Developer modeThis approach is useful for testing beta versions or patches before they reach the Chrome Web Store. Documentation on loading unpacked extensions is available at developer.chrome.com.
Chrome 134 introduced several changes that directly affect extension behavior. Understanding these changes helps distinguish between bugs and intentional platform changes.
Chrome 134 is in Phase 3 of the MV2 deprecation timeline. In this phase:
ExtensionManifestV2Availability set to 2)Source: Chrome MV2 deprecation timeline
Chrome 134 modified how extensions interact with the Side Panel API. Extensions that used chrome.sidePanel may need to update their permissions in the manifest. If a side panel extension stopped working, check if the developer has released an update.
Chrome 134 extended the service worker idle timeout from 30 seconds to 5 minutes for extensions that register active alarms or maintain open ports. This should fix extensions that previously lost state due to premature service worker termination.
However, extensions that rely on the previous 30-second timeout for cleanup operations may behave differently. If an extension’s memory usage has increased since updating to Chrome 134, this lifetime change may be the cause.
Chrome 134 enforces stricter Content Security Policy (CSP) for extension pages. Extensions that loaded external fonts, images, or scripts in their popup or options pages may break. The fix is on the developer side – they need to bundle these resources locally or update their CSP declarations.
Chrome updates can disable extensions for several reasons: MV2 deprecation (extensions using the old Manifest V2 platform are being phased out), profile corruption during the update process, or policy changes. Go to chrome://extensions to check each extension’s status. If they show an MV2 deprecation warning, search for MV3 alternatives on the Chrome Web Store. If no warning appears, try the profile repair steps in this guide. Source: Chrome Extensions developer documentation
Grayed-out extensions are typically blocked by Chrome policies. Open chrome://policy to check for active policies. On personal computers, you can remove unwanted policies through the system registry (Windows), defaults command (macOS), or policy files (Linux). On managed enterprise computers, contact your IT administrator to request the extension be allowlisted. Source: Chrome Enterprise policy list
The original uBlock Origin (MV2) is being disabled in Chrome 134 as part of the MV2 deprecation. The developer released uBlock Origin Lite, an MV3-compatible version, which works in Chrome 134 but has fewer filter capabilities due to the declarativeNetRequest API limitations. For maximum ad blocking in Chrome, use uBlock Origin Lite or switch to AdGuard’s MV3 extension. Source: Chrome Web Store
Yes, temporarily. On personal computers, you can set the ExtensionManifestV2Availability Chrome policy to value 2, which re-enables MV2 extensions. However, Google will eventually remove this override. A more permanent solution is to find an MV3-compatible replacement or switch to a browser that still supports MV2 (Firefox does not have the same deprecation timeline).
Open Chrome’s Task Manager (Shift+Esc on Windows/Linux, Window > Task Manager on macOS). Sort by Memory or CPU usage. Extensions with runaway memory or CPU consumption are likely causing stability issues. You can also check chrome://crashes for crash reports that reference specific extension IDs in the crash signature. Disable suspected extensions one at a time and test stability between each change. Source: Chromium crash reports documentation