Karla Sleutel Posted Sunday at 08:11 PM Posted Sunday at 08:11 PM 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 Posted Monday at 05:12 PM Posted Monday at 05:12 PM 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 Posted Monday at 07:30 PM Author Posted Monday at 07:30 PM 13 hours ago, mjd79 said: kernel33 from extended kernel and advapi32, ole32, shell32, user32 wrappers
Karla Sleutel Posted Monday at 07:32 PM Author Posted Monday at 07:32 PM Then I saw an old advice from D.Draker and replaced it with just NtOpenKey. Now I get this.
Karla Sleutel Posted Monday at 07:34 PM Author Posted Monday at 07:34 PM Then I deleted the Supermium wrapper NdDll, and without it I now see NO missing dependencies, but no start nevertheless.
Karla Sleutel Posted 1 hour ago Author Posted 1 hour ago 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?
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now