Consultancy needed on repackaging application

While reviewing a repackaging application we noticed that the repackager does not sort all the com registration keys in the correct component. When the repackager is not able to sort the registration with the correct component, it adds the key to a component with all other classes root keys that it cannot sort out. This component gets the attribute leave installed on uninstall, so these keys are'nt removed from the system. What do you think of this method? The advantage is that since the keys aren't removed , the system cannot be broken on uninstall, the disadvantage is that orphan registry key are left on the system, since the dll's that were registered by these keys, are removed by the system. Does this have a significant impact on the system or not. Perfomance loss. The repackaging tool is used by several clients an aparently the vendor does not receive complaints from the system administrators that are using the application. For your info, the repackaging application opts to use nor the selfreg table, nor the classid, typelib or progid table to contain registration , because they below you have the least trouble with registation in the "registry table" Merge modules are added when they have a perfect math of the merge module files and files in the msi.