Hi!
I was testing Google Chrome 31.0.1650.57 stable, and found it doesn't delete all added Registry Keys after closing the browser.
Here is RegShot's log after first run:
----------------------------------
Keys added: 8
----------------------------------
HKU\...\Software\Google
HKU\...\Software\Google\Chrome
HKU\...\Software\Google\Chrome\BrowserCrashDumpAttempts
HKU\...\Software\Google\Update
HKU\...\Software\Google\Update\Clients
HKU\...\Software\Google\Update\Clients\{......}
HKU\...\Software\Google\Update\ClientState
HKU\...\Software\Google\Update\ClientState\{......}
This one is after closing the browser:
----------------------------------
Keys deleted: 5
----------------------------------
HKU\...\Software\Google\Update
HKU\...\Software\Google\Update\Clients
HKU\...\Software\Google\Update\Clients\{......}
HKU\...\Software\Google\Update\ClientState
HKU\...\Software\Google\Update\ClientState\{......}
So, three first keys are not removed.
Same happens with version 33.0.1712.4 Dev
I also tested a backed-up old version 29.0.1547.66, and this one works fine (it deletes all created keys on exit).
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
They may have changed the class id for the new version. What is the actual number shown in the {....} for you?
Sometimes, the impossible can become possible, if you're awesome!
The number is the same as previous versions {8A69D345-D564-463c-AFF1-A69D9E530F96}
If I compare registry changes of v.29, this one did not create this "chrome" sub-keys, as v.31 does:
HKU\...\Software\Google\Chrome
HKU\...\Software\Google\Chrome\BrowserCrashDumpAttempts
For example, here is the log of Google Chrome Portable 29.0.1547.66
First Run:
----------------------------------
Keys added:10
----------------------------------
HKU\...\Software\Google
HKU\...\Software\Google\Common
HKU\...\Software\Google\Common\Rlz
HKU\...\Software\Google\Common\Rlz\Events
HKU\...\Software\Google\Common\Rlz\Events\C
HKU\...\Software\Google\Update
HKU\...\Software\Google\Update\Clients
HKU\...\Software\Google\Update\Clients\{8A69D345-D564-463c-AFF1-A69D9E530F96}
HKU\...\Software\Google\Update\ClientState
HKU\...\Software\Google\Update\ClientState\{8A69D345-D564-463c-AFF1-A69D9E530F96}
Log after close:
----------------------------------
Keys deleted:10
----------------------------------
HKU\...\Software\Google
HKU\...\Software\Google\Common
HKU\...\Software\Google\Common\Rlz
HKU\...\Software\Google\Common\Rlz\Events
HKU\...\Software\Google\Common\Rlz\Events\C
HKU\...\Software\Google\Update
HKU\...\Software\Google\Update\Clients
HKU\...\Software\Google\Update\Clients\{8A69D345-D564-463c-AFF1-A69D9E530F96}
HKU\...\Software\Google\Update\ClientState
HKU\...\Software\Google\Update\ClientState\{8A69D345-D564-463c-AFF1-A69D9E530F96}
Ah ok, they switched the keys themselves, not the class id. That makes sense. Surprised no one picked this up while 31 was in Dev or Beta. Makes me think no one is actually testing those branches in the portable channels so they may not be serving much purpose.
I'll rework the launcher to adjust it to these new keys.
Sometimes, the impossible can become possible, if you're awesome!
It's a single new crash key and the associated parent keys left behind. I've got a fix prepared that will go out with the next releases. You can grab the fix here [obsolete patch removed] to try it out.
Sometimes, the impossible can become possible, if you're awesome!
I've tested the fix, and it works fine (v. 31.0.1650.57 stable and 33.0.1712.4 Dev).
But first, I have to manually delete the empty key "HKU\...\Software\Google" that previous version leave.
Thanks!
We can't go back and remove that key that was already there without risking doing it from a local Chrome install. We could add extra logic to check for it, but the key being there doesn't harm anything and won't affect a local install you run later or another portable install.
Sometimes, the impossible can become possible, if you're awesome!
This is fixed in all 3 channels as of Stable 31.0.1650.63, Beta 32.0.1700.31, and Dev 33.0.1726.0.
Sometimes, the impossible can become possible, if you're awesome!