Windows Installer package does not install correctly on a Windows 2000-based server that is running Terminal Services in Application Server mode

Article translations Article translations
Article ID: 834878 - View products that this article applies to.
This article has been archived. It is offered "as is" and will no longer be updated.
Expand all | Collapse all

On This Page

Symptoms

When you install a Microsoft Windows Installer package on a Microsoft Windows 2000-based server that is running Terminal Services in Application Server mode, the Windows Installer package does not install correctly. HKEY_CURRENT_USER registry settings that are added by the Windows Installer package do not appear in the
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Terminal Server\Install\Software
registry subkey as expected.

Cause

This problem may occur when all the following conditions are true:
  • You are running Terminal Services in Application Server mode.
  • A program or a service uses the LoadUserProfile function to load the System account profile.

    Note The System account has a security identifier (SID) of S-1-5-18.
  • You install a Windows Installer package on your Windows 2000-based server after the System account profile is loaded.
During installation, the Windows Installer package calls a set of APIs. These APIs make sure that the registry settings that are added by the Windows Installer package propagate correctly from the
HKEY_USERS\.DEFAULT\Software
registry subkey to the
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Terminal Server\Install\Software
registry subkey. However, because the System account profile is loaded in the registry, the Windows Installer package registry settings are saved to the
HKEY_USERS\S-1-5-18\Software
registry subkey instead of to the
HKEY_USERS\.DEFAULT\Software
subkey. Therefore, the Windows Installer package settings never propagate to the
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Terminal Server\Install\Software
registry subkey.

Resolution

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

This hotfix requires Microsoft Windows 2000 Service Pack 3 or later.

Restart requirement

You must restart your computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
   Date         Time   Version            Size    File name
   --------------------------------------------------------------
   16-Jan-2004  19:51  5.0.2195.6824      42,256  Basesrv.dll      
   21-Sep-2003  00:45  5.0.2195.6824     236,304  Cmd.exe          
   16-Jan-2004  19:51  5.0.2195.6882     222,992  Gdi32.dll        
   16-Jan-2004  19:51  5.0.2195.6886     711,440  Kernel32.dll     
   16-Jan-2004  19:51  5.0.2195.6824      54,032  Mpr.dll          
   16-Jan-2004  19:51  5.0.2195.6883     334,096  Msgina.dll       
   16-Jan-2004  19:51  5.0.2195.6882      90,232  Rdpwd.sys
   09-Jan-2004  01:41  5.0.2195.6888   5,854,720  Sp3res.dll       
   16-Jan-2004  19:51  5.0.2195.6882     380,176  User32.dll       
   16-Jan-2004  19:51  5.0.2195.6891     391,952  Userenv.dll      
   15-Jan-2004  19:04  5.0.2195.6890   1,630,224  Win32k.sys
   11-Nov-2003  00:29  5.0.2195.6873     182,032  Winlogon.exe     
   16-Jan-2004  19:51  5.0.2195.6884     243,984  Winsrv.dll       
   16-Jan-2004  19:51  5.0.2195.6886     711,440  Kernel32.dll     
   15-Jan-2004  19:04  5.0.2195.6890   1,630,224  Win32k.sys
   16-Jan-2004  19:51  5.0.2195.6884     243,984  Winsrv.dll  

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article.

More information

This hotfix adds the DisableLoadSystemProfile entry to the
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon
registry subkey. After you apply this hotfix, the DisableLoadSystemProfile entry is enabled, and the REG_DWORD value is set to 1. If a program or service tries to use the LoadUserProfile function to load the System account profile, the LoadUserProfile function will return an error.

This problem does not occur in Microsoft Windows Server 2003 because the
HKEY_USERS\S-1-5-18
registry key is a symbolic link to the
HKEY_USERS\.DEFAULT
registry key.

For additional information about program installation in a Terminal Services environment, click the following article numbers to view the articles in the Microsoft Knowledge Base:
286100 PRB: HKCU registry entries not propagated on Terminal Services
186498 Terminal Server application integration information
For additional information, click the following article numbers to view the articles in the Microsoft Knowledge Base:
816915 New file naming schema for Microsoft Windows software update packages
824684 Description of the standard terminology that is used to describe Microsoft software updates

Properties

Article ID: 834878 - Last Review: October 26, 2013 - Revision: 3.0
Applies to
  • Microsoft Windows 2000 Server
  • Microsoft Windows 2000 Advanced Server
Keywords: 
kbnosurvey kbarchive kbautohotfix kbhotfixserver kbqfe kbbug kbfix kbwin2000presp5fix KB834878

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com