Thank you for being a valued part of the CNET community. As of December 1, 2020, the forums are in read-only format. In early 2021, CNET Forums will no longer be available. We are grateful for the participation and advice you have provided to one another over the years.

Thanks,

CNET Support

General discussion

Does Unistalling Software also Unistall Updates/Patches?

Aug 18, 2005 1:55AM PDT

If I download/install an update/patch for a particular software and then later uninstall that software, will the update/patch also uninstall along with it? And, if so, does the whole update uninstall or might there be bits and pieces of it still lurking in various parts of Windows (registry, etc.)?

Thanks in advance.

Discussion is locked

- Collapse -
Not assured. Example.
Aug 18, 2005 2:05AM PDT

For example Windows Media Player updates are often install only without any uninstall method. Sometimes a shared component is installed so that doesn't get rolled back out.

Since this is now a common practice for Windows (Linux and Macs will differ) I'll write no.

Bob

- Collapse -
Uninstalling software
Aug 18, 2005 2:09AM PDT

When you uninstall software, the updates and patches should be uninstalled also. But if the program, or its uninstall program, is poorly written, this may not be the case.

It is not at all uncommon for programs to leave bits and pieces around -- .dll files, documents, .ini files, etc. -- and yes, registry entries. These can be a real pain.

Frank

- Collapse -
Uninstalling
Aug 18, 2005 3:30AM PDT

The question is - why should that bother you? There is so much garbage in any registry and dll files that a little more may not hurt. Unless it conflicts with something else, and then you have to be specific - what happens that did not happen before and do you think that it is the result of the program not having uninstalled completely. Amos.

- Collapse -
Why be bothered?
Aug 19, 2005 2:57AM PDT

Because 1) the effect of accumulated bits of junk in the registry is similar to the accumulation of junk files on the drive; it interferes with the smooth, speedy operation of Windows. The slow-down for a single registry access may be miniscule, but because the registry is accessed so frequently, the aggregate is more significant.

And 2) Because of possible conflict with other operations. Things may work OK for a while, and then you load another program -- whoops, that new program does not work properly. Now you must spend time troubleshooting, and then perhaps find you need to clean something out of the registry.

IMHO registry maintenance should be just as much part of system housekeeping as is disk maintenance. You routinely run anti-malware programs, Disk Cleanup, Defrag, and/or other such programs; why not include a Registry maintenance program as well -- it isn't much effort.

Frank

- Collapse -
Why not in this instance
Aug 20, 2005 2:41AM PDT

Frank, I always bow to those of superior knowledge, especially someone who has preceded me by ten years in the computer world. I do accept registry cleaning as a necessary routine. But going after a single program that seems not to have uninstalled completely, looks to me like wasted effort on a cost/efficiency basis. I usually let sleeping dogs lie, between clean-ups, and my total boot-up time is around 50 seconds for an XP Pro with SP2 and more than 100,000 files. This does not sound too bad, does it? Amos.