Firefox and Chromium running on Windows 7 by e3kskoy7wqk.

[EliraFriesnan]

On 11/30/2025 at 10:36 PM, Jody Thornton said:

Vista or older, I stick to JUST keeping Windows 8 going. 

Jody, Vista is the same 6.x as Win8, as soon as he retires Vista, Win8 will follow the same road.

Win10 is another story though.

[Jody Thornton]

I still have LTSC 2019 setup, and heavily customized, but I'm putting off using it.  I really enjoy Windows 8.

[mjd79]

https://github.com/e3kskoy7wqk/Chromium-for-windows-7-REWORK/issues/7

[Jody Thornton]

On 12/15/2025 at 3:27 AM, mjd79 said:

https://github.com/e3kskoy7wqk/Chromium-for-windows-7-REWORK/issues/7

I'm using his Firefox ESR builds.  They suit me fine.  For now, that is

 

Edited December 16, 2025 by Jody Thornton

[ED_Sln]

I tested the new Chromium on Win XP. It runs faster than Supermium. But there are a few things to note.

The RAM consumption bug when C++ is installed can be resolved by adding the corrected_api_sets.zip folder from Supermium. In XP x64, there is enormous virtual memory consumption, and I haven't found a solution.

WebGL is completely disabled, even the software version, which means that websites that require it do not work.

Manifest v2 is available but disabled by default. You need to add the parameter --disable-features=ExtensionManifestV2Unsupported,ExtensionManifestV2Disabled to the shortcut.

To disable the notification that the OS is not supported, add --test-type to the shortcut.

The browser requires a CPU with SSE3.

Browser crash during import fixed in version 144.

[genieautravail]

@ED_Sln

Please, as I don't have a GitHub account, can you ask to the developper to remove the code that delete all extensions when you move the portable versions of Chromium and Ungoogled Chromium from one computer to another. 

It's a horrible feature added by Google... 

I'm not sure about that but it seems that even some settings are restored by default with the move.

Tested with Chromium 146.0.7656.0 and Ungoogled Chromium 144.0.7559.59.

Regards

 

Edited Wednesday at 06:57 PM by genieautravail

[NotHereToPlayGames]

Are you sure that your profile is set up to be portable?  ie, with either a "loader" or something like "chrome++"?

[ED_Sln]

@genieautravail

The ungoogled version has the flags #disable-encryption and #disable-machine-id. Enabling them will disable encryption and machine ID creation, allowing you to transfer your profile to another computer. The developer will not transfer them to the regular version, leaving the functionality completely stock. Therefore, for the regular version, use third-party tools to create a portable version.

[genieautravail]

16 hours ago, NotHereToPlayGames said:

Are you sure that your profile is set up to be portable?  ie, with either a "loader" or something like "chrome++"?

Yes, I use the loader of 360 Chrome browser.

Works very well with Supermium and Thorium too.

Regards

[genieautravail]

4 hours ago, ED_Sln said:

@genieautravail

The ungoogled version has the flags #disable-encryption and #disable-machine-id. Enabling them will disable encryption and machine ID creation, allowing you to transfer your profile to another computer. The developer will not transfer them to the regular version, leaving the functionality completely stock. Therefore, for the regular version, use third-party tools to create a portable version.

I will try these flags today.

Thank you for the tip.

Regards

Edited yesterday at 11:41 AM by genieautravail

[Slavich]

Bugs identified on Windows XP SP3:

1. Sound stutters on YouTube and when switching tabs.

2. Crash when launching Shazam.

3. 1080p YouTube videos stutter.

4. A menu appears with a reminder about the lack of support for Windows XP and Windows Vista (not a bug, but annoying on these operating systems).

5. When switching from one tab to another while listening to the radio online, the speed of the sound slows down, as if it is being stretched.

[ED_Sln]

@Slavich

Shazam has already been fixed. Stuttering and freezing of sound and video on YouTube is usually associated with a weak processor that lacks the power to process 1080 video, especially if it is VP9 and even more so AV1.

[NotHereToPlayGames]

Stuttering and freezing on YouTube is not a "bug".  It's expecting too much of an old processor, an old OS, and backported browsers to NOT stutter and freeze.

There are userscripts that can force h.264 and to force less-resource-hungry resolutions.  Again, expecting too much is not a "bug", it's a "reality check".

Another thing that I find helpful is to *INTENTIONALLY* "throttle" my internet speed.  It does not cause "lags", it forces the streaming service to NOT send me UN-NEEDED 4K.

 

Edited 3 hours ago by NotHereToPlayGames

[mjd79]

On 4/13/2025 at 12:22 AM, mjd79 said:

Edit 06/02/2026:
It looks like newer compiler versions have some problems on non-english OS'es. 

Before running autoninja, type in cmd "setx PYTHONUTF8 1"

Next, in /testing/scripts/common.py, find  
 

try:
    existing_acls = subprocess.check_output(['icacls', acl_dir],
                                            stderr=subprocess.STDOUT,
                                            universal_newlines=True)

and change it to that

  try:
    existing_acls = subprocess.check_output(
        ['icacls', acl_dir],
        stderr=subprocess.STDOUT,
        encoding='mbcs',
        errors='replace'
    )

Also in  build/toolchain/win/midl.py find:

  returncode, midl_output_dir = run_midl(args, env_dict)
  if returncode != 0:
    return returncode

And change it to that:

  returncode, midl_output_dir = run_midl(args, env_dict)
  if returncode != 0:
    return returncode

  # WORKAROUND: Copy MIDL outputs from temp dir to outdir
  for f in os.listdir(midl_output_dir):
    shutil.copy(os.path.join(midl_output_dir, f), outdir)

I have updated my old guide about compiling Chromium. Now compiling is 100% problems-free. I will check what the effect will be with the e3kskoy7wqk patches—he hasn't published the compilation instructions yet, I wonder if, as before, applying the patches and following the standard compilation procedure will be enough.

Edit: Compiling with e3kskoy7wqk working after disabling swiftshader/GLESL tests, but I see it generatings many warnings, probably because he restored old code with methods which triggers warnings in the latest compiler. But it looks like that will work. 22621 SDK is needed.

Edited 24 minutes ago by mjd79

[Slavich]

4 hours ago, ED_Sln said:

Stuttering and freezing of sound and video on YouTube is usually associated with a weak processor that lacks the power to process 1080 video, especially if it is VP9 and even more so AV1.

The developer's browser from the adjacent topic does not have such oddities.