PDA

View Full Version : Irritating IE homepage problem with TT



DaveMidgley
2006-09-18, 12:07
If I change the home page setting in Internet Explorer, Teatimer gives an "important registry change" warning every time I boot up following the change. The only way I can stop it is to disable teatimer, reboot, make the change and then reenable teatimer. Is this a bug? It's not exactly life-threatening, but it's really irritating!

md usa spybot fan
2006-09-18, 15:01
The cause of the problem is because TeaTimer's snapshot files are out of sync with the registry. TeaTimer takes snapshots of Registry entries and compares these with the Registry at startup. Until these snapshots are updated you are likely to get pop-ups (at startup) of changes you made in the past. In other words, TeaTimer attempts to return the Registry to the state it was in when the snapshots were taken.

I believe that the reason that snapshot files get out of sync with the registry is because when TeaTimer starts the snapshot files are read into memory and maintained there. The snapshot files only appear to be rewritten when TeaTimer closes. During system shutdown (or restart) it appears that TeaTimer is terminated before it has a chance to rewrite the snapshot files and therefore they are out of sync with the registry if changes have been made to the registry.

The solution to the problem is to refresh TeaTimer's snapshot files after making changes to the registry such as changing your home page. There are two ways to do this:Refresh TeaTimer's snapshot files:
Right click Spybot's TeaTimer System Tray Icon > click Exit Spybot-S&D Resident.
TeaTimer closes.
TeaTimer's snapshot files are refreshed at this time.

Restart TeaTimer:
Using Windows Explorer, navigate to C:\Program Files\Spybot - Search & Destroy.
Double click TeaTimer.exe to start it.

Manually exit TeaTimer immediately prior to system shutdown or restart.

DaveMidgley
2006-09-18, 16:28
Thanks, that seems to have done the trick, although it's odd that it only seems to be the IE home page - I've never noticed it happening on other registry changes.