What Microsoft Is Actually Turning Off
Since August 2026, Edge has begun disabling Manifest V2 extensions for consumers, with the phase-out completing by the end of the year. Managed enterprise deployments get a longer runway, into early 2027, before their installed extensions stop working under the old model. Edge is following Chrome, which already completed its own Manifest V2 sunset earlier this year - Microsoft is closing the last major gap in the transition rather than opening a new front.
The scope is narrower than the headline suggests. Microsoft's own count puts only 58 Manifest V2 extensions on the Edge Add-on Store at meaningful daily usage, and just 3 of those have shipped no Manifest V3 equivalent at all. Ninety-five percent of the store's most-used old-format extensions have already migrated. For most people, the browser will simply keep working with an updated version of whatever they already had installed.
The exception that matters is content blocking. uBlock Origin, the extension most relied on for ad and tracker blocking, cannot run its full version under Manifest V3 - Microsoft and Google both point affected users to uBlock Origin Lite instead, a rebuilt, deliberately more limited tool built to survive the new rules.
Why It Matters: the Rule Cap, Not the Rebrand
The technical reason a lighter uBlock Origin exists is not a Microsoft or Google product decision - it is baked into Manifest V3 itself. The old webRequest API let an extension inspect and block network requests as a page loaded them, in real time. Manifest V3 replaces it with declarativeNetRequest, which requires an extension to declare its blocking rules in advance and caps how many rules it can register at once.
That cap is the practical bite. New ad and tracker domains appear constantly; a Manifest V2 blocker could react to them the moment a request fired. A Manifest V3 blocker has to wait for its rule list to be updated and reloaded, and even then can only carry a fixed number of rules - which is exactly why uBlock Origin Lite blocks measurably less than its predecessor did.
Ad blockers were never only about hiding banners. Malicious ads - malvertising - have long been a real delivery channel for malware, and a real-time blocking layer is one of the few consumer-side defenses against it. Weakening that layer on the two most common Windows browsers in Europe is a security regression dressed as a compatibility update.
Yes, but Firefox Chose Differently
Mozilla has stated plainly that it will keep Manifest V2 extensions working in Firefox, including the full version of uBlock Origin, framing it as consistent with its Manifesto commitment to user control over browsing. Opera has taken a similar path. Neither is under the same commercial pressure Google and Microsoft face to standardize their extension platforms around one rule set.
That gives anyone who wants the stronger, older blocking model a real, actively maintained option rather than a dead end. It is not a workaround or a legacy holdout - Firefox's Manifest V2 support is a deliberate, ongoing product decision, not a countdown to its own eventual sunset.
Switching a fleet of managed Windows machines away from Edge or Chrome is not free, though. Enterprise policy tooling, single sign-on integrations and staff familiarity are all built around the Chromium-based defaults in most European offices, and a browser migration carries its own cost and disruption that a browser update does not.
What to Check Before December
Any business running Edge or Chrome as its managed default should audit which extensions its fleet actually depends on now, against Microsoft's and Google's published Manifest V3 migration lists. The 58-extensions, 3-without-replacement figures apply organization-wide too - a niche internal or security tool your IT team relies on could be in that unmigrated group without anyone having checked.
Security teams specifically should stop treating "ad blocker" and "malware filter" as the same line item. If a browser extension has been doing double duty as a malvertising defense, confirm the endpoint protection stack has a real answer for that gap once the extension's blocking power drops under Manifest V3, rather than assuming the old behavior carries over.
The early-2027 enterprise grace period is genuine breathing room, not a bluff - but Chrome's own Manifest V2 sunset is already finished, and Edge is now the last mainstream Chromium browser closing the same door. Later is not never, and the deadline that matters is the one your organization has not yet put on a calendar.
Read next: Google Assistant Shuts Down September 4 for Gemini | London Just Approved Its First Robotaxis, Supervised
