Chrome 140 Update Blocks Legacy Extensions: Here’s How to Fix It
Google has released Chrome 140, and with it, users have encountered new restrictions on extensions built on Manifest V2. Previously, support for such add-ons could be enabled through special flags, but these options have now been completely removed.
This has complicated the installation of popular ad blockers, including uBlock Origin, though workarounds remain possible for the time being.
To restore functionality, users must modify the browser shortcut. This involves creating a copy of the Chrome shortcut, adding the parameter
--disable-features=ExtensionManifestV2Unsupported,ExtensionManifestV2Disabled
to its properties, and launching Chrome with these arguments, thereby re-enabling support for the legacy API. Under these conditions, uBlock Origin can once again be activated or reinstalled from the Chrome Web Store.
An alternative method is to install the extension through the Load Unpacked feature. However, this requires first enabling the flag “Temporarily unexpire M139 flags” in Chrome 140, or “Temporarily unexpire M140 flags” in Chrome 141.
Both solutions are, however, temporary measures. Google will continue phasing out Manifest V2 capabilities, and eventually, running such extensions will no longer be possible.
Developers recommend preparing an exit strategy in advance: either migrating to browsers that still support Manifest V2—such as Firefox or Opera—or adopting blockers designed for Manifest V3. One example is the lightweight alternative, uBlock Origin Lite.
Support Our Threat Intelligence
If you find our technology report and cybersecurity news helpful, consider supporting our work.
Buy Me a Coffee
PayPal
