Chrome extension stopped working after an update? Seven causes and the fix for each

Extensions rarely break in a dramatic way. More often the icon goes grey, the toolbar button vanishes, or the extension sits there looking normal and simply stops doing its job. Chrome is usually telling you exactly why — in a place most people never look.
Below are the seven causes we run into most, in the order worth checking them, with how to recognise each one and what to do about it. The first three cover most cases.
Start here: read the extension's card
Type chrome://extensions into the address bar and find the extension. Its card shows whether it is switched on, and Chrome writes the reason underneath when it has turned something off. Clicking Details shows its permissions and site access. Keep this page open; most of the fixes below start from it.
1. It asked for new permissions and Chrome switched it off
When an update asks for more access than the version you approved — reading data on all sites, for example — Chrome disables the extension until you agree. You will see a message that it was disabled because it requires new permissions, sometimes with a badge on the puzzle-piece menu.
Fix: read the new permissions first. A grammar checker asking to read every page is expected; a calculator asking for the same is a reason to stop. If they make sense, accept them and switch the extension back on. If they do not, remove it — this is exactly the moment a sold or hijacked extension reveals itself. Our safety checklist helps with the judgement call.
2. Its site access is set to "on click" or a short list
Chrome lets you limit where an extension can run. Right-click its toolbar icon, or open Details, and look at site access: on click, on specific sites, or on all sites. If it is set to on click, the extension does nothing on a page until you click its icon — easy to set once for privacy and forget.
Fix: for extensions that need to act on every page (ad blockers, dark mode, password managers), choose on all sites. For everything else, on specific sites is a good middle ground — add the handful of domains where you actually use it.
3. Another extension is getting in the way
Two ad blockers, two dark-mode tools or two extensions that both rewrite the same page will fight. The symptom is an extension that works on some sites and not others, or worked until you installed something new.
Fix: create a fresh Chrome profile (profile icon → Add), install only the troubled extension, and test the same page. If it works there, the problem is in your main profile. Switch other extensions off one at a time — starting with the most recent — until it starts working again. Our guide to Chrome profiles explains profiles if you have not used them.
4. It was built for Manifest V2
Older extensions built on Manifest V2 no longer run in Chrome. Their cards say the extension is no longer supported, and there is no setting that brings them back.
Fix: check whether the developer has released a Manifest V3 version — sometimes it is a separate listing, as with uBlock Origin Lite. If not, find a replacement. Our Manifest V3 explainer covers what changed, and every extension page here lists alternatives.
5. The Chrome Web Store removed it
When Google finds that an extension contains malware or breaks Web Store policy, it takes the listing down and Chrome disables installed copies remotely. The card says so in plain words.
Fix: remove it, do not try to sideload it back, and change any passwords you typed on sites while it was installed if it had access to all your data. Then run through the safety checklist for the rest of your list.
6. Its files are corrupted
If files on disk change underneath an extension — after a crash, a disk clean-up tool or a sync problem — Chrome notices and shows a corruption warning with a Repair button.
Fix: click Repair. Chrome downloads a fresh copy from the Web Store. Your settings stored in the browser usually survive a repair, but export anything important first if the extension offers an export.
7. Your work or school manages Chrome
On a managed computer or profile, an administrator can block extensions, force-install them or limit what they can access. Chrome says it is managed by your organisation at the bottom of the menu, and affected extensions show a building icon or a note.
Fix: none from your side — ask your IT team. Keep personal extensions in a personal Chrome profile signed into a personal account, and the work policy will not touch them.
When the card shows nothing wrong
Sometimes the extension is switched on, has access, and still does nothing. Three checks are worth a minute:
- Look for errors. Switch on Developer mode at the top right of
chrome://extensions. An Errors button appears on cards that have logged problems; the message often names the page or feature that failed. Paste it into the developer's support page. - Toggle it off and on. Manifest V3 extensions run a background service worker that Chrome stops when idle. Switching the extension off and on restarts it cleanly, and fixes more than it should.
- Restart Chrome after updates. If Chrome shows an update waiting, relaunch. Extensions updated while an old browser version is still running can behave oddly until then.
Before you reinstall
Removing an extension deletes the data it kept on your computer — saved sessions, notes, custom rules. Reinstalling from the Web Store gives you a clean copy without any of it. If the extension has an export or backup option (tab managers like OneTab and Session Buddy do), use it first. Our guide to moving extensions to a new computer explains which data survives and which does not.
Frequently asked questions
Why did Chrome disable my extension?
The usual reasons are an update that asked for new permissions, an extension built on the retired Manifest V2, removal from the Chrome Web Store for a policy or malware problem, corrupted files, or a policy set by your organisation. The extension's card at chrome://extensions says which.
How do I turn a disabled Chrome extension back on?
Open chrome://extensions and switch it on. If it was disabled for new permissions, Chrome asks you to accept them first. Extensions removed for malware or built on Manifest V2 cannot be turned back on.
Will reinstalling an extension delete my data?
Usually, yes. Data the extension stored on your computer is removed with it. Settings it saved to Chrome Sync may come back, but export anything important before you remove it.
How do I see an extension's errors?
Switch on Developer mode at chrome://extensions. Extensions that logged problems show an Errors button with the messages.
