Errors with captured WinSCP.MSI

Created IRP from capture of running the setup.exe
Created ISM from IRP without making any modifications
Created MSI from ISM

I'm new to packaging but my thinking was the behavior of installing the MSI should mirror that of the executable, which installs fine. Running MSI renders two errors during installation.

Error 1401. Could not create key.
\SOFTWARE\Microsoft\Windows\CurrentVersion\Group\Policy\ServiceInstances\ b0xxxxx-xxx-xx. Verify that you have sufficient acces...


Error 1406. Could not write value ActiveShutdownDCL to key
\SYSTEM\CurrentControlSet\Control\Diagnostics\Performance.  Verify that you hav...

I can drill down in the transform to where they reside but don't know how to manipulate them - see below screenshots. So, my question of course is how to manipulate the key and create the other key? I'm using Installshield Admin Studio transform. Thank you in advance!

2 Comments   [ + ] Show comments
  • Ok, so I can't include screenshots apparently. Path to Error 1406 in transform as follows:
    * Name= ActiveShutdownDCL
    * Data =[System64Folder]WDI\LogFiles\WdiContextLog.etl.002
    * Component = RegistryData_HKLM

    Path for Error 1401 in transform as follows:

    In ServiceInstances, there is a folder with a "plus" sign on it, not next to it - does not expand or go away when you click on it. Right clicking on the folder (very long alphanumeric string) shows that it has a checkmark next to "install only".

    Any help in getting these errors resolved is very much appreciated. - rcooder 6 years ago
  • We make final adjustments to an MSI with a transform. We also use it for branding. I'll go back and try what you suggested and comment back with my results.
    Thank you! - rcooder 6 years ago
    • I suggest you use a "deployment" script for branding (also good to create a generic interface between deployment tool and package) as this decouples packages from the deployment tool / environment. - Pressanykey 6 years ago

Answers (2)

Posted by: Pressanykey 6 years ago
Red Belt
I suggest that you refine your exclusion list before capturing anything. the best way to do this is "capture" a running system, perhaps opening a couple of the built in windows apps (open a command window, start mspaint etc.). then carry out  a reboot and the resulting capture add those things to the exclusion list. Once you have done this a couple of times, your exclusion list should be pretty good.
Once your exclusion list is up to scratch, then you can capture your application. Remember you should clean up the capture before creating your capture project, which in turn should also be cleaned up. This should give you a pretty good msi to deploy.

Explicitly for the problems you mentioned, it appears that you are attempting to create / write to the policies registry key, which should not be part of WinSCP. That needs to be removed from your ISM project. The same applies to the diagnostics registry key. If you create a good exclusion list (which would exclude these entries anyway) you would not have the problems you are describing.

BTW, you mentioned a transform... if have you captured the legacy installation, why do you have a transform?

Posted by: Badger 6 years ago
Red Belt

Yeh, you definitely need to a bit of a clean up on your capture.

You might also benefit from making some changes to your packaging machine. Another little trick is to get that capture done as quick as possible, don't answer the phone, don't switch screens to send an email..... every moment that capture is running on an OS, things are happening. More things to look at and exclude

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login


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