Hi everyone ,

If i want to delete a key out of the msi database with orca ... i just go to the registrytable and delete the key and then click safe ??? right ??

I removed the key directly into the database ... or should i so a transform first ???


0 Comments   [ + ] Show comments

Answers (3)

Posted by: anonymous_9363 12 years ago
Red Belt
I removed the key directly into the database ... or should i so a transform first ???
That depends. If it's a vendor-supplied MSI (or one which extracts from a vendor's set-up stub), then yes, use a transform. If it's your own MSI i.e. authored by you from scratch or captured by a packaging tool, go ahead and delete it. If the latter, make sure that its component 'container' is removed also, along with the reference to that component in the FeatureComponents table.

One reason why I prefer to use a packaging tool to do this kind of thing is that the tool takes care of ALL the relevant edits so, if I delete a registry entry or file, all the associated tables are adjusted for me. It might not be as quick, but it *is* thorough.
Posted by: Lordeos 12 years ago
Senior Yellow Belt

I used a repack tool "emco package builder" .

Thx for the help
Posted by: dannyarya 12 years ago
Purple Belt

are you got any error?

as you want t delete a reg. key......
1. just go to registry talbe and delete that.
2. if that registry component is contain only this key then delete that component else leave it.
3. In component table check also for the Set Key Path.
4. and also check entry in to FeatureComponents talbe.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