Microsoft has confirmed that the unofficial Windows registry tweak allowing MV2 extensions like uBlock Origin in Edge still works, and the company has published updated guidance for IT administrators managing these settings.
What Microsoft confirmed
In a new post, Microsoft addressed a running question in the community: whether the registry workaround that lets users load legacy MV2 extensions had been quietly disabled. The answer, according to the company (as reported by Neowin), is that the tweak remains functional.
That means people who rely on uBlock Origin and other MV2-based extensions can continue using the registry method to keep them working in Edge for the time being. Microsoft did not announce any immediate change to the workaround, and it appears to be leaving the option open for now.
Alongside the confirmation, the company published additional guidance aimed at IT administrators. This is meant to help organizations that manage Edge deployments across a fleet of machines, where extension policy is typically rolled out centrally rather than machine-by-machine.
Microsoft has signaled that MV2 support in Edge will remain available for a period beyond the initial phase-out, but it has not promised indefinite support. That uncertainty is precisely why the company is steering organizations toward properly managed policy settings rather than individual workarounds.
The registry hack, explained
To understand why this matters, it helps to know what the hack actually does. Microsoft Edge, like other Chromium-based browsers, has been transitioning its extension platform from Manifest V2 (MV2) to Manifest V3 (MV3).
MV2 is the older extension format, and MV3 introduces stricter rules around how extensions run in the background. The registry tweak works by adding a policy entry that signals Edge to accept legacy MV2 extensions, effectively overriding the default behavior that would otherwise block them.
Importantly, the tweak does not modify the extension itself. It simply convinces Edge to load an extension built for the older platform. The workaround was popularized by the community after Microsoft began phasing out MV2 support.
Why MV2 still matters for uBlock Origin
The reason this workaround has drawn so much attention comes down to uBlock Origin specifically. It is one of the most widely used ad and tracker blockers, and it was built on the MV2 platform.
The extension’s developer announced that it would not be ported to MV3, arguing that the new platform’s restrictions would undermine the tool’s core capabilities. As a result, there is no MV3-native version of uBlock Origin to fall back on, which is why users have leaned on the registry method to keep it running.
This places Edge users in a similar position to Chrome users who have watched Chromium roll out its MV2 phase-out, with the registry workaround serving as the main way to preserve legacy extension support.
New guidance for IT administrators
Microsoft’s updated documentation targets the enterprise side of the equation. In organizational settings, extension availability is usually controlled through policy settings applied across many devices at once, rather than through individual user changes.
The new guidance is intended to help IT teams configure and manage the MV2-enabling policy consistently. This matters because a registry or policy change that works on a single PC can be fiddly to replicate at scale, and inconsistent configuration can leave some machines without the intended support.
What This Means for You
For everyday users, the headline takeaway is simple: if you use uBlock Origin in Edge, you can keep using it via the registry tweak for now. Microsoft has not pulled the plug on the workaround.
That said, it is worth treating this as a temporary measure. Microsoft’s broader transition away from MV2 is a longer-term direction, and workarounds of this nature are typically kept available only until a native alternative exists or the underlying platform fully moves on.
The practical upshot is that you have a working solution today, but you may want to stay aware of how Microsoft’s MV2 timeline evolves and be ready to adapt if the option is ever removed.
How to Get It
Applying the workaround means adding the appropriate registry entry that tells Edge to allow MV2 extensions. Because this involves editing the Windows Registry, it is worth proceeding carefully and creating a restore point or backup before making changes.
If you are managing a single PC, you can apply the tweak directly. If you are an IT administrator rolling this out across an organization, you should follow Microsoft’s updated admin guidance to ensure the policy is applied consistently across your fleet.
Either way, keep an eye on Microsoft’s official posts for any future changes to the workaround or the MV2 support timeline, since that is where the company will communicate shifts like these.
Source: Neowin
Over to you: Are you keeping uBlock Origin via the registry tweak, or have you already switched to an MV3-compatible alternative?
