Installing Certificate Lifecycle Manager fails on Windows Vista

You try to install the Certificate Lifecycle Manager (CLM) client on Windows Vista. You receive the following error message that indicates that the setup was not successful: To have us fix this problem for you, go to the "Fix it for me" section. If you’d rather fix this problem yourself, go to the "Let me fix it myself" section.

To fix this problem automatically, click the Fix this problem link. Then click Run in the File Download dialog box, and follow the steps in this wizard.




Note This wizard may be in English only; however, the automatic fix also works for other language versions of Windows.

Note If you are not on the computer that has the problem, you can save the automatic fix to a flash drive or a CD so that you can run it on the computer that has the problem.

Now go to the "Did this fix the problem?" section.

As a security measure, Windows Installer will not load script engines that are registered in HKEY_CURRENT_USER. As a user-writable store, a typical user can have an elevated installation to run their library masking as a script engine. This occurs if the custom action was not explicitly attributed by using msidbCustomActionTypeNoImpersonate (0x0800). This is an elevation of privileges attack. Therefore, Windows Installer returns error message 2738 or 2739 for custom actions type 6 and type 5, respectively, and returns the following Windows error: To resolve this problem, follow these steps:

1. Make sure that the Vbscript.dll and Jscript.dll files are not registered in HKEY_CURRENT_USER (HKCU). To do this, locate the following registry keys: 
   • VBScript: HKCU\SOFTWARE\Classes\CLSID\{ B54F3741-5B07-11CF-A4B0-00AA004A55E8}
   • JScript: HKCU\SOFTWARE\Classes\CLSID\{ F414C260-6AC0-11CF-B6D1-00AA00BBBB58}
2. Remove these keys if they exist in HKEY_CURRENT_USER.
3. Reregister the Vbscript.dll and Jscript.dll files in the system32 directory from an elevated command prompt by using Regsvr32.exe.

Check whether the problem is fixed. If the problem is fixed, you are finished with this article. If the problem is not fixed, you can contact support (http://support.microsoft.com/contactus) .

This problem occurs on Windows Vista. It has not been reported on other versions of Windows. However, the same problem could occur if the Vbscript.dll and Jscript.dll files are registered in HKEY_CURRENT_USER.