Oct. 17th, 2006

Bad Google

Oct. 17th, 2006 10:40 pm
torkell: (Default)
Dear lazyweb, Edit: problem solved. See next post for solution.

How do I kill the autoupdater in Google Toolbar for IE?


Useful toolbar good. Autoupdater less good. Forced updates bad. Forced update resetting everything very bad. Forced update removing functionality for no good reason extremely bad.


Google's motto needs some work.
torkell: (Default)
Google's autoupdater is a persistent little git, I'll give it that.

The old version of the toolbar is stored as C:\Program Files\Google\GoogleToolbar1.dll. What appears to happen is the updater creates GoogleToolbar2.dll, and registers that in COM. No idea if the old file is deregistered.

Plan A of reregister the old version and hope it didn't notice was doomed from the beginning. The updater saw through that attempt and behaved as normal

Plan B of the same, but then copy the old to where it expects the new and deny writes using NTFS permissions also failed. Instead of creating GoogleToolbar2.dll, GoogleToolbar3.dll was created.

Plan C, however, involves following Plan A and then using NTFS permissions to deny all modifications to the entirety of C:\Program Files\Google.
This appears to be quite successful. The updater can't really do anything if it can't create the new file, or modify or delete the old one. Worst it can do is clobber the registery settings for the toolbar. And that can probably be fixed by applying a similar ACL to HKEY_CURRENT_USER\Software\Google.

Autoupdate that, Google!

January 2026

S M T W T F S
     123
45678910
11121314151617
18192021222324
25262728293031

Most Popular Tags

Style Credit

Expand Cut Tags

No cut tags
Page generated May. 8th, 2026 01:15 am
Powered by Dreamwidth Studios