ERROR-126

 

Cause 1:

Error 126 means that “The specified module could not be found.”. The install calls the AddPrinterDriver Win32 API function and the Win32 API function returns this error. Usually it happens when the AddPrinterDriver Win32 API call cannot add the printer driver to the system because one or more of the driver files that should be already installed are not present on the system.

 

The system keeps the driver files locked. When you uninstall the printer driver Install Shield will not be able to remove the files, therefore it will prompt to reboot the system. Install Shield will mark the files to be deleted after reboot.

 

It could be that the system was not rebooted, the driver was installed, then the system was rebooted and some files got deleted. It is important to reboot the system each time the setup asks for it.

 

If you are using your own custom installation, make sure that you are copying all of the files to the correct locations specified in the documentation before adding the driver.

 

Cause 2 :

This behavior can occur if either of the following conditions is true:

 

• The %SYSTEMROOT%\System32\Wbem\framedyn.dll file is missing or damaged.

• The Windows Path environment variable does not point to the %SYSTEMROOT%\System32\Wbem folder.

 

SOLUTION

To resolve this issue, use both of the following methods.

Replace the Framedyn.dll File

1. Click Start, and then click Run.

2. In the Open box, type %systemroot%\system32\dllcache, and then click OK.

3. Right-click framedyn.dll, and then click Copy on the shortcut menu that appears.

4. Click Start, and then click Run.

5. In the Open box, type %systemroot%\system32\wbem, and then click OK.

6. On the Edit menu, click Paste. If you are prompted to replace the existing file, click Yes.

 

Verify System Variables

1. Click Start, right-click My Computer, and then click Properties on the shortcut menu that appears. If you receive the following error message, click OK:

rundll32.exe - Unable To Locate Component

 

This application has failed to start because framedyn.dll was not found. Re-installing the application may fix this problem.

2. In the System Properties dialog box, click the Advanced tab.

3. Click Environment Variables.

4. Under System variables, click Path, and then click Edit.

NOTE: If no Path variable is listed, click New. In the Variable name box, type Path.

5. In the Variable value box, type the following:

%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\wbem

Click OK three times (each time that you have the option).