Open chrome://extensions, find the extension, and flip its toggle off and then on again. That restarts the background service worker, which is what has actually stopped in the majority of cases where a popup opens blank or a button does nothing. If the toggle does not bring it back, quit Chrome fully and reopen it before trying anything else.
Do not reinstall yet. Reinstalling is the most commonly given advice and one of the least likely to help, and it throws away the extension's settings on the way.
An extension that has stopped working is not one problem. It is at least six problems that look identical from the toolbar, and the fix for one does nothing for the others. The fastest route is to match what you actually see on screen, so start with the symptom that fits.
Below the router the guide is ordered by cost, cheap checks first: the six step diagnostic, then the specific failure patterns, then repairing Chrome itself.
Run these in order. Each one costs less than the one after it, and each one rules out a whole category of cause. Stop as soon as the extension comes back.
Open chrome://extensions and flip the extension's toggle off and then on again. That restarts its background service worker, which is the most common reason a popup opens empty. Extensions you loaded from a folder yourself also get a reload icon in Developer mode.
Closing the last window is not the same as quitting. On macOS use Chrome, Quit Google Chrome. On Windows, confirm no Chrome process survives in Task Manager. A leftover process from the last update keeps serving the broken state.
Turn on Developer mode in the top right of chrome://extensions. The card then shows the extension ID, its version, and an Errors button if the extension threw one. A banner saying the extension is no longer supported means Chrome retired it, not that it broke. A Repair button means Chrome believes the files on disk were altered.
Click your profile avatar, choose Add, and create a local profile without signing in. Install only the broken extension there. If it works, the fault is in your main profile and not in the extension.
Two extensions that inject scripts into the same page, or that both claim the new tab page or the same shortcut, will break each other. Turn everything else off, confirm the extension works alone, then re-enable the others one at a time and test after each.
Open chrome://policy and filter for Extension. Entries such as ExtensionInstallBlocklist, ExtensionInstallAllowlist, ExtensionSettings or ExtensionManifestV2Availability mean something outside Chrome decides what you may run. On a work machine that is device management. On a personal machine it is security software or something you did not install on purpose.
If Chrome has given you wording, use it. The exact string narrows the cause faster than any amount of general troubleshooting, because each one comes from a different part of the browser. Find yours in the left column.
| What Chrome says | What it actually means, and what to do |
|---|---|
| This extension may have been corrupted | The files on disk no longer match the signed manifest hash. Click Repair on the extension card. Full section below, including what to do when Repair will not stick. |
| This extension is not from the Chrome Web Store and may have been added without your knowledge | A sideloaded extension, installed by an external program rather than by you through the store. If you did not install it deliberately, remove it and scan the machine. If you did, reinstall the store version. |
| This extension is no longer supported. Chrome recommends that you remove it | Manifest V2 retirement. Nothing is broken and nothing will fix it. See Extensions Chrome retired with Manifest V2. |
| This extension violates the Chrome Web Store policy | Google removed the listing after publication. The extension stays disabled and cannot be reinstalled. Find a maintained replacement. |
| This extension contains malware | Google flagged the extension and Chrome disabled it deliberately. Remove it, change any password you typed while it was installed, and do not attempt to re-enable it. |
| This extension is managed and cannot be removed or disabled | Force installed by policy on a managed device. Check chrome://policy for ExtensionInstallForcelist. Only whoever manages the device can change this. |
| Blocked by admin | An ExtensionInstallBlocklist or allowlist policy is refusing the install. Same place, chrome://policy. Send the extension ID to your IT team. |
| Failed to load extension / Manifest file is missing or unreadable | Only appears when loading an unpacked folder in Developer mode. You pointed Chrome at the wrong folder: it needs the folder that directly contains manifest.json, not its parent and not a zip. |
| Package is invalid: CRX_HEADER_INVALID | The downloaded package is truncated or was modified in transit, commonly by antivirus or a proxy that inspects downloads. Clear the cache, retry, then check the security software. |
| CRX_REQUIRED_PROOF_MISSING | You are installing a .crx file that Chrome cannot verify came from the Chrome Web Store. Install from the store listing instead. |
| NETWORK_FAILED | The install download was interrupted or blocked. Almost always antivirus, a VPN, or a filter sitting between Chrome and Google's servers. See The Chrome Web Store will not load. |
| An error has occurred. Please try again later. | The store's generic failure. Retry in a fresh profile, then on a different network, to separate a store outage from something local. |
On chrome://extensions with Developer mode on, a Manifest V3 extension normally shows its service worker as inactive. Chrome shuts idle service workers down on purpose to save memory and starts them again on demand. That line worries people constantly and almost never indicates a fault.
This is the failure generic troubleshooting articles never cover, and it hits business extensions hardest. Sales intelligence, prospecting, SEO and IT asset extensions of the kind published by vendors like ZoomInfo, Salesloft, Ahrefs or Lansweeper are not self contained software. They are thin clients: the extension is a panel, and the data comes from the vendor's servers over an authenticated API call. That gives them failure modes an ad blocker or a tab manager does not have.
The tell is that the extension is enabled and it opens, but you get an empty panel, a spinner that never resolves, a login screen you have already passed, or a message that your account cannot be verified. Chrome is fine. The session behind it is not.
Most of these extensions borrow the session from the vendor's own website rather than holding a separate login. When that session expires, or single sign on rotates a token, the extension keeps its stale cookie and every API call comes back rejected, usually with no message at all. Open the vendor's web app in a normal tab, sign out fully, sign back in, confirm the web app works, then reload the page you were using the extension on. Sign out from the vendor's app rather than from your identity provider, so the vendor issues a genuinely new session.
When the extension injects a panel into a page on another site and calls the vendor's API from inside it, that is a cross site request. If you have tightened cookie settings, installed a privacy extension, or your organisation pushed a stricter default, the session cookie is never attached and the API answers as if you were a stranger. Open chrome://settings/cookies and add the vendor's domain to the sites that are always allowed to use cookies, normally the same domain as the web app you log in to. Keep the exception rather than turning the global block off.
On a managed device an extension can be installed and visible while still being throttled by policy. Open chrome://policy and search for Extension. An ExtensionInstallBlocklist entry containing the extension's ID, an ExtensionSettings block restricting which sites it may run on, or a URLBlocklist entry covering the vendor's API domain all produce this symptom: present, opens, can do nothing. You cannot remove policies on a device your employer manages, so send the extension ID and a screenshot of the policy row to your IT team with the business reason.
Right click the extension icon and choose Options, or open its Details on chrome://extensions and follow the Extension options link. Most business extensions show their account or licence state there: which account is connected, which workspace, whether a seat is assigned. Paid extensions are commonly gated on a seat in the vendor's plan, and a seat that was reassigned or a subscription that lapsed leaves the extension installed and inert. Nothing you do in Chrome fixes a billing state.
Collect three things and the ticket resolves faster: the extension ID and version from chrome://extensions with Developer mode on, the output of the Errors button if there is one, and the browser console from the page where it fails. Open the console with Ctrl+Shift+J, or Cmd+Option+J on macOS. A request returning 401 confirms a session problem rather than a broken extension.
This is a real Chrome error string and it means something specific. Chrome ships extensions with a signed record of what every file should hash to, and checks the files on disk against that record before running them. If one byte differs, Chrome cannot tell an innocent problem from a malicious one, so it takes the safe option and disables the extension. A related message, that the extension is invalid, comes from the same family of integrity checks.
The realistic causes, in rough order of how often they are the answer:
Go to chrome://extensions and click Repair on the affected extension's card. Chrome downloads a fresh copy from the Chrome Web Store, verifies it, and re-enables the extension. Your settings survive, because Repair replaces the program files and not the extension's storage.
If Repair fails, or the extension returns to the corrupted state within a day, stop repairing it. Reinstall, then check your antivirus quarantine log for entries pointing at the Chrome profile folder, and add the Chrome user data directory to its exclusions if your security team allows it. Repeated corruption is a symptom of another program.
There is a case the standard advice misses entirely, and it is worth recognising because no amount of local troubleshooting resolves it. If exactly one extension reports corruption, Repair appears to succeed and then the same extension fails again, and every other extension you have is healthy, the problem is probably not on your machine. Repair re-downloads the same package from the Chrome Web Store, so if the version the vendor published is itself broken or incompatible with your Chrome build, you will loop indefinitely: repair, work briefly or not at all, corrupt again.
Three things separate this from local corruption:
If all three hold, go to the vendor rather than to Chrome. Check the extension's listing in the Chrome Web Store for a recent version bump, read the Support tab on the listing, and look for the vendor's own issue tracker or status page. When a vendor ships a bad build, the reports cluster within a day or two and the fix is a version the vendor has to publish. Widely used developer and SEO toolbars have gone through exactly this, where the corrupted-extension warning turned out to be a compatibility break between the published package and a new Chrome release rather than anything users could repair.
The one useful thing to do meanwhile is stop Chrome silently re-enabling a version you know is broken: leave the extension disabled rather than removed, so its settings survive, and re-enable it once the vendor confirms a fixed version has shipped.
If several extensions report corruption at once and none repair successfully, treat it as a disk problem. Check the drive's health and free space before reinstalling, otherwise you will corrupt the fresh copies too.
Chrome updates itself quietly and applies the new version at the next restart, so the machine that worked when you shut it down can be broken when you open it, with nothing you did in between. Two different mechanisms produce that, and they need different responses.
Open chrome://settings/help. That page reports the version you are on and finishes any update that was waiting, which is worth doing before anything else because a half-applied update is its own failure mode: the new binary is on disk, the running process is the old one, and extensions load against a mismatched pair. If it tells you Chrome is up to date and offers a Relaunch button, take it.
chrome://version gives you the full build string and, importantly, the Profile Path. Note that path down. You need it for anything involving the profile folder, and on a machine with several profiles it is the only reliable way to know which one you are actually in.
Some breakage after an update is permanent and intended. Chrome removes platform capabilities on a schedule, and an extension relying on a removed one stops working at the version where it goes. The clearest current example is the Manifest V2 to V3 transition, covered in its own section below. The signature is that the extension card carries a notice rather than an error, and Repair and reinstall both change nothing.
Extensions belong to a profile, and much of what a profile knows arrives over Chrome Sync. When sync is unhealthy the extension is often fine while its settings and its signed-in state are not, which reads from the toolbar as a broken extension.
chrome://settings/people and sign back in to resume it.To check rather than guess, open chrome://sync-internals and look at the Type Info tab. The Extensions and Extension settings rows show whether the server actually holds anything. A zero entity count against a profile you expected to be populated is your answer.
If the same update also took your bookmarks or your bookmarks bar with it, that is a separate set of causes with a separate set of fixes, including a backup file that Chrome overwrites shortly after each launch. See Chrome bookmarks disappeared: which of the four problems you have, and close Chrome before you go looking for that backup.
This is a different problem from a broken extension. Here the store at chromewebstore.google.com hangs, shows an empty grid, or fails outright, and installs never start, while extensions you already have keep working. The cause is almost always something between Chrome and Google's servers.
chrome://policy and search for Extension. An allowlist policy means only approved extensions can install, and the store looks broken when you try anything else.clients2.google.com as well as the store domain. A pi-hole style blocklist, a VPN with its own resolver, or a hosts file entry catching either host breaks installs while leaving normal browsing intact.sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder. On Windows run ipconfig /flushdns from an elevated prompt. Chrome keeps its own cache at chrome://net-internals/#dns, where Clear host cache does the same job.chrome://settings/clearBrowserData.Fastest way to split the problem in two: open the store in a fresh Chrome profile, then on a different network such as a phone hotspot. Working in a new profile points at your profile or an extension. Working on another network points at your network, DNS, or employer.
Check whether the extension is actually gone or merely out of sight. The first two explanations below account for most cases.
The icon is unpinned, not missing. Click the puzzle piece icon to the right of the address bar. Everything installed is listed there, and the pin next to the extension puts it back on the toolbar. Chrome unpins icons during some updates without telling you, and the extension has been running the whole time.
You are in a different Chrome profile. Extensions belong to a profile, not to the browser. If Chrome opened your second profile, a work profile, or a guest window, your extensions genuinely are not there. Check the avatar in the top right. Guest windows never load extensions at all, by design.
Sync has not finished, or is not on. On a new machine or a fresh profile, extensions arrive through Chrome Sync some time after bookmarks do. Check chrome://settings/syncSetup and confirm Extensions is included.
Everything went at once. If every extension disabled or vanished simultaneously, stop treating it as an extension problem. That pattern points at profile damage, a policy from device management, or security software that swept the profile directory. Test a fresh profile, then check chrome://policy.
Some extensions did not break. Chrome stopped running them. Extensions are built against a platform specification called a manifest, and Chrome has phased out the older Manifest V2 generation in favour of Manifest V3. Extensions never rewritten for V3 get disabled, and no amount of repairing, reinstalling or profile resetting brings them back, because there is nothing left on Chrome's side to run them with.
You can recognise this case immediately: the card on chrome://extensions carries a notice that the extension is no longer supported, and Developer mode shows the manifest version. There is no error, because nothing failed. Your options are narrow:
Enterprise policy has historically kept specific Manifest V2 extensions running past the point where consumer Chrome disables them, through the ExtensionManifestV2Availability policy. That is controlled by your IT department, not by you.
If extensions break repeatedly across profiles, if Chrome throws profile errors on startup, or if it asks you to sign in again every launch, the browser and not the extension needs attention. Escalate in this order, because each step costs more than the last.
| Step | What it does | What you lose |
|---|---|---|
Reset settings at chrome://settings/reset |
Restores the startup page, new tab page, search engine and pinned tabs, disables extensions, clears temporary site data | Nothing permanent. Bookmarks, history and passwords are kept |
| Create a new profile | Gives you a clean profile directory, with your data restored through Chrome Sync | Anything stored locally and never synced |
| Reinstall Chrome | Replaces the browser's program files, which the steps above do not touch | Nothing, unless you delete the user data directory during uninstall |
Reinstalling Chrome over an existing installation leaves your profile directory in place, so it repairs the application without touching your data. If a corrupted profile is the actual problem, reinstalling will not help and a new profile will.
Two phrasings reach this page regularly and mean slightly different things. The German "chrome reparieren", repair Chrome, is the section above: reset settings, then a new profile, then a reinstall over the top. The Russian "не устанавливаются расширения в хром", extensions will not install in Chrome, is usually not a Chrome fault at all and belongs in the Chrome Web Store section: a network or DNS block, a policy allowlist, or an employer firewall standing between the browser and Google's extension hosts.
Why are my Chrome extensions not working?
Five different causes, each with a different fix: a stalled service worker, which a toggle off and on clears; files that failed Chrome's integrity check, which Repair fixes; a policy on a managed device; an expired login at the vendor behind the extension; or an extension built for Manifest V2 that Chrome no longer runs.
Why do my Chrome extensions keep disappearing?
Check the puzzle piece icon next to the address bar first, because unpinned is not uninstalled, then confirm which profile you are in. If they keep being removed for real, check chrome://policy and your antivirus quarantine log.
Why is my ZoomInfo extension not working?
We do not publish that extension, but extensions in that category share a failure profile. They are thin clients over a vendor API, so they break when the session expires, when third party cookies are blocked for the vendor's domain, when a workplace policy restricts them, or when the paid seat lapses. Sign out and back in to the vendor's web app first.
What does 'This extension may have been corrupted' mean?
The files on disk no longer match the signed record of what they should contain, so Chrome disabled the extension rather than run code it cannot verify. Usual causes are antivirus quarantine, an interrupted update, or disk errors. Click Repair on the extension card at chrome://extensions.
Why is the Chrome Web Store not working?
A store that will not load is a network or policy problem, not an extension problem: a corporate firewall, a Chrome policy allowlist, DNS blocking of clients2.google.com, a stale DNS cache, an ad blocker, or Chrome's cache. Test it in a fresh profile, then on a different network.
How do I repair Chrome without losing my bookmarks and passwords?
Start with chrome://settings/reset and Restore settings to their original defaults, which keeps bookmarks, history and saved passwords. If that is not enough, create a new profile, then reinstall Chrome, which leaves your profile directory intact.
Chrome says the extension is invalid. What does that mean?
Same integrity checking as the corrupted extension message: Chrome could not validate the package, so it refuses to load it. For a store install, use Repair, then remove and reinstall. For an unpacked folder, the manifest is malformed or a file it references is missing.
Why did my Chrome extensions stop working after an update?
Either the update is only half applied, or the update deliberately retired the extension. Open chrome://settings/help, let it finish, and take the Relaunch button. If the extension card shows a notice saying it is no longer supported rather than an error, Chrome removed the platform feature it depended on and no repair or reinstall will bring it back.
Chrome keeps saying an extension is corrupted even after I click Repair. What should I do?
If several extensions are affected, suspect antivirus or the disk, and check the quarantine log. If only one is affected and it also fails in a brand new profile and on another machine, the published version is probably broken on the vendor's side. Repair just re-downloads the same package, so it will loop. Leave the extension disabled rather than removing it, and watch the listing for a new version.
What does 'This extension is not from the Chrome Web Store' mean?
It was sideloaded, meaning some program on the machine installed it rather than you installing it from the store. If you did not add it on purpose, remove it and scan the machine. If you did add it on purpose, install the Chrome Web Store version instead so Chrome can verify and update it.
My extension shows 'Service worker (Inactive)'. Is it broken?
No. Chrome shuts down idle Manifest V3 service workers to save memory and restarts them when they are needed. Inactive is the normal resting state and is not an error.