NotHereToPlayGames

Note regarding versions: The regular version will have a file name ending in _rebuild_#. Versions with a file name ending in _ungoogled disables embedded Google APIs in much the same way that "ungoogled-chromium" ( https://chromium.woolyss.com/ ) disables embedded Google APIs. The "ungoogled" version is recommended for those that prefer tighter control over a Google-based browser basically giving special treatment to Google cookies and violating user preference settings. A side effect to this approach (which also exists in "ungoogled-chromium") is that the Chrome Web Store is intentionally broken only in as far as the "Add to Chrome" button is concerned. This is great for those that prefer to manually install extensions as opposed to obtaining from the Chrome Web Store. A workaround to restore the "Add to" button (special thanks to @VistaLover for this solution) can be obtained from here -- https://github.com/NeverDecaf/chromium-web-store Mileage may vary, for me this only added the "Add to" button but clicking it only downloaded the extensions .crx (which I personally prefer anyway) as opposed to 'adding to' 360Chrome. I had similar results with official "ungoogled-chromium" on the official Chrome Web Store (restores "Add to" button but does not actually 'add to'). Special thanks to @Humming Owl for translated .png files. Special thanks to @Dixel for discussions leading towards the "ungoogled" versions. XP x86 SP2: v12, v13, and v13.5 work as-is in XP x86 SP2 but v11 requires special modifications - see this post by @we3fan Download links for starting from scratch with a NEW PROFILE: Regular: https://www.dropbox.com/s/mes4wez1v34w9k4/360ChromePortable_11.0.2031_rebuild_8.zip?dl=1 (last updated: Jan 9, 2022) https://www.dropbox.com/s/wol8va166au2p7j/360ChromePortable_12.0.1247_rebuild_12.zip?dl=1 (last updated: Jan 11, 2022) https://www.dropbox.com/s/6lnst7yp0dt34s5/360ChromePortable_13.0.2206_rebuild_9.zip?dl=1 (last updated: Jan 11, 2022) https://www.dropbox.com/s/8h4z346251wg7r8/360ChromePortable_13.5.1030_rebuild_6.zip?dl=1 (last updated: Jan 11, 2022) Ungoogled: https://www.dropbox.com/s/6z65t5yo08fr0ym/360ChromePortable_11.0.2031_rebuild_8_ungoogled.zip?dl=1 (last updated: Jan 9, 2022) https://www.dropbox.com/s/j5zxk7aqv9ljjjc/360ChromePortable_12.0.1247_rebuild_12_ungoogled.zip?dl=1 (last updated: Jan 11, 2022) https://www.dropbox.com/s/ld5dz2uwdowf1cz/360ChromePortable_13.0.2206_rebuild_9_ungoogled.zip?dl=1 (last updated: Jan 11, 2022) https://www.dropbox.com/s/glulv6r8sce6xpy/360ChromePortable_13.5.1030_rebuild_6_ungoogled.zip?dl=1 (last updated: Jan 11, 2022)

Cool! That works to return the "Add to" button and the Google cookie deletes like it is supposed to when settings say to delete on exit.

That's why I'm now providing two "flavors". Not everybody is going to "like" an 'ungoogled' version - but it is a must for privacy-conscious users and is also why "ungoogled chromium" has a very large user base. It's also why SRWare Iron had a very large following but I've stopped following it, unsure if still updated regularly.

Which version are you using? My rebuild? Russian Repack? Humming Owl rebuild? Chinese original?

It's not against the Chrome Web Store. I have a major problem with any web browser having a "delete cookies on exit" setting that Google builds in its own workaround. If I tell the browser to delete cookies on exit and it does NOT delete a Google cookie, that is BAD! Very, Very Bad! I think the second issue is due to whatever was "locking" those keys yesterday that seems to have gone away on its own.

That's a relief, that is how it is supposed to work -- the key is present when 360Chrome is open, the key self-deletes when 360Chrome is closed. This is true only when ran as "portable" (ie, using the "loader" exe and ini). MUI is normal behavior, unless you jump through some hoops to prevent the OS's default "most used" tracking or clean them out regularly with third-party software. I thought ESENT was related to anti-virus software, not sure. I don't have any ESENT keys in my registry.

