Use a dedicated Windows Registry policy path (Software\Policies\\ungoogled-chromium) instead of sharing with Chromium
Author: edividsCreated Sep 9, 2026Updated Sep 15, 2026
Labelsenhancementhelp wantedneed info
Description
Use a dedicated Windows Registry policy path (Software\Policies\\ungoogled-chromium) instead of sharing with Chromium
Who's implementing?
- I'm willing to implement this feature myself
The problem
On Windows, ungoogled-chromium currently reads policies from the registry path Software\Policies\Chromium. This causes policy conflicts when other Chromium-based browsers are installed on the same system, as they share the exact same registry hive path.
Possible solutions
Could ungoogled-chromium consider changing its registry policy path to Software\Policies\\ungoogled-chromium (or another appropriate unique path) to prevent cross-browser policy interference?
Alternatives
No response
Additional context
No response
Source: ungoogled-software/ungoogled-chromium