For a handful of hours this week, uBlock Origin—the widely trusted, open-source content blocker used by millions—simply disappeared from Microsoft Edge. The extension’s author, known as gorhill, confirmed on GitHub that an upload script error had accidentally pushed the Manifest V3-based uBlock Origin Lite build under the main uBlock Origin identifier in the Microsoft Store. The mistake triggered a cascade of consequences: the store’s policies blocked a rollback to the previous Manifest V2 package, forcing a temporary unlisting, and users found themselves either without an ad blocker or suddenly running the less capable Lite variant. The incident was resolved within hours, but it exposed the brittle intersection of extension publishing, the industry’s ongoing MV2-to-MV3 migration, and the precarious position of power-user tools on Chromium-based browsers.

The Incident: What Happened

According to gorhill’s public post, the mishap occurred while reworking an upload script. “I messed up yesterday, I uploaded uBO Lite using uBO extension id,” he wrote. The script change mistakenly applied the Lite build to the store listing for the full uBlock Origin extension. When the error became apparent, attempts to push a corrected Manifest V2 build (version 1.65.0) were rejected by the Microsoft Store dashboard. The store interpreted the new submission as a downgrade from MV3 to MV2, a move now prohibited by Partner Center policies that restrict new MV2 extensions. With no quick rollback option, gorhill unlisted the extension to prevent further auto-replacements.

The unlisting meant that Edge users who already had uBlock Origin installed suddenly found the extension either disabled or automatically updated to the Lite version. Clicking the icon did nothing, and ads flooded pages that had previously been clean. The fix came after the developer worked with Microsoft’s extension support team: a repackaged build with a date-style version number (like 1.65.0) was accepted as a newer release, restoring the full MV2-based uBlock Origin to the store. Users affected were advised to uninstall the extension and reinstall from the Store, then reimport any saved settings.

The Root Cause: A Script Error Meets MV2/MV3 Restrictions

The human error was straightforward, but the aftermath highlights how store policies around manifest versions can turn a simple mistake into a support nightmare. Microsoft, like Google, has been pushing the Manifest V3 architecture for Chrome and Edge extensions, citing security and performance improvements. However, the Edge team has left the official end-of-life date for MV2 support as “TBD” in its documentation, creating an ambiguous middle ground. Meanwhile, Partner Center rules already block new MV2 submissions, meaning that a developer who accidentally uploads an MV3 package under an existing MV2 listing cannot easily revert—the store sees it as a disallowed attempt to publish a legacy extension.

This policy collision is at the heart of the incident. gorhill’s upload script mistake would have been a minor bump on platforms with more flexible rollback mechanisms. On Edge, it became a full-scale disruption because the store’s automated checks classified the corrected MV2 build as an invalid MV3→MV2 downgrade. The temporary unlisting was a desperate but necessary step to stop the damage while seeking manual intervention from store support.

Why This Matters: The Manifest V2 to V3 Transition

To understand the stakes, we need to look at what MV2 and MV3 actually mean for ad blocking. The older Manifest V2 allowed extensions to use the WebRequest API, which could intercept and modify network requests in real time—essential for advanced content blockers. uBlock Origin’s power comes from dynamic filtering rules, regex-based pattern matching, header inspection, and per-site granularity, all of which depend on that API.

Manifest V3 replaces WebRequest with Declarative Net Request (DNR), a more restrictive model. Instead of actively inspecting traffic, extensions must declare a static set of rules ahead of time. DNR is safer and less resource-hungry, but it caps the number of rules, lacks header-level capabilities, and cannot replicate the full flexibility of MV2. The result is that extensions like uBlock Origin cannot port all their features to MV3; the “Lite” variant exists precisely because a full-featured MV3 version is impossible under current constraints.

Google Chrome has aggressively driven the migration, disabling MV2 extensions for many users and pushing adopers to MV3-compliant alternatives. Firefox has maintained robust MV2 support. Microsoft Edge occupies an uneasy middle: MV2 still works, and enterprise policies can extend its life, but the store already restricts new submissions, and the public timeline for a cutoff remains “TBD.” This uncertainty leaves power users and developers in limbo, and the uBlock Origin mishap is a living example of what can go wrong when the rules are vaguely defined.

Immediate Recovery: How to Get uBlock Origin Back

