mjd79

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

On XP only GDI rendering is working. I will try to use DirectWrite. 139 on vanilla Vista SP2 works, but if you run without existing profile, it has some function missing in shell32.dll. Edit: DirectWrite from Supermium working! I can't get working hardware acceleration, even with disabled blacklist and D3D9... All api-ms-win-crt, p_advp32.dll, pwp_shd.dll, p_ole.dll, pwrp_k32.dll, ucrtbase.dll - that's the files needed for working dwrite.dll from Supermium.

https://github.com/e3kskoy7wqk/Chromium-for-windows-7-REWORK He made few reworked versions. It also can support XP and Vista without extended kernels

Delete

I'll check it out (for free ) That's me too. I can send you a modified version of 140 ESR or the latest one.

Yes, also on 8.0

I see that there is a need for a more detailed explanation. You need: Vista SP2 x64 (you may need to upgrade it to 2017 EOL) kernel33.dll from Vista extended kernel v2023-03-09. p_advp32, p_ole, pwp_shl, p_user from Supermium 132 R4. (for convenience you can name them advapi33, ole33, shell33, user33 etc) In the chrome.exe file, change kernel32.dll to kernel33.dll in the import table using CFF Explorer In the chrome.dll file, change the same import. Then open this file in HxD and search for advapi32, ole32, shell32, user32 - they may be in several places, change the ones that are full import table looking like below: In the chrome_elf.dll file, as you rightly pointed out, change NtOpenKeyEx to the NtOpenKey version.

I used kernel33 from extended kernel and advapi32, ole32, shell32, user32 wrappers from Supermium 132. As you can see, for example, ublock works. I didn't need a platform upgrade or an extended kernel installation for this

The first builds of Chromium 140 are available. As expected, flags have been removed and the policies entry in the registry no longer works. But after adding --enable-features=AllowLegacyMV2Extensions --disable-features=ExtensionManifestV2DeprecationWarning,ExtensionManifestV2Disabled,ExtensionManifestV2Unsupported to the MV2 shortcut it still works. We will see for how long, as these are very early compilations. That is Chromium for Windows 7 by e3kskoy7wqk*

Many people use a different system than they have in their profile, or have several computers with different systems.... So reboot12 was right to ask the question.

I described a few posts above what to do. In addition to changing the minimum version in the PE header of firefox.exe, you should swap a few imports in xul.dll and mozglue.dll, and you will be able to run the latest version.

Wrapper of bcryptprimitives (e.g., p_cryptp from Supermium) and kernel32 (e.g., pwrp_k32 also from Supermium). And you can mod this yourself.

https://github.com/ToprakBZK/Modern-Chrome-134-For-Windows-7-and-8.1/releases Be warned, should anyone come across it, it's Blaukovitch's crack LOL My goal for more than a year was to become independent of his solutions when creating my own mods, but unlike that kid, I succeeded....

Sandbox working

I already know what is messing up Chromium 127+ It is the kernel32.dll and kernelbase.dll version checking. I rewrote it to return a false value for them indicating Win 10, and here is the result: The latest versions also use IsWindowArranged from user32, which is absent in 8.1 - possible to be replaced by, for example, IsWindowVisible. Now it remains for me to write my own version of UpdateProcThreadAttribute.