Hello,
This may happen if during
"Paths Resolution" action group one of your installation folder is resolved to an invalid path (e.g. "System64Folderwbem\Repository"). So, you can search in your project (CTRL+F) for the related path ("System64Folderwbem\Repository") and see if there is any installation folder set to this invalid path. If so, you should edit it to use a valid resolved path at install time.
As a side note, please keep in mind that the import features in Advanced Installer (the Repackager, the Import MSI feature etc.) are intended to be used to get a starting point for your installation package, not to completely reproduce other installation packages. The Repackager tool captures only the effects of the installation (the changes made on the system). If the original installation package executes custom code (programs, scripts etc.) then only the effect will be captured (registry entries, files and folders etc.). Also, after repackaging an installation some adjustments may be necessary in order to obtain a working installation package.
Let us know if this helped, otherwise please send us the .aip (project file) to
support at advancedinstaller dot com so we can investigate its settings.
All the best,
Daniel
FOLLOW US
Get the latest news in Application Packaging