mjd79

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.

Unfortunately, it is not known where it sits, but any attempts to neutralize it have failed. For what it's worth, it's interesting to note that the browser works after replacing it with TraceSetInformation. STATUS_BREAKPOINT without this feature starts at version 133.0.6876.1 from e3kskoy7wqk. I did a thorough search of the entire repository downloaded locally (including all 3rd party components) in 133.0.6876.1 and 6861.0, the use of this function in the code files has not changed at all. My suspicions fall on the dxc generated by mcgen during compilation, but I have no idea what to do about it next. I am currently working on moving patches to version 120.0.6099.338 - one of the longer supported LTS versions. And one thing puzzles me - how the author moved the original commits from 2023 removing support for Win 7 (only that reversed, for that I already have a script) for all of his versions. All the diffs/commits after merging into one file are more than 35 thousand lines of code, and there are about 100 of them. And for most of the files, lines have changed in the meantime, where some code needs to be removed or added, in the case of some, for example, 50 lines. Did he correct it manually? I find it hard to believe... more than 650 files are being changed. I tried manually correcting the hunk, but quickly gave up. I even tried to create scripts that search for given passages in the original files and, based on that, determine new lines to put in the hunki, but that too succeeded for a small number of files.

That is, the breaking of the engine or V8 by author continues. The question is for what reason? The author doesn't have to do anything with it to maintain legacy OS compatibility.

https://github.com/win32ss/supermium/issues/1367 I don't have a github account, so if someone could pass on. Win32ss needs a bcryptprimitives function, specifically ProcessPrng. Supermium doesn't have VMP anyway, so the author can change the import to his own implementation of bcryptprimitives in the patcher anyway. GetProcessMitigationPolicy and SetThreadInformation are also needed, but from what I've seen the author of Supermium certainly knows. Oh, right, I forgot. On Supermium 132, including R3 widevine does not work at all, even on Windows 10, and even more so with the repaired widevine under 7, or with original widevine with VXkex. The world does not end with Netflix, there are many sites that use DRM, for which unnecessary for the author to buy VMP license for Supermium. Works in 126 R7:

Unfortunately, versions 2830.0 and 2380.100 have recently stopped working. For now, my temporary workaround for 4.10.2891.0 on Win 7 is to use pwrp_k32 from Supermium instead of kernel32, an p_cryptp instead of bcryptprimitives. There are actually a few functions missing, so perhaps I will write my wrapper and make it available to the public. That's basically what Mozilla does. https://hg-edge.mozilla.org/releases/mozilla-esr115/log?rev=widevine You can find bcryptprimitives in the widevinecdm.dll file by searching 62 00 63 00 72 00 79 00 70 00 74 00 70 00 72 00 69 00 6D 00 69 00 74 00 69 00 76 00 65 00 73 in hex editor (two occurrences), replace, for example, 62 at the beginning with 78, and name the p_cryptp.dll file xcryptprimitives.dll.

Indeed, the sandbox is fixed. #supermium-tab-options works fairly decently, although v109 mode has minimal bugs (at least on 7 SP1 with Aero).