Error Message When You Attempt to Install Program Using Windows Installer


When you try to install a product on a computer running Windows NT 4.0 and Windows Installer starts, you may receive one of the following error messages:
  • The Windows Installer service failed to start. Contact your support personnel.
  • Error 1631: The Windows Installer service failed to start. Contact your support personnel.
  • Internal Error 2755: Please contact product support for assistance.
After you receive the error message, the installation quits.


This behavior can occur when you try to install a program that is installed using Windows Installer. The following registry key contains a value of data type REG_EXPAND_SZ, and the string is null:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment
Userenv.dll returns an error message when it tries to process the value, and Windows Installer quits. The following example shows a null value:


A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem.

To resolve this problem, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English-language version of this fix should have the following file attributes or later:

Date Time Size File name Platform
1/18/2000 3:47p 76,048 Userenv.dll Intel
1/18/2000 3:47p 123,664 Userenv.dll Alpha


To work around this behavior, remove null environment variables before you install the program.

NOTE: The potential impact of removing such variable is unknown at this time.


Microsoft has confirmed that this is a problem in Windows NT 4.0.