Microsoft Edge MV2 Phase-Out to Disable uBlock Origin by End of 2026

Edge's Manifest V2 Phase-Out Catches Up With uBlock Origin Users​

Endicott says he opened Edge and found pages full of ads after months of warnings that the change was coming. His reasons for using a blocker are specific. He only blocks ads on some sites, allowlists sites he visits often, and mainly uses uBlock Origin to see how his own Windows Central articles look without ads and to take clean screenshots. He valued its per-element controls. For example, he could block page items he didn't want while keeping a product box that belongs in an article about a Surface going on sale.

The account doesn't include his Edge version, uBlock Origin version, Edge channel, or any error message. That means the exact cause of this failure can't be confirmed from the report alone. The broader context is well documented, though. When Microsoft announced its timetable in August, it said that "Beginning in August 2026, Microsoft Edge will start the consumer transition away from Manifest Version 2 (MV2) extensions and toward MV3. Our goal is to complete the consumer transition by the end of 2026, with enterprise deprecation following in early 2027." PCWorld, Winaero and Windows Central all covered that announcement.

Edge was the last major Chromium browser still running the classic extension through official channels. The uBlock Origin project page says the Chrome Web Store removed the extension on August 31, 2026. The same page still lists Microsoft Edge Add-ons as an install source and quotes Microsoft's plan for the end of MV2. Endicott's experience is an early, public example of what the rest of Edge's consumer users can expect over the next three months.

Microsoft's MV2 Timeline for Edge Runs on Two Clocks​

Readers trying to work out when their own browser will be affected will find that Microsoft's documents don't agree on the dates. The August blog post and the press coverage said some users with MV2 extensions installed will see notices on the Manage Extensions page and on Edge Add-ons product pages beginning in August 2026, and over time MV2 extensions will be disabled by default, with users directed to recommended MV3 versions where available. Microsoft's developer timeline on Microsoft Learn, last updated September 15, 2026, gives a later date. It says deprecation warnings will be shown to some users in mid-September 2026, in Edge's Manage extensions page and on the Edge Add-ons website.

Both sources agree on how the rollout works. It starts in preview builds and reaches the general-release channel later. According to PCWorld's summary, MV2 extensions will be gradually turned off by default over the next few months, showing up first in the Canary, Dev, and Beta channels before moving to the Stable channel by the end of the year.

Here's the combined schedule from Microsoft's Learn timeline and its announcement:

Microsoft hasn't published an exact Edge version or build number, or a date when any particular consumer PC will lose MV2 support. A Stable-channel user who still has a working uBlock Origin today isn't in a different situation from Endicott. Their browser just hasn't been switched over yet.

Microsoft argues the timing is justified by how much has already migrated. Per Winaero, 95% of the top MV2 extensions in the Edge Add-ons store have already moved to MV3, and only 58 MV2-based extensions still have meaningful usage, just three of which lack a publicly available MV3 version. Those figures explain why Microsoft sees the change as low-impact. They also explain why uBlock Origin users are the most vocal group affected.

Why the webRequest API Sits at the Center of the uBlock Origin Break​

A manifest version is the extension platform that a Chromium add-on is written for. Endicott points to request interception as the MV2 capability uBlock Origin depends on. Windows Central explains the technical difference this way: MV3 limits the WebRequest API, which allows ad blockers to dynamically intercept and block network requests before they load.

Under MV2, uBlock Origin can look at each network request and decide what to do with it as it happens, using its filter lists and the user's own rules. The project describes its advanced mode as including a point-and-click firewall that can be configured site by site. That dynamic control is what Endicott relied on when he blocked some page elements and allowed others.

MV3 swaps that live decision-making for declarative rules. The extension gives the browser a set of rules in advance, and the browser does the filtering. Microsoft presents this as a security and performance gain. When it first adopted MV3 in October 2020, it said the change would reduce fragmentation for developers and improve privacy, security, and performance for users. Edge is built on Chromium, and Microsoft's documentation calls MV3 a Chromium project initiative. Edge is effectively following Google's lead, just about a year behind Chrome.

Endicott's point that many other blockers "simply mask ads" instead of stopping the request describes cosmetic filtering. With cosmetic filtering, the ad content may still download but gets hidden on the page. That's a general description of how the approach works, not a measured comparison of specific products.

uBlock Origin Lite Is the Official MV3 Path, With Documented Gaps​

The uBlock Origin team maintains an MV3 version called uBlock Origin Lite (uBOL), available from the Chrome Web Store, Firefox Add-ons, Edge Add-ons and Safari. It's the obvious option for anyone who wants to stay on Edge, and Endicott calls it short of its "full fat" sibling. The project's own documentation shows where the differences are.

The uBOL README says the extension uses the MV3 API and works entirely declaratively, so it doesn't need a permanently running process to filter content. Its service worker only runs when you open the popup or the options page. The default rules include uBlock Origin's built-in filter lists, EasyList, EasyPrivacy and Peter Lowe's Ad and tracking server list. For a lot of users, that covers most ad blocking.

According to the project FAQ, these features can't be ported through the MV3 API uBOL uses:

