Yes, it's normal. Standard installer/uninstallers packages usually take minimal aspects into account such as only the pre-packaged files and folders. This means removing only the files that the package "could see" as they were directly placed within.


Think about an installer/uninstaller like packing items into a storage unit. The unit already has a bunch of other junk in it (other programs, other registry values, other temporary files) The installer/uninstaller is some random mover hired to do a job. He takes all of the items in front of him, makes a checklist of all of these items and packs them together on his truck (this would be the DVDP Setup file,) then he takes them somewhere and unpacks them into your storage unit (your computer when you install the software,) and leaves.

Not long after he leaves, you go into the unit, open some of the boxes, take things out, and then just leave them laying around in the unit (a.k.a. running the installed program.) Eventually, you decide you want to get rid of "everything that the worker put in" (or uninstall.) The worker comes back with his checklist, packs everything up that he saw, and leaves. But he wasn't told beforehand that the lamps might get taken out of their boxes at some point, so when he takes the box away, the lamps get left behind.  Deleting happens on the file level first before the folder level. If an unexpected file is left behind in a folder, then folder isn't deleted because only empty folders (generally) are supposed to get deleted. Registry values are not created until certain EXE or DLL files are run, so they too are "taken out of the box" items that the worker leaves behind.


Revo Uninstaller (I love the program) is the worker's assistant that takes a lot more care using extra reasoning that goes beyond the "checklist." He looks at the side of the box and sees a picture of the lamp, then obviously the lamp was once in the box and it needs to go as well.

Assuming you are dealing with a program installed the standard way (rather than using RU to first install the program which creates an "image" of the install,) RU looks deeper, hunting for files to see if they even exist. This can have both benefits and disadvantages, especially when deleting files from the registry. While I have had very few problems with RU flagging registry values that I didn't want deleted, it does happen.

I hope this clears things up.

Don't be so quick to rush to judgement. How about just stop and enjoy using the program for its intended purpose for awhile. It might change your perspective, once you start having some fun.

Quoting dtsig:

Quote:
But i guess the theory is to ignore the problems and just use it as it is.

Not at all what I meant. It just seemed that maybe you got caught up a bit in the heat of battle. Based on your extensive background, I think you would gradually get on top of it and sort out the "wheat from the chaff" as they say. But with the flurry of posts and responses, back and forth, I think we all - those of us who are trying to help - got a bit dizzy with details and having some trouble following all the loose ends ...

As you sort out the truly tough problems and formulate some recomendations for Invelos, just go ahead and post those suggestions in the feature requests forum. And you are still a VIP in my book!