Eclipse Community

I love the ungoogled chromium project and it still is my default browser (though i do have several browsers installed for different purposes)
Im curious is there any forks of ungoogled chromium for windows 7 that respect the projects objectives/features?

id take ungoogled chromium 112 for windows 7

The only one I know is this one (v127):
https://github.com/adeii/supermium-portable/releases/download/v124/ungoogled-Chromium-portable-127.0.6533.89-x64-VxKex.7z

x64 only and it requires VxKex. I have not tried it.

There is another thread here at Eclipse that discusses 360Chrome v21.
I have never used v21 but it does run in Win7.
It will not be "ungoogled" by default, but I do know "how" to ungoogle it if the Original Poster is interested.

For reference, I was running XP up until just months ago and I have experience in modifying 360Chrome v13.5.
It's actually quite easy but is a bit time-consuming. I just never had a need for v21 directly as I migrated from XP to 10 and skipped 7.

If enough Eclipse Members are interested, I could add a v21 to the Community Projects section.
I would advise to only run it inside a VM until vetted and matured.

Duke wrote: *

11 Feb 2025, 19:46

The only one I know is this one (v127):
https://github.com/adeii/supermium-portable/releases/download/v124/ungoogled-Chromium-portable-127.0.6533.89-x64-VxKex.7z

The project that this is forked from has a v130.
It's currently my default browser in Win10 since stumbling into this thread.
Faster benchmark scores than Official Ungoogled and I prefer portable browsers.

It's my understanding (the more-in-the-know-here may be able to provide hints/suggestions [though I suspect that most members here use Firefox over Chrome/Chromium]) that it can be made to work in Win7/VxKex by "replacing DiscardVirtualMemory with VirtualAlloc". Doesn't sound too difficult. I'd be willing to attempt with proper hints/suggestions. The portable loader typically will still function with the underlying app folder updated from v127 to v130.

The-10-Pen wrote: *

22 Feb 2025, 13:57

The project that this is forked from has a v130.
It's currently my default browser in Win10

But this thread is about Windows 7
So if you can do changes to make this version 130 running on Windows 7 then just do it

As of late I've been following this fork: https://github.com/e3kskoy7wqk/Chromium-for-windows-7

The github consists pretty much entirely of .diff files with instructions on how to patch and build the code from the official source.
It seems open and quite transparent with the modifications it makes to the code, although if anybody more intelligent than me could take a look to be sure that'd be great.

The ungoogled build is fully up to date on 133, and the main fork is even updated to nightly 135. The developer also seems to make up to date nightly forks of firefox (137) and electron (36) as well.

I'm surprised I haven't heard of these projects sooner, unless there's some sort of reason not to use them I'm not aware of.

ersatz wrote: *

04 Mar 2025, 16:48

The ungoogled build is fully up to date on 133

Have you tested it on Windows 7 or 8 ? Does it work ?

Yes I tested ungoogled chromium 133, normal chromium 135, and electron 36 to run a few apps on windows 7 and they all worked flawlessly. Cannot confirm whether or not the firefox builds work but I don't see any reason to assume they wouldn't.

I did my best to look through the modifications they made to each program's source. There's a lot and I'm not entirely qualified to understand whats going on but it looks fine to me. Its pretty insane how thorough it all is, there are .diff files for making 7 compatible versions of pretty much the last 20 versions. (Minus electron, which is only available for nightly 36)

Thanks for the info

But it would be nice to have an ungoogled Chromium build which still supports Manifest V2 extensions.
AFAIK they dropped Manifest V2 with Chromium v127.

Define "still supports"?
I'm on Official Ungoogled Chromium v133 and several of my extensions are MV2.

The-10-Pen wrote: *

05 Mar 2025, 16:48

I'm on Official Ungoogled Chromium v133 and several of my extensions are MV2.

Until June 2025:
https://developer.chrome.com/docs/extensions/develop/migrate/mv2-deprecation-timeline?hl=en

ill be trying https://github.com/e3kskoy7wqk/Chromium-for-windows-7/releases/tag/ungoogled-chromium_132.0.6834.159

Lappo wrote: *

08 Mar 2025, 21:21

ill be trying https://github.com/e3kskoy7wqk/Chromium-for-windows-7/releases/tag/ungoogled-chromium_132.0.6834.159

i forgot sometime round 126 or so they butchered the UI, id seen it the last time i ran artix but i forgot about it, i aint touching that ugly UI with a stick

Lappo wrote: *

08 Mar 2025, 21:37

they butchered the UI
i aint touching that ugly UI with a stick

AGREED!

