W
Wolf K
AFAIK, all the keys are grouped by program name, since that is whatAh, so it can only run being given a name. (IME, some softwares putGene E. Bloch said:On 5/14/2013 6:03 PM, J. P. Gilliver (John) wrote:
In message <[email protected]>, Gene E. Bloch
On Sat, 11 May 2013 11:47:57 +0100, J. P. Gilliver (John) wrote:
What has been puzzling me for some time, is how Revo - or any
similar,
but this one seems to get the most praise - _knows_ what it can and
can't remove. Short of doing a reinstall and monitoring it, so
that it []
No. When the program's own uninstaller finishes, Revo just looks
through
the registry and the file system looking for things it recognizes as []
But how does it do that "recognising"? []
Well, to judge from results, it looks for the folder(s) and registry
keys with the program's name. Basically, it runs an automated regedit.
things - both registry entries and folders - under the name of the
software house, sometimes without the name of the actual prog. - and of
course sometimes under names that contain neither of those.)
Windows needs. *.dlls called by the program will be grouped in the
program folder. I would expect AppData to be used, too.
Of course, if program installation and uninstallation were done
properly, we wouldm;t need 3trd party uninstallers, and we wouldn't be
making inferences about how they work.
Same as you would when you look for left-over folders, or a registry[]+1
Your first two sentences are exactly what I was planning to say
The same question: how does it know what it can remove? (Just by hoping
there are name connections?)
cleaner that looks for broken dependencies, etc.
HTH