The Visual C runtime heap manager is incorrectly selected during the process startup in Windows Server 2003 Service Pack 1 with the East Asian language pack installed

Support for Windows Server 2003 ended on July 14, 2015

Microsoft ended support for Windows Server 2003 on July 14, 2015. This change has affected your software updates and security options. Learn what this means for you and how to stay protected.

This article has been archived. It is offered "as is" and will no longer be updated.
Symptoms
On a Microsoft Windows Server 2003 Service Pack 1 (SP1)-based computer that has the East Asian language pack installed, you find that the Visual C runtime heap manager is incorrectly selected during the process startup. Because this heap manager does not have the pageheap option enabled, it prevents you from troubleshooting a spooler heap corruption issue.
Cause
This problem occurs because there is a problem in the East Asian language support in Windows Server 2003 SP1.

If you install the East Asian language pack, the Usp10.dll file will be loaded by the Gdi32.dll initialize routine. The Usp10.dll file will then call the malloc() function in Msvcrt.dll. At this point, the Msvcrt.dll file is loaded but it is not initialized. The malloc() function will select the heap manager for the system heap or the runtime heap.

However, if the Msvcrt.dll file is already initialized, the malloc() function always uses the system heap on a Windows Server 2003 SP1-based computer. In this case, the malloc() function selects the runtime heap manager because the Msvcrt.dll file does not detect the version of the operating system.
Resolution

Service pack information

To resolve this problem, obtain the latest service pack for Windows Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
889100 How to obtain the latest service pack for Windows Server 2003

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. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

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, contact 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.

Prerequisites

You must have Windows Server 2003 SP1 installed to apply this hotfix.

Restart requirement

You must restart the 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 file attributes) 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 item in Control Panel.
File nameFile versionFile sizeDateTimePlatform
Usp10.dll1.422.3790.2706379,90419-May-200603:32x86
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Windows Server 2003 Service Pack 2.
More information
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
Properties

Article ID: 919136 - Last Review: 01/16/2015 01:55:24 - Revision: 4.0

  • Microsoft Windows Server 2003 Service Pack 1
  • kbnosurvey kbarchive kbautohotfix kbwinserv2003sp2fix kbbug kbfix kbqfe KB919136
Feedback