Chrome Extension Keeps Getting Disabled After an Update? (2026)

You opened Chrome this morning and the toolbar icon was gone. The extension you use every day is sitting greyed-out at chrome://extensions with a line of red text underneath, and flipping the toggle either does nothing or it switches itself back off the next time Chrome restarts. Nothing you did changed. Chrome updated overnight and decided your extension was no longer welcome.

As of June 2026 (Chrome 149, stable June 2), Chrome auto-disables an extension after an update for five distinct reasons, and the red text under the extension tells you which one. Read that message first. The re-enable path is different for a sideloaded extension than for a Manifest V2 one, and trying the wrong fix wastes time. Start here.

Read the Disable Message, Then Re-Enable

Open chrome://extensions and find the dimmed extension. The text under its name is the diagnosis. Match it to the row below before touching the toggle.

To re-enable the ones that allow it: click the toggle on the extension’s card. If it stays on through a Chrome restart, you are done. If it flips back off, the cause is structural (sideload, MV2, or policy) and a toggle will not hold it. The sections below handle each structural cause.

Fix the “Not From the Chrome Web Store” Disable

This is the most common after-update disable, and the toggle will not save you. Chrome’s extension hardening auto-disables most extensions that were installed from anywhere other than chromewebstore.google.com — a downloaded .crx file, a bundled installer that added a registry entry, or a sideload from another Chromium browser.

1. Note the exact extension name from chrome://extensions.
2. Search for it on the Chrome Web Store. Many extensions that people sideload are also published there.
3. If you find it, remove the disabled sideloaded copy, then install the store version. The store copy updates through Chrome’s normal channel and will not get auto-disabled for this reason.
4. If the extension is not on the store at all, there is no durable re-enable path in a standard Chrome profile. The extension was distributed outside Google’s review process and Chrome will keep blocking it.

This hardening rolled out progressively starting in 2024 and tightened through 2025; an update in mid-2026 can be the moment it finally catches a sideloaded extension you installed years ago. The trigger is the update applying the newer policy, not the extension changing.

When Manifest V2 Is the Reason (the Long Sunset)

If the message reads “no longer supported” or warns that the extension may stop working, you are looking at the Manifest V2 sunset, not a one-off bug.

This one is older than most people realize. Chrome began auto-disabling Manifest V2 extensions in stable builds in October 2024, and the enterprise ExtensionManifestV2Availability policy that let organizations keep them running was removed with Chrome 139 in mid-2025. By June 2026, MV2 is effectively dead for ordinary users. The only thing left is a residual ExtensionManifestV2Disabled flag workaround, and that is being closed across the Chrome 150–151 line (Chrome 150 stable lands June 30, 2026). If an extension of yours is still MV2 now, it was disabled in that 2024–2025 rollout, not by the update you just installed.

What to do:

1. Check the extension’s Chrome Web Store listing for a recent update. Many developers shipped a Manifest V3 rewrite — installing the update resolves it.
2. If the developer abandoned the extension, it is not coming back. Look for an MV3 alternative that does the same job.
3. Any residual flag trick to force an MV2 extension back on buys you days at most. The 150–151 line removes the last workaround, and there is no path back that does not go through an MV3 version.

This is the one disable reason where re-enabling is a dead end. The platform changed underneath the extension.

Stop Developer-Mode Extensions From Switching Off

If you loaded an extension as an unpacked folder through the Developer mode toggle, Chrome treats it as lower-trust and can disable it when it updates or when the profile reloads. The old “Disable developer mode extensions” warning popup was retired by Google, but the disable-on-update behavior for unpacked extensions did not go away with it.

• Re-enable it: toggle it back on at chrome://extensions. For an unpacked extension this usually holds within a session.
• Make it durable: if a published Chrome Web Store version of the same extension exists, install that instead. Store extensions do not get the developer-mode treatment.
• If you are the developer: this is expected. Pack and publish, or accept that unpacked builds need re-enabling. Unpacked is for testing, not daily driving.

Developer-mode disables are the most harmless of the five: annoying, not a wall. A store install removes the annoyance entirely.

Re-Enable a Policy-Disabled or Corrupted Extension

Two remaining causes, two different paths.

Disabled by policy. If the text says the extension was turned off by your administrator or by policy, the toggle is greyed out and unclickable. This comes from a workplace device-management profile, a school-managed Chromebook, or Chrome Family Link parental controls. On a managed device, the only fix is asking the administrator to allowlist the extension. On a personal device you think should not be managed, open chrome://policy and chrome://management to see what is applying the rule — a leftover enterprise enrollment or a second profile is sometimes the culprit.

Corrupted update. “This extension may be corrupted” means the update download or the extension files on disk got damaged. Click Repair if Chrome offers it on the extension’s card. If there is no Repair button, or repair fails, remove the extension and reinstall it from the Chrome Web Store. A clean download replaces the damaged files. Before you uninstall, check whether the extension can export its settings, because a reinstall wipes local data.

Keep a Disable From Erasing Your Work

Re-enabling an extension is one problem. The quieter problem is what the disable did to whatever the extension was holding for you. An uninstall-reinstall cycle wipes an extension’s local storage on that profile, so any extension that kept your configuration, sessions, or layout purely on-device hands you a blank slate when it comes back.

This is where the kind of extension matters. Tools that treat your data as account-synced or as recoverable state survive a disable. Tools that hold everything in volatile UI do not.

SuperchargeNavigation (v1.3.0 on the Chrome Web Store as of June 2026) is built for exactly this resilience. Your tabs live in named workspaces saved to chrome.storage.local, and the extension takes 50 automatic snapshots per workspace at 5-minute intervals — a rolling 4+ hours of history. If Chrome disables and you re-enable the extension, your workspaces are still there; if you ever uninstall and reinstall, opt-in Chrome-native sync (your browser account, not our servers) restores them rather than starting empty.

Because it ships as a published Manifest V3 store extension, it does not hit the sideload, MV2, or developer-mode disable reasons above in the first place. The Alt+K command palette searches open tabs, history, and bookmarks from the keyboard, so even after a rough morning of re-enabling things, finding a tab is a search instead of a hunt. Free core, local by default, no account required, zero telemetry.

Stop It Happening Next Update

The five causes do not all have a prevention, but most do.

If the extension is on the Chrome Web Store and you installed it from there, after-update disables are rare — the store-install path is the one Chrome trusts. The disables in this article cluster around extensions that came in through a side door (sideload, unpacked) or that the platform is sunsetting (MV2).

If your disabled extension shows “Not from the Chrome Web Store” → find it on the store and reinstall there. If it shows “no longer supported” → it is MV2, and you need an MV3 replacement. If it is greyed out under policy on a device you own → check chrome://policy for an enrollment you did not expect. Anything else, a reinstall from the store clears it.