How do I remove a program from the registry?

[Gary]

If I run regedit and delete the program folder would that work? I'll do a
full backup first.

 

[Ken Blake, MVP]

If I run regedit and delete the program folder would that work? I'll do a
full backup first.

Entries for a program can be all over the registry--sometimes in
hundreds of different places.

Trying to remove them manually is a prescription for disaster.

 

[Shenan Stanley]

If I run regedit and delete the program folder would that work?
I'll do a full backup first.

What is it you are actually trying to accomplish?

 

[Unknown]

Yes, that removes it from the registry.

 

[Pegasus \(MVP\)]

If I run regedit and delete the program folder would that work? I'll do a
full backup first.

This is likely to fail. It's also not a good idea to start a new
thread on an existing post - check the many answers you
have received there.

 

[Unknown]

Why do you say 'likely to fail'? I've done this many times.

 

[Pegasus \(MVP\)]

Why do you say 'likely to fail'? I've done this many times.

Because, as Ken Blake has already pointed out, installation
details can be kept in lots of places in the registry. Unless
you know which key is checked by the program, you're in
for an up-hill battle. For example: I have spent hours trying
to convince a PC that a certain HP printer drive was no
longer installed. I succeeded after deleting each and every
reference to Hewlett Packard (and to HP), and there were
lots of them! In the process I crippled the driver for the
other HP printer that the client had . . .

The OP should use the supplier's removal program, for
which I gave him a link.

 

[Unknown]

Tis unfortunate but Ken exaggerates too much. That simply is not fact.

 

[Donald L McDaniel]

Sometimes this will work. Many times it won't. Depends on how
"complicated" the program is and whether it leaves hard-to-search-for
keys or not. Simple programs usually may be uninstalled this way.
Low-level utilities almost always are not removable by first deleting
the program's folders, then using the Registry Editor to remove its
keys.

Entries for a program can be all over the registry--sometimes in
hundreds of different places.

And many times without leaving any references to the actual program,
its files and folders, or its OTHER registry keys.

Trying to remove them manually is a prescription for disaster.

Agreed.
Example: Try removing a version of Norton AV sometime by searching for
keys from within Registry Editor. You will be doomed to failure, for
sure.

Many times, files/folders/keys necessary for a program's removal will
still be locked by the OS, since references to them would still in be
user memory. This is why some uninstallers require you to reboot
after the uninstallation, to remove these locked files/folders/keys.
It is always a good idea to remove programs from memory before
attempting their uninstallation, if possible.

Use a good-quality XP-compatible Registry cleaner instead.

Many will allow one to remove such programs when they are not
removable using "Add/Remove Programs" or their registered
uninstallers.

Some are free, some cost a nominal fee. And some work better than
others. I've found that "JV16 Tools 2008" (not a free tool) is an
excellent tool which almost always succeeds in removing such
unremovable programs with little or no trouble.


Donald L McDaniel
Please reply to the original newsgroup and thread.
========================================================

 

[Donald L McDaniel]

Tis unfortunate but Ken exaggerates too much. That simply is not fact.

Whenever possible, of course. Many times it just isn't possible.
For instance, for a few years, it was not possible to uninstall
WindowBlinds (from Stardock.com) using its safe uninstaller, since the
uninstaller was placed in the WRONG FOLDER, and it could not be found
by the OS. Also, sometimes the uninstaller may become "broken", and
for that reason, would be unusable.

Sorry, bud, but Ken's advice is in no way "exaggeration". It is
"gospel truth", as many have found.

Vista's uninstallation routines are much improved, but developers
STILL put keys and files all over the place, where they cannot be
found by Registry Editor, no matter HOW HARD you try.

XP's uninstallation routines were not exactly the best, either.

An OS can't always do everything one wants, no matter how strongly he
desires it. PERIOD.

If a programmer doesn't use "standard" installation practices, the OS
cannot make up for his faulty code.


Donald L McDaniel
Please reply to the original newsgroup and thread.
========================================================

 

[ANONYMOUS]

You can try this MS tool. I have found it very useful:

http://support.microsoft.com/kb/290301

Once you have used it, you will need to delete all the folders which are
likely to be on the HD. Read the instructions first.

hth

 

[Bill in Co.]

It all depends. For a small program, it is possible, in some instances.
But for a larger program, forget it - it's hopeless. As in: it's a
Herculean Task. (and a really clear example of this would be Offfice -
LOL)

 

[Nonny]

It all depends. For a small program, it is possible, in some instances.

Is that your "definitive" answer for small programs? I notice you do
a lot of fence straddling.

 

[Bill in Co.]

Is that your "definitive" answer for small programs? I notice you do
a lot of fence straddling.

I don't straddle fences, but, I do try to cover most bases, based on my
experiences.

What I'm saying is: you can successfully do it for some programs, but you
cannot for others. (There is NO way you could do it for Office - for an
obvious case).

Just as I have also talked about using the "right tool" for the "right job",
when comparing the efficacies and advantages of using, say, ERUNT , vs
System Restore, for restoration.

So, is there a one sentence, simple-minded, answer, that definitely defines
either? Nope. No way.

It comes from experience. And, (bottom line), it ain't usually answered
properly in one simple sentence (with few exceptions).