This could be a problem with merge module. check merge module for said DLL in your repository. Check file vesion and mergemodule version. Its not good practice to leave error as it is even if you are able to install the MSI.
The error is regarding COMCAPTURE.exe, check if dll has any COM data and its not coming through mergemodule(Com data is not getting registered).

I would suggest recapturing of source with exclusion of merge module at capturing state.( You can include later if you want ).

If you want to proceed with same package make sure all the files installed by source are installed by your package(check all attributes of files) and all the registries with key values are same.
You should use clean build for this.

Thank you sir!

I will give this a shot this morning and see what happens.

>I would suggest recapturing of source with exclusion of merge module at capturing state
How does THAT work? Think:

- How would SetupCapture know which components are part of a merge module?
- If a merge module is involved, that means an MSI is involved and that means you ought not to be capturing it in the first place.

I am assuming that the O/P is capturing a non-MSI install and is then being advised that some of the files are available as merge modules and is being offered the option of using these merge modules.
However, there is a good chance that the merge modules are older than the files being captured, so that is the first thing to check. Merge modules are offered if there is a match on the filename, but I don't believe there is much in the way of version checking going on to verify if the merge module files are the same version.

Secondly, the HH activeX is part of the support for reading HTML help files (*.CHM) - and there are various security fixes for CHM files such as not allowing them to be opened from a network location by default. These security updates may be interfering with COM extraction from the activex control, so maybe running WIseCOMCapture.exe against the DLL involved to extract the registration information manually may be a good idea.

Have you considered creating a transform on the pacakge instead? We were able to do all of the post installation config in the MST as well as install all of the patches in a custom action wisescript.