When a Terminal Services client computer logs off from a Microsoft Windows Server 2003 Service Pack 1 (SP1)-based Terminal Services session, you may receive a stop error message that resembles the following on the Terminal Services server that the client was connected to:

Back to the top

This problem is caused by a session pool leak that occurs in Win32k.sys when a client computer logs off from a Terminal Services session. This problem may also cause other client computers that are logged on to the Terminal Services computer to stop responding.

Back to the top

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:

Back to the top

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, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site: 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. To create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" section and the online request forms display 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 service Pack 1 (SP1) installed on your computer.

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.

Back to the top

Windows Server 2003, Itanium-based version

File name	File version	File size	Date	Time	Platform	SP requirement	Service branch
Gdi32.dll	5.2.3790.2709	907,776	24-May-2006	20:01	IA-64	SP1	SP1QFE
Win32k.sys	5.2.3790.2709	5,553,664	24-May-2006	20:01	IA-64	SP1	SP1QFE
Wgdi32.dll	5.2.3790.2709	285,184	24-May-2006	20:02	x86	SP1	WOW

Back to the top

Windows Server 2003, x64-based version

File name	File version	File size	Date	Time	Platform	SP requirement	Service branch
Gdi32.dll	5.2.3790.2709	610,304	24-May-2006	20:01	x64	SP1	SP1QFE
Win32k.sys	5.2.3790.2709	4,529,152	24-May-2006	20:01	x64	SP1	SP1QFE
Wgdi32.dll	5.2.3790.2709	285,184	24-May-2006	20:02	x86	SP1	WOW

Back to the top

Windows Server 2003, x86-based version

File name	File version	File size	Date	Time	Platform	SP requirement	Service branch
Gdi32.dll	5.2.3790.2709	282,112	24-May-2006	19:42	x86	SP1	SP1QFE
Win32k.sys	5.2.3790.2709	1,850,880	24-May-2006	01:23	x86	SP1	SP1QFE

Back to the top

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 Microsoft Windows Server 2003 Service Pack 2.

Back to the top

For more information about the standard terminology that is used to describe Microsoft software updates, click the following article number to view the article in the Microsoft Knowledge Base:

Back to the top