Question On may 31th 2025 Chrome disabled Mv2 extensions, a year has gone. How did it impact your favorite extensions?

Please provide comments and solutions that are helpful to the author of this topic.
Will it receive updates, or is this an outdated extension version?
@lokamoka820, yes, as of right now it still receives updates. Brave independently hosts the MV2 version of uBlock Origin on their own servers so it doesn't depend on the Chrome Web Store anymore. While the core extension code remains working thanks to Brave's current implementation, the most important part—the filter lists—continue to pull automatic updates daily just like always. It's a great solution for now, though down the road it will depend on how long Brave decides to maintain this internal workaround. 🛡️✨
 
@Halp2001 and @lokamoka820

Why not use the build in Mv2 extension option of Brave for uBlockOrigin Mv2?
View attachment 297955
Hi @LinuxFan58, to be honest, when I first tried fixing this, that built-in option wasn't available yet (or at least I completely missed it). So yeah, looking back it definitely felt like a bit of a "sadomasochistic" exercise :LOL:on my part doing it the hard way! I really appreciate you sharing that solution, it makes things so much easier for everyone. 🛡️✨
 
Hi @LinuxFan58, to be honest, when I first tried fixing this, that built-in option wasn't available yet (or at least I completely missed it). So yeah, looking back it definitely felt like a bit of a "sadomasochistic" exercise :LOL:on my part doing it the hard way! I really appreciate you sharing that solution, it makes things so much easier for everyone. 🛡️✨
I understand that you missed it, t is only visible from the settings menu, not when clicking on the extension icon in the top bar :unsure:
 
@Sampei.Nihira, actually, Brave does use the AppContainer sandbox for its renderer processes on Windows. I just checked my own running processes in Process Explorer and they split exactly like that for security. The main browser process runs at Medium integrity, while tabs and extensions run at Low and Untrusted. In Chromium, that Untrusted label is the visual proof that the process is strictly isolated inside the AppContainer with no privileges to touch the OS. Here is a screenshot of how it looks on my end.
View attachment 297956

Hi, thanks for your test.
That's not how it works; you should check it this way:

1.png

;)(y)
 
Hi, thanks for your test.
That's not how it works; you should check it this way:

View attachment 297968

;)(y)
You’re absolutely right, @Sampei.Nihira . Thanks for the correction. Technically, the ‘Not Trusted’ label alone isn’t enough to confirm AppContainer — you need to check the specific column, just like you showed in your screenshot. I learned something new today.🎯
So with your test, it’s clear that Brave does use AppContainer — I was just looking at the wrong indicator. Thanks for taking the time to explain it and share the correct screenshot!

Cheers and keep learning! 🙌
 
You’re absolutely right, @Sampei.Nihira . Thanks for the correction. Technically, the ‘Not Trusted’ label alone isn’t enough to confirm AppContainer — you need to check the specific column, just like you showed in your screenshot. I learned something new today.🎯
So with your test, it’s clear that Brave does use AppContainer — I was just looking at the wrong indicator. Thanks for taking the time to explain it and share the correct screenshot!

Cheers and keep learning! 🙌

No, it's my personal Chrome installation that uses the AppContainer Renderer because I made that change a while ago.

All other Chrome installations do not use the AppContainer Renderer.
And so I assume the same is true for all other Brave browsers.