If you were affected by the incident, the recovery is straightforward. The corrected build is now live in the Microsoft Store, and the following steps will restore full functionality:

  1. Reinstall from the Microsoft Store (recommended)
    - Open Edge, click the Extensions puzzle-piece icon, and choose Manage extensions.
    - Remove uBlock Origin from the list.
    - Head to the Microsoft Edge Add-ons store and search for “uBlock Origin.” Install it fresh.
    - Once installed, open the uBlock Origin Dashboard, go to Settings, and use the Restore button to import a backup of your filters and rules if you had one.

  2. Use the Chrome Web Store as a fallback
    Edge supports installing Chrome extensions. If the Microsoft Store listing ever becomes unavailable again, visit the Chrome Web Store, search for uBlock Origin, and add it to Edge. This method works because Edge is Chromium-based and respects Chrome Web Store installations when the setting is enabled.

  3. Sideload the developer build from GitHub (advanced)
    - Navigate to the official uBlock Origin GitHub Releases page.
    - Download the Chromium build (a ZIP file named like uBlock0_1.65.0.chromium.zip).
    - In Edge, go to edge://extensions and toggle Developer mode on.
    - Click Load unpacked and select the extracted extension folder.
    - This manual install bypasses the store entirely and gives you the exact build published by gorhill. Remember, manual installs don’t auto-update, so you’ll need to check for new releases periodically.

If your custom filters or per-site settings were reset during the swap, use the Dashboard’s Restore function to import a backup. If you never created a backup, this is a perfect lesson to do so: open the uBlock Origin Dashboard → Settings → Back up to file. Store that file somewhere safe.

Long-Term Resilience: Backups, Browsers, and Policies

The incident offers a clear playbook for future-proofing your ad-blocking setup:

  • Export your uBlock Origin settings regularly. The backup file captures your filters, whitelists, and dynamic rules. It’s your insurance against any extension reset, uninstallation, or browser profile corruption.
  • Consider a dedicated MV2-friendly browser. Firefox remains the most reliable platform for full-featured MV2 content blockers. If you depend on advanced uBlock Origin capabilities, using Firefox as your primary or secondary browser ensures you won’t be forced into a Lite version.
  • For enterprise environments, leverage Edge policies. Administrators can set the ExtensionManifestV2Availability policy to explicitly allow MV2 extensions on managed devices. This can delay forced migration until Microsoft provides a definitive cutoff date. The policy documentation on Microsoft Learn outlines how to enable MV2 for all extensions or specific ones.
  • If sideloading, verify releases. Only download from gorhill’s official GitHub repository. Check the release notes and, if possible, verify checksums. Sideloaded extensions are a powerful workaround but also a security responsibility.

The Broader Picture: Fragile Publishing, Uncertain Futures

uBlock Origin’s brief disappearance is more than a quirky glitch. It underscores how the entire extension ecosystem is being reshaped by platform vendors, often without clear communication or smooth transition paths. Developers are caught between maintaining two separate codebases (MV2 and MV3), navigating store policies that can block legitimate updates, and placating users who demand features that MV3 simply cannot provide.

The current state of MV2 on Edge is a ticking clock with no visible countdown. Microsoft’s documentation still marks the MV2 deprecation date as “TBD,” a placeholder that has persisted for months. This silence creates risk: users and IT departments cannot plan effectively, and developers like gorhill face unpredictable technical hurdles. As this incident shows, even a minor scripting mistake can be amplified into a user-facing crisis by policy restrictions designed for a transition that has yet to complete.

The broader lesson is that robust, user-empowering tools like uBlock Origin now operate in a fragile state. Their survival depends on the willingness of browser vendors to support legacy APIs, the ability of developers to maintain multiple builds, and the vigilance of users who are willing to sideload or switch browsers. The web is moving toward a more controlled, declarative extension model—one that offers tangible security benefits but strips away the deep customization that power users have come to expect.

Final Thoughts

The good news: uBlock Origin is back on Microsoft Edge, and restoring it is a quick uninstall-reinstall process. The bad news: the underlying tensions won’t disappear. As the MV2-to-MV3 migration continues, similar disruptions are likely, particularly on platforms that enforce ambiguous or poorly communicated policies. For now, the simplest protection is a backup file and a willingness to adapt. Whether you stay on Edge with the full extension, switch to Firefox for unfettered blocking, or accept the Lite version’s limitations, the choice is yours—but only if you remain informed and prepared. The incident is a reminder that in the modern browser landscape, the tools you depend on can vanish in a moment, and the only reliable defense is a proactive one.