Software Deployment

I will answer to this question by myself.
After some kilometers of installer I found out that mentioned registry keys are removed only if the folders registry keys pointed to are empty. I have some log files in those folders, which were created by application not by installer.
I had set my custom cleanup procedure to late in a sequence and therefore during uninstall the folders were not empty.
Consequently, the registry keys remained in a registry.

So, after all the problem was on my side, even that installer made mentioned registry keys.

I saw a lot of this kind of "remained" registry keys in my registry, so I hope I help someone to clear this.

Thanks for all help!

BR,

The simplest way is to populate the RemoveRegistry table. http://msdn.microsoft.com/en-us/library/aa371208(VS.85).aspx

First it's Windows Installer that creates these registry information (Windows Installer metadata) and should be removed automatically by WI during uninstall if the folders are removed during this action.
It seems that the CA isn't working correctly during uninstall thus leaving the metadata behind.

I *was* going to suggest stopping the CA running and instead have the folders created by using the CreateFolders table but decided against it, having judged the OP's level of knowledge from the question.

You're right, of course, Kim. I'd wager that the MSI is one of those which get knocked out quickly by vendors, where install CAs have no corresponding uninstall CA, in this case, to remove the folders created.

Thanks for all answers but I think that nobody give me the right answer.
Once more:
I do not implement and Custom action to create these registry settings. These settings creates installer by itself. I just want to mention that installer leave only keys which have path generated by custom action of type 35 - set directory name.
I also do not have any custom action to remove those keys because, as I said before, installer creates them by itself and I have no control over them.
Do know anybody how to solve my problem?
Thanks in advance.
Andreo

Er, yes we did. Re-read the replies.

those keys because, as I said before, installer creates them by itself and I have no control over them.

If there are just a limited number of regkeys, create a batch file and add commands to delete the regkeys
REG DELETE HKLM\Microsoft\Windows\CurrrentVersion\Unistall\{KEYNUM} /f

no offence AEK but dont follow the previous posts advice.

As VBScab mentioned the removedRegistry table is the better approach.

John,

I don't think Ian's suggestion regarding RemoveRegistry table will work as it will remove during install and the OP wants the registry to be removed during uninstall.

Really? I guess that would be true if the RemoveRegistryValues action were conditioned, but it isn't by default, is it?

My reading is that during an installation, it will remove registry values authored in the RemoveRegistry table if the associated component will be installed. During an uninstall, it will remove registry values associated with components to be uninstalled.

Hi Ian,

Always nice to have a discussion with you [;)]
Allthough I havn't used the RemoveRegistry table for a while so I can't confirm on a proof-of-concept (and don't have the time to test it right now) but according to the SDK:
Remarks
The registry information is deleted from the system registry when the corresponding component has been selected to be installed locally or run from source.

Thanks for all replays fellows.
But my opinion is still that I'm not responsible for those registry keys.
Those registry keys are not created by somekind of Custom Action I implemented!
Registry keys, which I created during installation are removed. Also, I do not talk about folders. They're removed by installer after uninstall, too.

So, I'm talking about registry keys which installer creates in its database (which is by the way in registry under HKLM\Software\Microsoft\Windows\CurrentVersion\Installer) during installation.

What I was able to found out is, that those leaved registry keys points to folders which names are composed (not folders are created!) by Custom Action of type 35. Other folders which names are composed by regular installer properties are removed as well.
I'm not agree with suggestion to use RemoveRegistry table. Why should I use it if I do not create those keys?

Any suggestion?

Thanks in advance.
Andreo

This is bizarre! You asked how you could remove the keys in question. We told you. Now you're asking why you should be responsible for removing them? Who cares?!?

If you want them removed, use the RemoveRegistry table. If you don't want them removed, forget about them. How much simpler could it be?