The possibility of running modern Chrome, Brave and Ungoogled on Win Vista 64bit with Manifest V2 using tricks.

[Karla Sleutel]

On 6/29/2025 at 6:32 PM, mjd79 said:

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*

Did you try to launch it on Vista with SM files? See if MV2 will also be supported?

[mjd79]

20 hours ago, Karla Sleutel said:

Did you try to launch it on Vista with SM files? See if MV2 will also be supported?

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  

[Karla Sleutel]

13 hours ago, mjd79 said:

kernel33 from extended kernel and advapi32, ole32, shell32, user32 wrappers

 

[Karla Sleutel]

Then I saw an old advice from D.Draker and replaced it with just NtOpenKey. Now I get this.

[Karla Sleutel]

Then I deleted the Supermium wrapper NdDll, and without it I now see NO missing dependencies, but no start nevertheless.

[Karla Sleutel]

On 6/30/2025 at 10:12 AM, mjd79 said:

advapi32 from Supermium 132.

Supermium's advapi misses this api. How do you run it, then?

[mjd79]

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.

Edited yesterday at 01:16 PM by mjd79

[Karla Sleutel]

11 hours ago, mjd79 said:

may need to upgrade it to 2017 EOL

That I can't do, I need to maintain the gaming performance.

BTW, I had managed to start 137. But not 140. And with the old redirection method, WITHOUT SM files at all.

I don't have any EX kernels extensions installed. 

[Karla Sleutel]

Could you help me to run CatsXP, maybe? I could only get up to the 125th version of it.