• Dynamic filtering and dynamic URL filtering, the rule-based firewall behind uBlock Origin's advanced mode, are not available.
• Per-site switches for remote fonts and scripting are not available.
• Cosmetic filtering and scriptlet injection are off by default, and users have to raise the filtering mode to Optimal or Complete to turn them on.

The FAQ also says how much you notice these gaps depends on the sites you visit and how you configure the extension. Someone who installs uBlock Origin and never touches it may see little difference. Someone like Endicott, who works element by element on specific pages, is the kind of user most likely to miss what's gone. Other coverage says the same: an August analysis by iTechGuides described uBOL as a separate project with reduced flexibility for custom filtering, dynamic rules, script control, and advanced per-site behavior.

Brave Shields and Brave's MV2 Pledge Explain the Switch​

Endicott looked at Brave first because of its extension policy. Brave's help center says it will keep supporting a small set of MV2 extensions: AdGuard, NoScript, uBlock Origin and uMatrix. That gave him a Chromium browser where he could reinstall the classic extension if he needed to.

He didn't end up doing that. He tried Brave Shields, the ad and tracker blocker built into the browser, found it "quite effective," and says he'll stick with Shields for now while keeping uBlock Origin as a fallback. His account doesn't say he installed uBlock Origin in Brave. His positive experience is with Shields only.

Brave's own technical write-ups say Shields' ad blocking runs natively in the browser's network stack instead of through an extension using the MV2 webRequest mechanism. In practice, Shields doesn't depend on Chromium keeping MV2 alive, because it isn't an extension at all. Endicott says Shields, like uBlock Origin, blocks network requests, which speeds up pages, and that it lets him block specific elements "with a couple of clicks," though without uBlock Origin's element zapper. The speed and ease-of-use points are his impressions. He doesn't report any measurements.

Firefox is the other common destination. The uBlock Origin project says the extension "works best on Firefox." Firefox doesn't run on Chromium, so it isn't affected by Edge's MV2 schedule.

ExtensionManifestV2Availability Gives Admins a Bridge Into 2027​

Managed Windows fleets are on a separate schedule. Winaero reports that managed devices will not be affected during the consumer rollout, and Microsoft expects enterprise deprecation to begin in early 2027.

For that period, administrators have the ExtensionManifestV2Availability policy, supported in Edge 123 and later on Windows and macOS. It isn't available on Android or iOS. The Group Policy setting is "Control Manifest v2 extension availability" under Administrative Templates/Microsoft Edge/Extensions in MSEdge.admx. It's also a REG_DWORD value named ExtensionManifestV2Availability under SOFTWARE\Policies\Microsoft\Edge. The documented values are:

• A value of 0 (Default) leaves MV2 loading to the browser's built-in schedule.
• A value of 1 (Disable) blocks MV2 installs and disables existing MV2 extensions.
• A value of 2 (Enable) allows MV2 extensions, but Microsoft says this will be treated as unset once MV2 support is turned off by default.
• A value of 3 (EnableForForcedExtensions) allows only force-installed MV2 extensions, meaning those deployed through ExtensionInstallForcelist or through ExtensionSettings with the "force_installed" or "normal_installed" mode. Microsoft says this option stays available whatever the migration state.

The policy is mandatory-only. It refreshes dynamically, applies per profile, and doesn't apply to profiles signed in with a personal Microsoft account. This is a tool for organizations with work or school management, not a fix home users can apply to get uBlock Origin back on their personal PCs. Microsoft calls MV2 deprecated and says all extensions will eventually need to move to MV3, so admins should treat option 3 as time to migrate, not a permanent exception.

What this means for you​

If you use the classic uBlock Origin on a personal copy of Edge, decide now what you'll replace it with instead of waiting for Edge to disable it. Business users on managed PCs can let IT handle the timing. Microsoft's rollout goes from preview channels to Stable, so Canary, Dev and Beta users will generally lose MV2 first. Stable users should expect it by the end of the year.

• Open edge://extensions and check whether uBlock Origin shows a deprecation warning, since Microsoft says the notices appear on that page for a subset of users.
• Back up your custom filters and allowlist from uBlock Origin's settings while the extension still runs, because Edge will disable it once the switch reaches your channel.
• Try uBlock Origin Lite if you mostly rely on default filter lists, and move its filtering mode to Optimal or Complete if you need cosmetic filtering.
• Choose Firefox, or Brave with its stated MV2 commitment for uBlock Origin, if you rely on dynamic filtering or per-site script and font switches.
• Treat Brave Shields as a built-in blocker that doesn't depend on MV2, keeping in mind that its good reviews in this case come from one writer's impressions, not measurements.
• If you manage Edge for an organization, set up ExtensionManifestV2Availability with force-installed extensions before early 2027 and use that window to test MV3 replacements.

Endicott's switch to Brave is the most visible example so far of a change that will reach every consumer Edge install by December. Microsoft has set the direction and a rough schedule, and uBlock Origin's maintainers have released their MV3 version. What's left is each user's own choice between Edge with a reduced blocker and a different browser with the full one. For enterprise IT, the same decision is pushed back only until the early-2027 deprecation begins.