Q107052: ERRDOC: Run-Time Error 1608
Retired InstallShield Versions
Project Type
Basic MSI, InstallScript MSI

When an InstallShield setup is launched, the following error occurs:

"Error -1608: Unable to create InstallDriver instance"


Little information is known at this time about the specific cause of this initialization error because it rarely occurs and is typically encountered on an intermittent or machine-specific basis. Some known causes for this error are as follows:

  • Windows 98 machines do not have Microsoft DCOM98 installed properly
  • DCOM permissions are not set to an adequate level
  • The InstallScript engine was not installed properly
  • The operating system has become corrupted
  • An older version of InstallShield Developer is being used
  • Other applications or utilities are running in the background and causing a conflict
  • Insufficient privileges in Windows

This error no longer occurs in InstallShield 12 or later. The architecture in InstallShield 12 and later has several advantages over the earlier architecture:

End users no longer encounter error 1608, or other COM/DCOM run-time errors that are related to finding the running IDriver.exe file. When these errors occurred under the earlier model, they were difficult to resolve, often requiring changes to DCOM settings. Also, the reliance on the running object table made the model brittle across the spectrum of usage scenarios, including Fast User Switching and Windows Terminal Services.

The following options have been known to resolve this error message in the majority of cases:
  1. Reinstall the InstallScript engine by running the "isscriptx.msi" file located in the following location, where x is the version of InstallShield being used:

    <InstallShield Installation Location>\Redist\Language Independent\i386

    Example: The InstallShield 11.5 InstallScript engine is called "isscript1150.msi".

  2. Upgrade to InstallShield 12 or later.  These latest versions replace IDriver.exe with ISSetup.dll which will avoid this error entirely.  More information on the latest version available can be found at our Support page.

  3. Delete the folder <PROGRAMFILES>\Common Files\InstallShield\Driver, and run the InstallShield setup again to recreate this folder.

  4. Manually register the file "IDriver.exe" using the following command line:
    <PROGRAMFILES>\Common Files\InstallShield\Driver\<VERSION>\Intel 32\IDriver.exe /REGSERVER

    <VERSION> contains the version of InstallShield that is installed.

  5. Reset the DCOM permissions by following these steps:

    1. Launch the utility DCOMConfig by typing "dcomcnfg" in the Windows Run dialog.

    2. Select the Default Security tab.

    3. Click the Edit Default button in the Default Access Permissions section.

    4. Make sure you choose Allow Access permissions.

    5. Click OK in the utility, and re-run the setup.

  6. Empty all temporary folders. The specific temporary folders for a machine can be determined by accessing the DOS prompt and typing "set". Note the values listed for "TEMP" and "TMP", and delete all files in those locations.

  7. Make sure no other applications, including utilities such as virus scanners, are running in the background. Close all running applications and utilities, and launch the InstallShield setup again.

  8. If this occurs on a Windows 98 machine, install Microsoft DCOM98 from the link below, and re-run the setup:
  9. Make sure you have full administrative rights for that particular system.

  10. Reinstall the operating system, as this behavior has been known to occur when an environment has been corrupted.

Additional Information

If the error message also includes a negative number, such as "-2147467262", more information on this error code may be found by inserting the following InstallScript code into your script:

MessageBox( FormatMessage( -2147467262 ), 0 );

This code translates the error code into meaningful text, which may assist in narrowing down the source of the problem.

Note: Some error codes do not contain meaningful text, and therefore the MessageBox may appear blank in these rare situations.

Last Modified Date: 10-23-2012ID: Q107052