uBlock Origin Not Working in Chrome? Fixes After the Manifest V2 Shutdown

The icon went grey. Filters stopped updating weeks ago. Nothing you clicked caused it, and reinstalling will not bring the extension back.

What Chrome 150 and 151 took away

If your content blocker died this summer, the cause is a code removal, not a corrupted profile. Google spent close to five years retiring Manifest V2, the permissions system that governs what a browser extension is allowed to do, and the final steps landed weeks ago.

The sequence is worth having straight. In March 2025 Chrome began disabling Manifest V2 extensions by default across all channels. Chrome 138, stable on 24 July 2025, made that permanent and deleted the settings toggle that let you switch them back on. A stubborn minority kept full uBlock Origin running past that point through developer mode and a command line override. Chrome 150, released 30 June 2026, dropped the flag that restored MV2 installs from the Web Store. Chrome 151 reached stable on 28 July 2026 and deleted the AllowLegacyMV2Extensions code path from Chromium entirely.

There is no flag left to flip. Any forum thread telling you otherwise predates July.

August 31 is the last date on Google’s timeline

At the end of this month, every remaining MV2 extension leaves the Chrome Web Store. Google’s published timeline is clear about the consequence: copies already on disk stay installed, stop receiving updates, and cannot be pulled down again once the listing is gone.

That listing has confused people all summer. Full uBlock Origin carried a Manifest V2 entry right through it, sitting at version 1.72.2 as of 8 July 2026 with a user count still in the millions. Almost none of those installations have run on stable Chrome since 138. The figure reflects enterprise images, forked Chromium builds, and machines that quietly stopped updating.

The frozen filter list is the part that actually costs you something. Ad and tracker domains rotate constantly, so a blocklist that stopped refreshing in August is measurably weaker by November. It degrades rather than breaks, which is why most people will not notice.

The Lite build is a different tool, not a smaller one

Manifest V3 swaps blocking webRequest for declarativeNetRequest. Under the old API, the extension saw each request as it happened, knew which page had asked for it, and decided in the moment. The replacement takes rules registered in advance, caps how many can apply at once, and hands back none of that context. uBlock Origin’s maintainer has stated plainly that a fully compatible version is not coming.

uBlock Origin Lite is built for MV3 and it works. For most people reading this, it is enough. It blocks the standard ad and tracker sets on the sites you visit every day, and it does so without the performance cost of a permanently resident filtering engine. What you give up is dynamic filtering, per-site scripting control at any real depth, and most custom filter syntax.

One setup detail people miss: after installing Lite, open its dashboard and raise the default filtering mode. Basic is what ships, and it blocks noticeably less than the Optimal or Complete settings.

Chromium is not your only option

Firefox is not built on Chromium and is not bound by Google’s extension framework. Mozilla shipped its own version of Manifest V3 while keeping the webRequest API functional, so the full extension runs there unchanged. If the tool itself is what you want back, that is the direct swap, and profile import will carry your bookmarks and passwords across in a few minutes.

Brave went the other way and built blocking into the browser engine, skipping the extension system. Edge and Opera are Chromium projects following the same MV2 schedule, so moving to either one solves nothing.

Filtering before the browser gets involved

Every fix above is scoped to one browser on one machine. Plenty sits outside that boundary: mobile apps, smart TVs, consoles, the ads Windows serves into its own panels.

DNS-level filtering operates one layer down. Your device asks for a domain, the resolver checks it against a blocklist, and a flagged request never resolves at all. The browser is never consulted. Because it runs at the connection rather than inside a tab, it covers every application on the device at once, and no manifest 

version can switch it off.

This is why a number of VPN services now ship a filtering resolver as a built-in feature instead of an extension. Quality varies far more than the feature pages suggest, though. Gizmodo ran five of them against the same blocking test rather than taking the published claims at face value, and the spread between them was wide enough to matter.

Set expectations before you switch anything on. Domain-level filtering is blunt by design: it blocks a host or it does not, with nothing in between. Sites that load logins, payment frames, or embedded players from a flagged domain will break in confusing ways, so find the whitelist before you need it.

What none of this repairs

YouTube ads arrive from the same domain as the video itself. No domain-level blocker separates the two, and that applies equally to first-party advertising on any large platform that serves its own inventory. If that was your main reason for running a blocker, none of the options here will satisfy you.

The security case tends to get buried under the advertising revenue argument, which is a shame, because it is the stronger one. CISA’s capacity enhancement guide on browser security, revised in August 2023, tells organisations to evaluate ad blocking as a defence against malvertising, the practice of pushing malware through legitimate ad networks. The same document carries a caveat that reads differently in 2026: blocking extensions run at high privilege and can see all traffic between the workstation and the network. That reservation was always pointing somewhere other than the extension store.

What genuinely shifted on 28 July is where the decision lives. Blocking used to be a per-browser choice you made yourself and could revoke with one click. Push it down to the resolver and it becomes an infrastructure setting, and infrastructure has an owner. Whoever runs that resolver now decides which domains you never see. Better terms than Chrome is offering, certainly. Not the same kind of control.