It's the same nowadays. Every single one of us ALWAYS has the "excuse" when asked "Why did you take the production floor down three hours?" "Because I was denied my request to take it down for four minutes! Right here is my paperwork request. Right here is my paperwork denial."

Previous build links are now dead. I was running out of room on my Dropbox storage.

ROTFL It cracks me up how often this happens. We have somewhere between 350 and 400 computers on the factory floor and they all have software licences that are purchased two years at a time and all based on when the equipment was purchased. Heck, we have some licenses expire before the machine even makes it through "debug and validation" and yet Engineering puts it into "production" with an EXPIRED license, so I have to immediately shut it down and red-tag it! The software companies will pro-rate the license but we can't get "IT" to go that route (ie, update all 350 to 400 when the factory is shut down for two weeks between model years, pro-rate the first license to coincide with model year changeover). Instead, we end up with random computers across the entire production floor popping up "nag screens" for THIRTY DAYS that a license is about to expire. And an Operations Manager so h#llb#nt on squeezing the turnip that IT can't take the machine offline for FOUR MINUTES to update the license. So we dang near always end up with the license EXPIRING and the machine WILL NOT RUN until that license is updated. Several phone calls spanning multiple time zones and THREE HOURS LATER the machine is back up and running. All because the Operations Manager wouldn't release the machine for FOUR MINUTES. And because "IT" can't see past the nose on their face to schedule ALL licenses to be updated during a two-week shutdown, as if their "job security" is somehow tied to them taking THREE HOURS to run down license updates that we all know only takes FOUR MINUTES. But I digress...

