Software Deployment

For disabling an action you'd have to look in the InstallExecuteSequence table. When you identify the offending CA just give it an impossible-to-meet condition like 1=2.
As for what's triggering the "Add new Hardware" wizard, it could be a rundll commandline triggering the appropriate CPL, or the fact there's still something wrong with the driver signing.

Kr,

PJ

What if you preinstall the drivers?
Does it still come up with the New hardware wizard?

I could deactivate the CustomAction InstDrv in the InstallExecuteSequence Table. It is at position 6605 and doing so prevented the hardware wizard from showing.

Hm, good point.

I will try tomorrow pre-installing the drivers if I can get them off the original package and in which format they are.
Im not a wizard of repackaging drivers hence I have always relied on switches / .ini modifications upon silent driver installations.

Thank you for the tip.

IM_2.08_Setup.exe /S /v"/qn /norestart"

The structure of the commandline arguments (the /v part) shows me the underlying installer is already an MSI.
You should be able to grab that during the install and start from it as a basis. You will have better control of the driver installation actions this way. Have a look in the %TEMP% and %APPDATA% folders of the installing user while the setup is running.

PJ

Yes, Pieter have a good point.
Would probably work even better with the MSI and drivers installed separate (if the drivers are installed outside of the MSI), than installing the drivers and then the setup.

OK,

I cant seem to get this one working.

I can extract all the details out from the MSI using the administrative installation.

I can see that the DPinst64.exe is called at some point cause it pops up the wizdard in context.

However, i cant seem to be able to remove the call to this file from the MSI, i dont know really where to look.
The CustomAction table does not seem to have anything related to calling the DPInst64.exe after successful installation.
How can i prevent DPInst64.exe from being called when the MSI istallation is finished/successful? Where and what should i look?

As a test, you could try temporarily renaming the DPInst64.exe that the installer is calling, then running the MSI with extended logging (/LV*) and seeing which action fails.

Tried that one:

1) Renamed DPInst64.exe to DPInst64xxx.exe (from administrative installation extraction)
2) Launched the MSI (from administrative installation extraction)
3) At beginning of installation: "Error 1308 Source File Not Found" [Cancel][Retry][Bypass]
4) Chosed Bypass so the installation would continue
5) The installation continued without futher errors
6) Log shows that the installation ended without errors! (Return value 0)
x) The only other error is the error 1308 during a:

Executing op: ActionStart(Name=InstallFiles...
Error 1308.Source file not found: Verify that the file exists and that you can access it.

Where does this leave us?
The installer isnt actually calling this file, but something else that launches it? Should that still give us more errors?

Have a look if the DifxAPP merge module is part of the installer perhaps...
Or have a look at the DPInst log file at %SystemRoot%\DPINST.LOG

No trace of DifxAPP.

Good to know the log file location of DPInst.
But opening that log shows that the DPInst did not run during my last installation, when I renamed the EXE.
So renaming DPInst64.exe will cause MSI to popup an Source not found error, but continues successfully on all other parts but the driver part.

So somehow the MSI is launching the DPInst64.exe or something related to this EXE which causes the original "New Hardware Wizard" popup.
I know know how to do all this silently, i would just need to get rid of the popup from the original installer.

Which table should I be examining/altering to drop one action from the installation?

Thank you for your help today.
Ill definately have a look at the table you mentioned tomorrow.

ORIGINAL: pjgeutjens

For disabling an action you'd have to look in the InstallExecuteSequence table. When you identify the offending CA just give it an impossible-to-meet condition like 1=2.



Ok, thats it!

Thank you very much for helping me through this. I couldnt address this problem yesterday, but as I picked it up today
that was the first thing i looked for. There was an installExecuteSequence by the name of "InstallDrv", which i gave an
impossible condition. Result = no hardware wizard pop up.

Now I can install the Software silentely as a stand-alone and the drivers silently as a stand-alone installtion.

Could not have done it without you :)
Cheers and have a great weekend (soon).