ED_Sln

There is a second link to mini_installer.exe, which is a browser.

@EliraFriesnan The developer replied: https://github.com/e3kskoy7wqk/Chromium-for-windows-7/issues/70 The browser he linked to runs even on XP, but it is x64.

I created Isuue. Now we just have to wait for the developer's response.

Was telemetry added to Vista? Write KB, I'll check what these updates are. Maybe there's something important there. Because I installed all the updates that are available.

No, there shouldn't be any problems with that processor. I thought that maybe you have a processor without SSE3 and that's why it won't start. Then you need to write to the developer. Even though he no longer supports Vista, he may be able to tell you what the problem is.

What kind of processor do you have?

Supermium 138 opened without errors.

Yes, I'm talking about them. Well, then I don't know what else might be needed. I have all the updates installed, as well as all versions of C++ and Net 4.6.2. Does version 136 give the same error?

You need to download chrome.packed-vista.7z and run it with the --no-sandbox parameter. Everything is written there. If this is done, then some updates may be missing, especially the Platform Update.

Yes, and versions ESR 128.14.1 and 140.5.0 have already been released.

Does anyone know what happened? The repository on GitHub is archived, and the website is down.

It also works, but after launching it sets the timer to 2 ms, after launching the browser it switches to 1 ms, and after closing the program it remains at 1 ms.

I'm not sure if that's it. It mentions an ACPI timer, but this thread is about HPET, which doesn't depend on the processor frequency and is measured in milliseconds rather than megahertz.

No, you cannot set a different value. As far as I know, these values are hard-coded into the OS kernel, and you cannot set a value lower than 1 ms.

If it starts using more memory than it has and the OS has to constantly dump the excess into a swap file, then yes, this can cause it to run unstable. Increasing the available memory should fix this, because each tab will be able to use 2 GB of RAM.