# Vivaldi prompting to disable manifest V2 extensions

**URL:** <https://taggartinstitute.org/t/vivaldi-prompting-to-disable-manifest-v2-extensions/749>\
**Category:** General\
**Created:** [July 9, 2026, 12:17pm UTC](https://taggartinstitute.org/t/vivaldi-prompting-to-disable-manifest-v2-extensions/749 "2026-07-09T12:17:23Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![LeonVQZ](https://taggartinstitute.org/user_avatar/taggartinstitute.org/leonvqz/32/75_2.png) [@LeonVQZ](https://taggartinstitute.org/u/LeonVQZ)\
**Post date:** [July 9, 2026, 12:17pm UTC](https://taggartinstitute.org/t/vivaldi-prompting-to-disable-manifest-v2-extensions/749/1 "2026-07-09T12:17:24Z")

</div>

I just got this prompt after updating Vivaldi today

 ![image](https://taggartinstitute.org/uploads/default/original/2X/2/297c44106c9610c1090c364e42cff037e194587d.png)

I still have installed the V2 version of uBO, and after updating to “8.1.4087.46 (Official Build) (arm64)” it seems that they’re doing this to prepare us for 8.2 or 8.3.

[https://forum.vivaldi.net/topic/118899/fyi-google-chrome-149-will-be-the-last-version-fully-supporting-mv2-and-blocking-webrequest-on-regular-extension-installs](https://forum.vivaldi.net/topic/118899/fyi-google-chrome-149-will-be-the-last-version-fully-supporting-mv2-and-blocking-webrequest-on-regular-extension-installs)

And it’s not vivaldi’s fault, it’s being removed from source.

---

<div class="post-metadata">

**Author:** ![maynard](https://taggartinstitute.org/user_avatar/taggartinstitute.org/maynard/32/434_2.png) [@maynard](https://taggartinstitute.org/u/maynard)\
**Post date:** [July 9, 2026, 12:26pm UTC](https://taggartinstitute.org/t/vivaldi-prompting-to-disable-manifest-v2-extensions/749/2 "2026-07-09T12:26:25Z")

</div>

Google/Chromium did this a while ago … now accepting only diminished uBlock Origin Lite

Firefox doesn’t have this restriction.

---

<div class="post-metadata">

**Author:** ![mttaggart](https://taggartinstitute.org/user_avatar/taggartinstitute.org/mttaggart/32/10_2.png) [@mttaggart](https://taggartinstitute.org/u/mttaggart)\
**Post date:** [July 9, 2026, 12:50pm UTC](https://taggartinstitute.org/t/vivaldi-prompting-to-disable-manifest-v2-extensions/749/3 "2026-07-09T12:50:11Z")

</div>

Did you ever look under the hood at what Vivaldi’s built-in ad blocker is?

The answer might surprise you.

---

<div class="post-metadata">

**Author:** ![LeonVQZ](https://taggartinstitute.org/user_avatar/taggartinstitute.org/leonvqz/32/75_2.png) [@LeonVQZ](https://taggartinstitute.org/u/LeonVQZ)\
**Post date:** [July 9, 2026, 1:02pm UTC](https://taggartinstitute.org/t/vivaldi-prompting-to-disable-manifest-v2-extensions/749/4 "2026-07-09T13:02:02Z")

</div>

> [@mttaggart](#):
>
> what Vivaldi’s built-in ad blocker is?

Nope, I’ve never searched it.  
Vivaldi has had many updates since last I tried it, so it might be much better now.

---

<div class="post-metadata">

**Author:** ![maynard](https://taggartinstitute.org/user_avatar/taggartinstitute.org/maynard/32/434_2.png) [@maynard](https://taggartinstitute.org/u/maynard)\
**Post date:** [July 11, 2026, 11:40am UTC](https://taggartinstitute.org/t/vivaldi-prompting-to-disable-manifest-v2-extensions/749/5 "2026-07-11T11:40:34Z")

</div>

I get similar from 8.1 with regard to Feedbro extension, which the upgrade disabled … but I could manually re-enable it … for now.

Some more old stuff from the devs: [Manifest v3 update: Vivaldi is future-proofed with its built-in functionality | Vivaldi Browser](https://vivaldi.com/blog/manifest-v3-update-vivaldi-is-future-proofed-with-its-built-in-functionality/)