having an issue using the install shield device driver wizard

i have recaptured a package and put once i have built my msi i have ran installshield and edited the msi and ran the device driver to include 3 folders which have .inf files in for the drivers.

on doing this and saving my msi, it then fails to launch 1603

nothing in the logs to suggest what is causing this

but is the msi going to try looking for the device driver files in the location i gave it or does it embed them into the msi?


im confused as to why it isnt working and dont know hot to trouble shoot it as i need the drivers in this package


NB if i revert to the msi i created with no drivers it works fine

I can also create the driver package separately and it works on its own

so something the repackager is capturing is either preventing it or it doesnt like the admin studio created msi, i dont really want 2 msi's per application, i have noticed an issue with unsigned driver, does anyone know of a command to suppress the unsigned drivers? or to sign the drivers so it goes away as i think thats the issue



0 Comments   [ - ] Hide Comments


Please log in to comment

Community Chosen Answer



There is an option to force into legacy mode on the driver wizard, but this will only work for XP and below. If you need to sign the driver yourself, there is a very good how-to here: http://www.itninja.com/question/guide-to-signing-unsigned-drivers

Answered 12/10/2012 by: dunnpy
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity



Have this same problem.  KACE's consensus is that the msiexec.exe file is corrupted and needs to be reinstalled/reregistered, which I am in the process of testing this morning.  Just a pain in the butt when the machine having the problem is a hundred miles away.

But I wonder if it's just an XP problem.  Might take a look at this:




Answered 12/10/2012 by: gcarpenter
Green Belt

Please log in to comment