How to keep using adblockers on chrome and chromium

manifest-v2-chrome.md

How to keep using adblockers on chrome and chromium

1. google's manifest v3 has no analouge to the webRequestBlocking API, which is neccesary for (effective) adblockers to work
2. starting in chrome version 127, the transition to mv3 will start cutting off the use of mv2 extensions alltogether
3. this will inevitably piss of enterprises when their extensions don't work, so the ExtensionManifestV2Availability key was added and will presumably stay forever after enterprises complain enough

You can use this as a regular user, which will let you keep your mv2 extensions even after they're supposed to stop working

Linux

In a terminal, run:

sudo mkdir -p /etc/opt/chrome/policies/managed /etc/opt/chromium/policies/managed
echo '{ "ExtensionManifestV2Availability": 2 }' | sudo tee /etc/opt/chrome/policies/managed/policy.json /etc/opt/chromium/policies/managed/policy.json

ChromeOS

• enable developer mode
• upon rebooting, go into vt2 (shift+ctrl+right arrow function key)
• log in as root
• type in /usr/libexec/debugd/helpers/dev_features_rootfs_verification && reboot
• upon rebooting, go into vt2 again and log in as root
• run the commands from the linux section

Windows

Open regedit, and create Software\Policies\Google\Chrome\ExtensionManifestV2Availability in HKEY_LOCAL_MACHINE as a dword set to 0x00000002

MacOS

In a terminal, run: defaults write com.google.Chrome ExtensionManifestV2Availability -int 2 defaults write com.google.Chromium ExtensionManifestV2Availability -int 2

(note that i haven't tested this for mac. please let me know if it doesn't work)

on my Manjaro install using the extra/chromium package, the policy folder was located in /etc/chromium/policies/..., note the lack of opt

Powershell option from this thread:
Run powershell as admin and then use this command:
$path = "registry::HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome"; New-Item $path -Force; Set-ItemProperty $path -Name ExtensionManifestV2Availability -Value 2

Thank you!

This change makes Chrome say "Your browser is managed by your organization" in the settings. It has an impact of disabling browser DNS setting, and maybe something else. Some claimed they had issues restoring browser to unmanaged state even after clearing the registry.

I found an official guide on how to properly clear out the policies and their cache: https://support.google.com/chrome/a/answer/9844476?hl=en

Policy state can also be checked here (after successful modification it says ExtensionManifestV2Availability: 2):
chrome://policy/

Try setting "DnsOverHttpsMode": "secure"
Windows command: reg add HKLM\Software\Policies\Google\Chrome /v DnsOverHttpsMode /t REG_SZ /d secure /f

The value "automatic" can also be used instead of "secure".

source

For Ubuntu : Chromium is packaged by snap, so the right file is /var/snap/chromium/current/policies/managed/policy.json

this no longer works on ChromeOS as of R131 due to this patch: https://chromium-review.googlesource.com/c/chromium/src/+/5258257

also the path for chromium is /etc/chromium/policies/managed/

src/chromium/src/components/policy/core/common/policy_paths.cc:
--------------------------------------------------------------------------
#if BUILDFLAG(IS_POSIX) && !BUILDFLAG(IS_MAC)
#if BUILDFLAG(GOOGLE_CHROME_BRANDING)
const char kPolicyPath[] = "/etc/opt/chrome/policies";
#elif BUILDFLAG(GOOGLE_CHROME_FOR_TESTING_BRANDING)
const char kPolicyPath[] = "/etc/opt/chrome_for_testing/policies";
#else
const char kPolicyPath[] = "/etc/chromium/policies";
#endif  // BUILDFLAG(GOOGLE_CHROME_BRANDING)
#endif  // BUILDFLAG(IS_POSIX) && !BUILDFLAG(IS_MAC)

it works on win/mac, good job.