But it's actually very easy to fix!
Download (don't "install", just download) (use crx4chrome, Get CRX, CRX Extractor/Downloader, etc) any "theme".
Extract the .crx, edit the manifest.json, .zip then rename to .crx, then "install" into Ungoogled Chrome.

I use this one - https://chromewebstore.google.com/detail/darker-classic-blue/ebnoknfohgdljcfdkigconnialgigdap
Then I edit the manifest tab colors to match all other title bar colors on my system.
Nothing I hate more than 99% of my programs using the same colors but then Chromium using its own.
So my Chromium is configured to MATCH my other programs.

My manifest:

{
"update_url": "https://clients2.google.com/service/update2/crx",

"manifest_version": 3,
"version": "1.0.1",
"name": "Classic Blue",
"theme": {
"colors": {
"frame": [ 0, 99, 177 ],
"frame_inactive": [ 72, 143, 199 ],
"toolbar": [ 234, 241, 251 ],
"ntp_background": [ 255, 255, 255 ],

"tab_text": [ 60, 64, 67 ],
"bookmark_text": [ 41, 74, 112 ],

"tab_background_text": [ 255 , 255, 255 ],
"tab_background_text_inactive": [ 255 , 255, 255 ],

"ntp_text": [ 41, 74, 112 ]
},
"tints" : {
"buttons-disabled": [ 0.6, 0.8, 0.8 ]
}
}
}

Looks like the Chromium-for-win7 repo seems to be focusing on just providing patches for modifying chromium in general so the ungoogled-chromium build is getting a little out of date. Good news is the patches look compatible between different forks based on what the dev said so I'm gonna try compiling the latest ungoogled-chromium myself.

If it all works fine I'll upload the binary somewhere in case anybody needs it.

ersatz wrote: *

25 Mar 2025, 16:20

If it all works fine I'll upload the binary somewhere in case anybody needs it.

I've been meaning to attempt a compile.
I kind of fear that it is a very big bite and too much to chew.
I'd be interested in knowing how easy or difficult it is to "learn" how to compile.

Well, very ironically just as I went to the repo to follow the build instructions I saw that they've just now released a new ungoogled build.
Just installed it and it works great! Here's the link for anyone who needs it. Looks like its the latest version. Super happy they're continuing to supply builds, I prefer firefox but use ungoogled for school so its wonderful to have the option.



Sidenote: I was also encountering a bug in the 133 build in which youtube playback wasn't functioning properly, but it looks like that's been fixed in this version. ＼(＾▽＾)／

ersatz wrote: *

27 Mar 2025, 00:24

Sidenote: I was also encountering a bug in the 133 build in which youtube playback wasn't functioning properly, but it looks like that's been fixed in this version. ＼(＾▽＾)／

There's a fix for that (below).

YouTube is basically using WebGL (fingerprinting?) and performs tests for *valid* WebGL data.
Official Ungoogled used to send *invalid* (ie, "blank"/"empty") WebGL data and YouTube "caught on".

There are forks out there that make this same MISTAKE with clienthints, you should *NOT* send "blank" / "empty" data !!!
"Blank" / "Empty" is a GIGANTIC FINGERPRINT in-and-of-itself!

Fix for YouTube on v133 -

// ==UserScript==
// @name - YouTube 03 - Workaround and H264ify
// @version 2025-02-27
// @match https://www.youtube.com/*
// @match *://*.youtube.com/*
// @match *://*.youtube-nocookie.com/*
// @match *://*.youtu.be/*
// @run-at document-start
// @grant none
// ==/UserScript==

(function () {
"use strict";

const h264ifyEnable = true;
const h264ifyBlock60fps = false;

const originalGetContext = HTMLCanvasElement.prototype.getContext;
HTMLCanvasElement.prototype.getContext = function (contextType) {
if (contextType === "webgl" || contextType === "webgl2") {
console.log("WebGL is disabled by Tampermonkey");
return null;
}
return originalGetContext.apply(this, arguments);
};

if (!h264ifyEnable) {
return;
}

function override() {
var videoElem = document.createElement('video');
var origCanPlayType = videoElem.canPlayType.bind(videoElem);
videoElem.__proto__.canPlayType = makeModifiedTypeChecker(origCanPlayType);

var mse = window.MediaSource;
if (mse === undefined) return;
var origIsTypeSupported = mse.isTypeSupported.bind(mse);
mse.isTypeSupported = makeModifiedTypeChecker(origIsTypeSupported);
}

function makeModifiedTypeChecker(origChecker) {
return function (type) {
if (!type) return '';

var disallowed_types = ['webm', 'vp8', 'vp9', 'av01'];
for (var i = 0; i < disallowed_types.length; i++) {
if (type.includes(disallowed_types)) return '';
}

if (h264ifyBlock60fps) {
var match = /framerate=(\d+)/.exec(type);
if (match && parseInt(match[1], 10) > 30) return '';
}

return origChecker(type);
};
}

override();
})();