For a handful of hours this week a small but important piece of the Edge browsing experience vanished for some users: uBlock Origin — the widely trusted, open‑source content blocker used by millions — was effectively replaced by uBlock Origin Lite in Microsoft Edge after an accidental upload and briefly unlisted in the Microsoft Store. The mix‑up, acknowledged by uBlock Origin’s author (known as gorhill) on GitHub, was the result of an upload script error that applied the Lite build to uBlock Origin’s store listing. The issue has been fixed and the correct build returned to the store, but the incident exposes three interlocking realities for Windows and Edge users: how extension publishing and Manifest V2/V3 compatibility interact today, practical recovery steps when an extension stops working, and the long‑term risks to users who rely on powerful, low‑level blockers as browser platforms evolve. (github.com)
uBlock Origin (often abbreviated uBO) is an open‑source, high‑performance content blocker that has been the ad‑blocking choice for many Windows users because of its efficiency, configurability, and strong community trust. It historically used the older extension model known as Manifest V2 (MV2) to intercept and modify network traffic using APIs—capabilities that made deep filtering, dynamic rules, and response‑level checks possible.
In recent years Chromium — the engine that powers Chrome and Microsoft Edge — introduced Manifest V3 (MV3). MV3 replaced or limited several MV2 APIs in the name of security and performance, chiefly replacing the full WebRequest blocking API with a more declarative model (Declarative Net Request, or DNR). That change dramatically reduced the ability of content blockers to perform some advanced filtering tasks. The policy and platform migration from MV2 to MV3 has been gradual and controversial; browsers, extension stores, and developers have adapted in different ways. Microsoft’s developer guidance and policy pages show that the Edge team has left parts of the MV2 retirement timeline as TBD, while Partner Center rules about accepting MV2 submissions changed as far back as July 2022. (learn.microsoft.com) (learn.microsoft.com)
For most Edge users the immediate fix is straightforward — reinstall the corrected store build or load the official release from GitHub — and then export a uBO backup to avoid future surprise resets. For those whose workflows depend on the advanced, MV2‑only features of uBlock Origin, the practical options are explicit: keep a browser that supports MV2, accept the limitations of MV3‑era Lite variants, or keep a disciplined, manual sideload/update process.
The incident is a useful, real‑world lesson in why robust backup habits, clear maintenance channels, and platform transparency matter. It also underlines why open‑source projects and attentive maintainers remain crucial to preserving users’ control over privacy, performance, and content filtering on the web. (techissuestoday.com, github.com, learn.microsoft.com)
If uBlock Origin stopped working, begin with a backup of your uBO settings, uninstall and reinstall from the Edge add‑ons store, and — if needed — use the GitHub developer build for a temporary restore. Keep an eye on your browser’s MV2/MV3 support policy and export settings regularly to protect against future publishing or store changes.
Source: Windows Central uBlock Origin disappeared from Microsoft Edge — here’s how to restore it
Background
uBlock Origin (often abbreviated uBO) is an open‑source, high‑performance content blocker that has been the ad‑blocking choice for many Windows users because of its efficiency, configurability, and strong community trust. It historically used the older extension model known as Manifest V2 (MV2) to intercept and modify network traffic using APIs—capabilities that made deep filtering, dynamic rules, and response‑level checks possible.In recent years Chromium — the engine that powers Chrome and Microsoft Edge — introduced Manifest V3 (MV3). MV3 replaced or limited several MV2 APIs in the name of security and performance, chiefly replacing the full WebRequest blocking API with a more declarative model (Declarative Net Request, or DNR). That change dramatically reduced the ability of content blockers to perform some advanced filtering tasks. The policy and platform migration from MV2 to MV3 has been gradual and controversial; browsers, extension stores, and developers have adapted in different ways. Microsoft’s developer guidance and policy pages show that the Edge team has left parts of the MV2 retirement timeline as TBD, while Partner Center rules about accepting MV2 submissions changed as far back as July 2022. (learn.microsoft.com) (learn.microsoft.com)
What happened on Edge — the short version
- The uBlock Origin developer prepared and published a uBlock Origin Lite (uBOL) build that targets Manifest V3. During a publishing script change, that Lite build was mistakenly uploaded using uBO’s extension identifier in the Microsoft Store.
- Because the store viewed the new package as an MV3 submission associated with the uBO extension ID, the system prevented a simple rollback to the older MV2 build. Facing that restriction, the author temporarily unlisted the extension to stop further unintentional replacements while working with Microsoft’s extension support to restore the correct package. (techissuestoday.com)
- The issue was resolved: the full uBlock Origin build was republished with an adjusted version number (date‑style numbering) so the store would accept it as a newer release and preserve users’ access to the original extension functionality. Users affected by the swap were advised to reinstall from the Microsoft Store or restore settings from uBO’s backup if rules or per‑site modes were reset. (pupuweb.com, techissuestoday.com)
Why this matters: Manifest V2 → Manifest V3 explained
The technical pivot
- Manifest V2 (MV2): offered the WebRequest API, which allows extensions to inspect and block network requests at runtime. This is essential for full‑featured blockers like uBO because it supports complex, dynamic filtering (including regexes, header‑based rules, and top‑frame context).
- Manifest V3 (MV3): replaces the runtime interception model with declarativeNetRequest (DNR) and service worker background scripts. DNR is designed to be safer and more performant but is less flexible: it has limits on the number of rules, lacks some header‑level and regex capabilities, and cannot replicate all MV2 behaviors. That fundamentally constrains how some blockers operate. (xda-developers.com, theverge.com)
The ecosystem fracture
Browsers, extension stores, and developers respond differently:- Google Chrome has been firmly driving MV3 migration and has removed or disabled many MV2‑based extensions for some users, prompting options such as uBlock Origin Lite (an MV3‑compliant, reduced‑capability variant) or workarounds for advanced users. Coverage of the Chrome roll‑out and its impact on ad blockers is widely reported. (theverge.com, tomsguide.com)
- Microsoft Edge continues to support MV2 for now but has partner‑center rules and policies that complicate updates and store behavior around MV2 vs. MV3 submissions; the company’s guidance lists a migration timeline but leaves some end‑dates as TBD. That ambiguity is why developers like gorhill can run into publishing hurdles when an MV3 package collides with an MV2 listing. (learn.microsoft.com)
- Firefox has historically kept MV2 support available longer and remains a favored platform for users who need the full capabilities of MV2‑based blockers.
How to restore uBlock Origin in Microsoft Edge — concrete steps
If uBlock Origin stopped working in Edge for you or was replaced by the Lite build, there are practical recovery options. These are listed in order from simplest (recommended) to most advanced (developer mode).- Reinstall from the Microsoft Store (recommended)
- Open Microsoft Edge.
- Click the Extensions icon (puzzle piece) and choose Manage extensions.
- Remove uBlock Origin from the browser.
- Open the Microsoft Store app (or the Edge Add‑ons store) and search for uBlock Origin.
- Install the extension again from the store listing.
- After installation, open uBO’s Dashboard and restore any saved settings (use uBO’s export/import) if needed.
- This is the official route and ensures automatic updates via the store. Many affected users fixed the problem by uninstalling and reinstalling once the correct build reappeared.
- Install from the Chrome Web Store (Edge supports Chrome extensions)
- Edge supports installing Chrome extensions if the setting is enabled. Navigate to the Chrome Web Store and install uBlock Origin or uBlock Origin Lite there if the store listing is available for your region. This can be a reliable fallback while store listings stabilize.
- Load the extension manually from the GitHub releases (developer/advanced)
- Visit the uBlock Origin GitHub “Releases” page and download the Chromium build (the asset named like uBlock0_x.y.z.chromium.zip).
- In Edge go to edge://extensions and toggle Developer mode on.
- Click Load unpacked and select the extracted extension folder.
- Confirm the extension is loaded and enabled.
- This method bypasses the official store but keeps you on the stable uBO code published by the author. It’s the standard sideload fallback used when stores block or remove packages. Be aware that manually loaded extensions don’t update through the store and can be disabled by browser policy or future browser versions. (github.com, tomsguide.com)
- If settings changed or filters were lost
- Reopen uBO’s Dashboard → Settings → use Restore to import a prior backup if you exported settings earlier.
- If custom filters were lost, reapply them via My filters or reimport from your saved file.
Practical checklist: what to do now
- Backup your uBlock Origin settings today: Dashboard → Settings → Backup. This is the single most practical insurance against future glitches.
- If you rely on advanced MV2 features (dynamic filtering, regex‑heavy rules, header modifiers), consider using Firefox for those needs — it remains the most MV2‑friendly mainstream option.
- If you sideload uBO from GitHub, keep a local policy of periodic manual checks for updates and verify signatures and release notes before installing new builds.
- If you administer enterprise machines, review Edge’s ExtensionManifestV2Availability policy to control whether MV2 extensions remain enabled for your fleet. Enterprises can extend MV2 operation through policy until an official cutoff. (learn.microsoft.com)
Strengths in this story
- The incident underscores the value of transparent, open‑source development: uBO’s GitHub repo, release artifacts, and public developer commentary allowed rapid diagnosis and community guidance.
- The fix demonstrates that collaboration between maintainers and store support teams can restore functionality quickly when the root cause is identified.
- The event is a useful reminder that power users can self‑recover with developer mode sideloading and GitHub releases — a resilience advantage not available for closed‑source, store‑only extensions.
Risks and downsides
- Publishing workflows are brittle when two manifest models coexist. As this case shows, store dashboards and packaging rules can block simple rollbacks and force maintainers into awkward workarounds.
- MV3’s limits are not merely academic: when platforms deprecate MV2, users can lose essential blocking capabilities unless developers provide robust MV3 equivalents — and in many cases, MV3 simply cannot match MV2’s flexibility. That leaves power users in a bind: accept reduced capability, sideload code, or switch browsers. (xda-developers.com, theverge.com)
- Sideloading and manual installs carry risk: if users stop relying on the official store they may miss automatic security updates, and manual installs can be disabled by policy or broken by future browser changes.
- Store or policy changes can be sudden and opaque, particularly around security or manifest enforcement; the lack of firm MV2 EOL dates from vendors makes long‑term planning hard for extension authors and IT admins. Microsoft’s documentation still lists some dates as TBD, which is inconvenient for administrators and users depending on MV2 behavior. (learn.microsoft.com)
What this incident suggests about the future
- Expect continued churn. The MV2 → MV3 migration is ongoing, and browser vendors will continue to refine enforcement and partner‑center policies. That migration will reshape which extensions remain viable on which platforms.
- Developers will adopt pragmatic strategies: maintainers may ship MV3 “Lite” variants to preserve a presence in Chromium stores, keep MV2 builds for platforms that allow them, and provide clear sideload instructions for advanced users.
- Users who need deep control should plan for alternatives: either keep a dedicated MV2‑friendly browser (e.g., Firefox), maintain a developer‑mode workflow for sideloading, or accept reduced functionality in the MV3 era.
- Enterprises should build policies: IT departments should set Edge policies (like enabling MV2 for specific extensions) and prepare for a support model that includes sanctioned sideloading or alternate browsers where necessary. (learn.microsoft.com)
Security and privacy guidance
- Keep the browser and extensions updated. Even if an extension is temporarily sideloaded, maintain a schedule to check for upstream releases and security patches.
- Only install extensions from trusted sources (official store listings or an author’s verified GitHub). Verify release notes and checksums when possible.
- Audit extension permissions: uBlock Origin requests broad access precisely because it must inspect and modify web traffic. That is normal for content blockers, but users should be wary of other extensions requesting the same permissions without a trustworthy track record. Community trust, open code, and a consistent maintainer history matter.
- Avoid downloading “forks” or clones from random third‑party sites that may inject analytics or adware. Prefer official author releases or well‑known store listings. (github.com)
Final analysis
This brief disappearance of uBlock Origin from Microsoft Edge was an avoidable but instructive mishap: a publishing script error collided with the industry’s messy transition between extension models. The good news is that the problem was quickly acknowledged and repaired by the maintainer with store support, and routine user recovery steps (uninstall/reinstall, or manual install via GitHub) restored functionality for most people. The bigger takeaway is structural: the web‑extension ecosystem is changing beneath users’ feet, and power features once granted by MV2 are no longer guaranteed on every Chromium‑based browser. Users, administrators, and developers must adapt.For most Edge users the immediate fix is straightforward — reinstall the corrected store build or load the official release from GitHub — and then export a uBO backup to avoid future surprise resets. For those whose workflows depend on the advanced, MV2‑only features of uBlock Origin, the practical options are explicit: keep a browser that supports MV2, accept the limitations of MV3‑era Lite variants, or keep a disciplined, manual sideload/update process.
The incident is a useful, real‑world lesson in why robust backup habits, clear maintenance channels, and platform transparency matter. It also underlines why open‑source projects and attentive maintainers remain crucial to preserving users’ control over privacy, performance, and content filtering on the web. (techissuestoday.com, github.com, learn.microsoft.com)
If uBlock Origin stopped working, begin with a backup of your uBO settings, uninstall and reinstall from the Edge add‑ons store, and — if needed — use the GitHub developer build for a temporary restore. Keep an eye on your browser’s MV2/MV3 support policy and export settings regularly to protect against future publishing or store changes.
Source: Windows Central uBlock Origin disappeared from Microsoft Edge — here’s how to restore it