Updated links. Apologies for so many updates in such a short amount of time, these should do for a while. I also still need to apply latest rounds of updates to my v13 rebuild. I've also been looking into XP x86 SP2 but that's more of a back-burner project at the moment. I now have two "flavors" of each rebuild. The "ungoogled" flavor takes the same route as "ungoogled chromium" ( https://chromium.woolyss.com/ ) and intentionally breaks a Chrome Web Store embedded API. The advantage is that this prevents an unwanted Google cookie "local storage persistence" present in all Chromium-based browsers since Chrome v69 (which is what 360Chrome v11 is based off of). The "disadvantage" (to some folks) is that this 'fix' removes the "Add to Chrome" button when visiting the Chrome Web Store. For those not familiar, you don't have to use the Chrome Web Store in order to install extensions. I personally download them from https://www.crx4chrome.com/ then save them locally, edit, then drag-and-drop into the chrome://extensions/ page. There are also extensions available that will download the .crx directly from the Chrome Web Store as opposed to going through the "Add to Chrome" button. Just offering some alternatives... Download links - https://www.dropbox.com/s/vbhhwmhl139clid/360ChromePortable_11.0.2031_rebuild_3.zip https://www.dropbox.com/s/o6fhbaypj2q3i7y/360ChromePortable_11.0.2031_rebuild_3_ungoogled.zip https://www.dropbox.com/s/0ifua74kkb35e2e/360ChromePortable_12.0.1247_rebuild_7.zip https://www.dropbox.com/s/cvnnhqc4r812va5/360ChromePortable_12.0.1247_rebuild_7_ungoogled.zip ps - The only difference between the two flavors is the "resources.pak" file. If you wish to alternate back-and-forth between the two, that file is the only file that you need to swap. Make sure to not criss-cross versions. You can swap resources.pak betweeen v11 rebuild 3 and v11 rebuild 3 ungoogled, but you cannot use the v12 resources.pak with v11 and vice versa.

Finally found a fix for this nuance! Will be incorporated in my next set of uploads.

If that key is not deleting for you, right-click the key (I'm assuming you are using simple regedit to view registry) and select Permissions. Make sure your user account has "permission" to delete that key. You should have a checkmark under "Allow" for the "Full Control" permission. If you don't have that "Full Control" -> "Allow" checkmark, then I can only assume that you have some sort of "security" software that has taken it upon itself to lock you out of deleting that registry key.

I do not have any ESENT entries.

I do not get any popups on any of those links, if that is what you are asking. But remember, I do not allow javascript. I would have to break my own rule of not allowing javascript on a popup test site just to test to see if I get a popup. That would be what is called a self-fulfilling prophecy.

I'm not saying that the entire registry is locked. I'm saying that the ONE KEY is locked - HKCU\Software\360chrome Didn't you say you could not delete the ONE KEY - HKCU\Software\360chrome?

Very strange indeed. I don't know how to see what is "locking" the registry entry from being deleted. You seem to have some "security program" preventing you from deleting that registry entry.

If you have a legit reason for having two, that is one thing, I'm not trying to tell you how to run your own computer. Generally speaking though, it's not really a good idea to have two antivurus programs installed, two popup blockers installed, two script-blockers installed, et cetera. <off topic> Reminds me of my college days. I was not the party-type but some of my friends were. One of my friends would brag to anybody and everybody that he "double wrapped it" for "extra protection". He was the FIRST person that semester to impregnate his girlfriend - despite us all telling him that you DO NOT WEAR TWO!

You have something causing a "lock" then. That is not normal portable loader behavior, something is causing a "lock". Have you rebooted? Does Task Manager verify that 360Chrome is indeed closed?

Why TWO extensions just to block popups? Is that an XP x86 SP2 thing? Are popups that bad on x86 SP2? I swear on all four grandparents' graves (make that five, my dad's mom passed away when I was 3 and grandpa remarried), I haven't seen a popup in over twenty years and I don't have any popup-blocker extensions and I don't even use 360Chrome's built-in setting to "disable popups". Okay, okay, TWENTY years might be a SLIGHT exaggeration. I did just track down one of my installation discs from 2004 (seventeen years ago) where my default browser was GreenBrowser coupled with Proxomitron. The author of Proxomitron passed away in 2004 and I used it long before 2004, I just can't find physical proof via installation media. GreenBrowser used to basically compete with Maxthon and Sleipnir. I went back and forth between Sleipnir and GreenBrowser as my default back then. They were basically "frontends" to Internet Explorer. It gave me TABBED BROWSING long before IE ever introduced it. The company I worked for at the time was hit with a virus that Firefox spread throughout the company network (circa 2006 to 2010, don't recall exactly). My GreenBrowser coupled with Proxomitron - my computer was the only computer in the company (200+ computers spanning 6 midwest facilities) that was NOT hit with the virus [production-level, excluding management and "big whigs").

Does it DELETE and stay deleted if you do not start 360Chrome?

I've already found the culprit for the Web Store. Ungoogled Chromium (v88 tested in Win7 -- https://chromium.woolyss.com/ ) does the same thing, no "Add to Chrome" button! This to me is not a "side effect" but rather a PREFERENCE in much the same way that I always preferred "Ungoogled Chromium" over the "regular" version. I'll see if I can find a different way to prevent the unwanted persistent Google cookie. At the very least, I may have to go a route similar to what https://chromium.woolyss.com/ takes -- two releases, one "regular" one "ungoogled".

That second one is supposed to delete when you exit the browser when using the portable mode loader.ini. Please delete both of those keys while 360Chrome is closed. Launch 360Chrome, keep open for 10 seconds or so, exit 360Chrome. And see if those keys return.

I may end up KEEPING this "side effect" in my own personal-use version, but I will return the Chrome Web Store functionality to the public-use uploaded version. I download .crx files from https://www.crx4chrome.com/, modify locally, then install locally. I never actually install directly from the Web Store. Can you please tell me the key name? HKEY_CURRENT_USER\Software\360chrome is created WHILE the browser is running, but should DELETE ITSELF when the browser is closed.

Same is true for @Dixel's v13. Hmmm... I hope we don' thave to "allow" an unwanted persistent Google cookie when NOT visiting the Web Store just to be able to use the Web Store when we want to use the Web Store.

Bummer, back to the drawing board. Thanks for the update.