You are currently offline, waiting for your internet to reconnect

A memory leak occurs after you install Microsoft Windows 2000 Server Service Pack 4

This article has been archived. It is offered "as is" and will no longer be updated.
After you install Microsoft Windows 2000 Service Pack 4 (SP4), a memory leak condition may occur on a server that also has Microsoft Operations Manager (MOM) installed. When you try to log on to the server computer, you may experience one or more memory errors. Additionally, the server may stop responding (hang), and event ID 2020 may appear in the system event log.
This problem may occur if programs generate remote procedure call (RPC) network traffic. This problem may affect MOM because MOM generates RPC traffic when it communicates with managed agents.

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: 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.


You must have Windows 2000 SP4 installed to apply this hotfix. If MOM 2000 SP1 is installed on the server, stop the MOM Service (Onepoint) before you apply this hotfix.

For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
260910 How to obtain the latest Windows 2000 service pack

Restart requirement

You must restart your computer after you apply this hotfix.

Hotfix replacement information

This hotfix replaces Knowledge Base article 825237.

File information

The English version of this 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   -----------------------------------------------------------   02-Feb-2004  19:59  5.0.2195.6824      42,256  Basesrv.dll   21-Sep-2003  00:45  5.0.2195.6824     236,304  Cmd.exe   02-Feb-2004  19:59  5.0.2195.6882     222,992  Gdi32.dll   02-Feb-2004  19:59  5.0.2195.6894     711,952  Kernel32.dll   02-Feb-2004  19:59  5.0.2195.6824      54,032  Mpr.dll   02-Feb-2004  19:59  5.0.2195.6895     334,608  Msgina.dll   02-Feb-2004  19:59  5.0.2195.6892      90,264  Rdpwd.sys   09-Jan-2004  01:41  5.0.2195.6888   5,854,720  Sp3res.dll   02-Feb-2004  19:59  5.0.2195.6891     380,688  User32.dll   02-Feb-2004  19:59  5.0.2195.6891     391,952  Userenv.dll   21-Jan-2004  19:48  5.0.2195.6892   1,630,256  Win32k.sys   11-Nov-2003  00:29  5.0.2195.6873     182,032  Winlogon.exe   02-Feb-2004  19:59  5.0.2195.6884     243,984  Winsrv.dll
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
Although this memory leak problem is known to occur with MOM, other programs that generate RPC traffic may also trigger this problem. You may experience this problem after you install Windows 2000 SP4 even if MOM is not installed or otherwise implicated.

The change in the Userenv.dll file is to fix a token leak issue in the Windows 2000 SP4 Services.exe process. The leak occurs whenever a thread that is executing some of the userenv functions does not impersonate the user for some reason.

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
rpc, crash, hang,

Article ID: 835517 - Last Review: 01/17/2015 16:30:38 - Revision: 4.0

Microsoft Windows 2000 Server, Microsoft Windows 2000 Advanced Server

  • kbnosurvey kbarchive kbautohotfix kbhotfixserver kbqfe kbbug kbfix kbwin2000presp5fix KB835517