MichaelU wrote: Everyone, we are actively looking into the incompatibility with many versions of InstallShield and Microsoft's recent security update to IE (KB 2962872). Further information and updates will be available on the InstallShield 2014 Sticky. Thanks Michael. I run into the same trouble using InstallShield 2011 Premier. ... View more

GetEnvVar('COMPUTERNAME', svComputerName); or RegDBSetDefaultRoot(HKEY_LOCAL_MACHINE); RegDBGetKeyValueEx("System\\CurrentControlSet\\Control\\ComputerName\\Computername", "Computername", nvType, svComputerName, nvSize); ... View more

Please follow up on this thread, with regard to error 1618 and LaunchApplication. ... View more

Your uninstallParams variable contains a incorrect escape sequence for the log file path. \\ inserts a backslash. Try this code: function UninstallThirdParty(hMSI) STRING szApp, szParams; STRING szTempPath; STRING szLogFilePath; STRING Message; begin GetEnvVar ( "TEMP", szTempPath ); szLogFilePath = szTempPath ^ "test.log"; szApp = WINSYSDIR^"msiexec.exe"; LongPathToQuote (szApp, TRUE); szParams = "/x {10277218-0100-0904-9ABB-000BDB5CF35D} /qn /lv* " + szLogFilePath; if (ISERR_SUCCESS == LaunchApplication(szApp, szParams, "", SW_NORMAL, LAAW_PARAMETERS.nTimeOut, LAAW_OPTION_USE_SHELLEXECUTE|LAAW_OPTION_WAIT|LAAW_OPTION_SHOW_HOURGLASS)) then if (0 == LAAW_PARAMETERS.nLaunchResult) then Message = "Third party completely uninstalled"; MessageBox(Message,SEVERE); else SprintfMsiLog("### LaunchApplication failed: %d", LAAW_PARAMETERS.nLaunchResult ); Message = "Error while third party uninstall"; MessageBox(Message,SEVERE); endif; else SprintfMsiLog("LaunchApplication failed"); endif; end; Info: You should note that you may need elevated privileges to perform the uninstallation. If you trigger the script as a custom action from within MSI based setup you can only run the uninstall during the UI sequence. (SprintfMsiLog does not work from custom actions launched through DoAction events.) ... View more

Have you created a catalog file which contains the digital signature for the driver package as well? If not I would recommend to refer to Signing Drivers for Public Release (Windows Vista and Later). ... View more

Take a look at Specifying the Run-Time Location for InstallShield Prerequisites at the Release Level. ... View more

Just run the setup with verbose logging and search the log file for the term 'DIFXAPP:'. ... View more

Take a look at the What’s New in InstallShield 2008 help topic. LaunchAppAndWait has been superseded by LaunchApplication and WaitForApplication. Maybe that will fix your problem. ... View more

You should also take a look at Rob Mensching´s Windows Installer Components Introduction. ... View more

Try this: Create a new test project and put all driver package related files into a single component. Mark 'This component includes a device driver' at the advanced settings of the component. If you still have trouble post the installation log and some more information about your system and device. ... View more

Take a look at my first post of this thread. ... View more

SMadden wrote: Moin Holger, thanks for looking into the issue. I openeded a support ticket with MS on this and just wanted to give some feedback on the results. The bottomline is that the test case is invalid since the DeviceManager was used to change the devices state. A repair install is only supposed to fix a malfunctioning driver. It is not supposed to change the devices state. This can only be achieved by a reinstall, not a repair. -Sandra Danke für das Feedback, Sandra 🙂 ... View more

I presume you use a pure InstallScript based project type, correct? Which InstallShield version do you use? DIFxDriverPackageInstall updates a currently installed older driver by default if the newer driver is a better match. ... View more

Christopher Painter posted a nice DTF sample to dynamically generate UI content on his blog a while ago. Maybe that´s an option for you. ... View more

Hey Sandra, not sure but it could really be a problem of DIFxApp since DPInst is working fine in the same scenario. I checked the setupapi.dev.log and noticed that SetupCopyOEMInf will be called twice during repair install. The first results with SUCCESS but the second results with FAILURE (0x00000050). Could it be that SetupCopyOEMInf will be called instead of UpdateDriverForPlugAndPlayDevices?!? (just a thought..). -Holger ... View more