mjd79 Posted April 14, 2025 Posted April 14, 2025 (edited) The patcher included by e3kskoy7wqk, along with the diff files for each compilation (a total of 5 apply_patches.bat files), require a bit more correction than the author claims. At “REPO_PATH=E:\win7dep\chromium\src” change the path to yours, of course, but besides that, you also need to replace “!REPO_PATH!” with “%REPO_PATH%” in two places. In addition, it is required to add clang_use_chrome_plugins = false to args.gn. Edited April 14, 2025 by mjd79 3
mjd79 Posted April 16, 2025 Posted April 16, 2025 (edited) Unfortunately, Chrome Sync still does not work after adding Google API keys, you still need OAuth2 keys. As a not being a Chromium developer, you can only use the default keys, which can be added with the --oauth2-client-id and --oauth2-client-secret flags. There is a simple solution for this, so that you won't have to add flag it to shortcuts or in the registry (in case you set it as default browser) void ChromeMainDelegate::PreSandboxStartup() { base::CommandLine& command_line = *base::CommandLine::ForCurrentProcess(); std::string process_type = command_line.GetSwitchValueASCII(switches::kProcessType); if (!command_line->HasSwitch("oauth2-client-id")) { command_line->AppendSwitchASCII("oauth2-client-id", "77185425430.apps.googleusercontent.com"); } if (!command_line->HasSwitch("oauth2-client-secret")) { command_line->AppendSwitchASCII("oauth2-client-secret", "OTJgUOQcT7lO7GsGZq2G4IlT"); } With this code, replace the PreSandboxStartup() function in the chrome_main_delegate.cc file. Edit: in testing/variations/fieldtrial_testing_config.json there are flags about TabStripComboButton and disabling MV2 support. They override the default values declared in the corresponding files, hence you need to remove them from this json. Edited June 2, 2025 by mjd79 3
Klemper Posted April 17, 2025 Posted April 17, 2025 On 4/16/2025 at 7:30 PM, mjd79 said: Unfortunately, Chrome Sync still does not work after adding Google API keys, So! It's basically Ungoogled, right? No more need to apply patches @NotHereToPlayGames asked you to apply for him several posts before? 2
Klemper Posted April 17, 2025 Posted April 17, 2025 @mjd79have your ever tried --memory-pressure-off ? 2
mjd79 Posted April 17, 2025 Posted April 17, 2025 (edited) On 4/17/2025 at 9:38 AM, Klemper said: So! It's basically Ungoogled, right? No more need to apply patches @NotHereToPlayGames asked you to apply for him several posts before? No, any pure Chromium lacks API keys and OAuth2, I remind you that I only applied e3kskoy7wqk patches to the completely original Chromium. I have not tried this flag, I will check it under Win7, on which, of course, my rebuilts work. Edited February 8 by mjd79 2
Klemper Posted May 13, 2025 Posted May 13, 2025 On 4/18/2025 at 6:24 PM, mjd79 said: I probably also already know how to use YY-Thunks, which will allow us to run this on Vista. Looking forward to it! EventSetInformation is a Win8 telemetry function. Can block it completely. https://learn.microsoft.com/en-us/windows/win32/api/evntprov/nf-evntprov-eventsetinformation 2
ED_Sln Posted May 27, 2025 Author Posted May 27, 2025 Firefox 139.0 https://github.com/e3kskoy7wqk/Firefox-for-windows-7/releases/tag/139.0
Karla Sleutel Posted July 3, 2025 Posted July 3, 2025 @ED_Sln, in 137 Hints are still there. Look. The flag doesn't work, again. Did it, ever? 1
Karla Sleutel Posted July 3, 2025 Posted July 3, 2025 (edited) Clear data on exit. The flag doesn't work, cookies are still being left, just discovered. UPD. Never mind, started working after several re-launches. Edited July 3, 2025 by Karla Sleutel
Karla Sleutel Posted July 6, 2025 Posted July 6, 2025 brought back manifest v2 extension support. Cool! https://github.com/e3kskoy7wqk/Chromium-for-windows-7/releases/tag/140.0.7275.1 3
EliraFriesnan Posted November 14, 2025 Posted November 14, 2025 On 3/20/2025 at 6:16 AM, ED_Sln said: I just now saw, there is a build for Vista, try it, maybe it will work on 7 without SP1: https://github.com/e3kskoy7wqk/Chromium-for-windows-7/releases/tag/136.0.7063.0 Thanks! On a fresh Vista SP2 Net 4.6.2, it doesn't load at all. debug.log [1114/123040.823:ERROR:main_dll_loader_win.cc(138)] Failed to load Chrome DLL from C:\Chromium\134.0.6998.165\chrome.dll: The parameter is incorrect. (0x57)
ED_Sln Posted November 15, 2025 Author Posted November 15, 2025 18 hours ago, EliraFriesnan said: Thanks! On a fresh Vista SP2 Net 4.6.2, it doesn't load at all. 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. 1
EliraFriesnan Posted November 15, 2025 Posted November 15, 2025 2 hours ago, ED_Sln said: --no-sandbox parameter. That I did right from the start, nothing changed. 2 hours ago, ED_Sln said: especially the Platform Update. Platform Update, you mean KB2117917, KB971512, yes I have those. Also Nvidia driver.
ED_Sln Posted November 15, 2025 Author Posted November 15, 2025 6 hours ago, EliraFriesnan said: Platform Update, you mean KB2117917, KB971512, 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? 1
EliraFriesnan Posted November 16, 2025 Posted November 16, 2025 On 11/15/2025 at 2:41 PM, ED_Sln said: all versions of C++ Made no difference. On 11/15/2025 at 2:41 PM, ED_Sln said: Does version 136 give the same error? Yes.
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