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
To apply this hotfix, you must have Windows Server 2003 SP1 or Windows Server 2003 SP2 installed on the computer.
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
Restart requirement
You must restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix replaces the following hotfixes:
901150 You may receive a �Stop 0x000000ab� error message when you log off a Terminal Services session on a Windows Server 2003 S901150-based Terminal Server
907242 You receive a "Stop 0x000000ab" error message when you log off from a Terminal Services session on a Windows Server 2003 S907242-based terminal server
910362 Error message when you log off from a Terminal Services session on a Windows Server 2003 Service Pack 1-based terminal server: "Stop 0x000000AB SESSION_HAS_VALID_POOL_ON_EXIT"
918673 You receive a "Stop 0x000000ab" error message when a Terminal Services client computer logs off from a Terminal Services session on a Windows Server 2003 S918673-based Terminal Services computer
923035 Stop error message when a Terminal Services client logs off from a session on a server that is running Windows Server 2003 with Service Pack 1: "Stop 0x000000AB (SESSION_HAS_VALID_POOL_ON_EXIT)"
924806 Stop error message when a client logs off a Terminal Services session on a server that is running Windows Server 2003 with Service Pack 1: "Stop 0x000000AB (SESSION_HAS_VALID_POOL_ON_EXIT)"
928942 Error message when you log off a Terminal Services session on Windows Server 2003 Terminal Server with Service Pack 1 or with Service Pack 2: "Stop 0x000000AB"
931282 Stop error message when a client computer logs off from a Terminal Services session on a server that is running Windows Server 2003 with Service Pack 1 or with Service Pack 2: "Stop 0x000000AB (SESSION_HAS_VALID_POOL_ON_EXIT)"
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.
Windows Server 2003 with Service Pack 1, x86-based versions
File name | File version | File size | Date | Time | Platform | SP requirement |
---|
Gdi32.dll | 5.2.3790.2892 | 284,160 | 02-Mar-2007 | 08:11 | x86 | SP1 |
Win32k.sys | 5.2.3790.2965 | 1,856,000 | 02-Jul-2007 | 12:12 | x86 | SP1 |
Windows Server 2003 with Service Pack 2, x86-based versions
File name | File version | File size | Date | Time | Platform | SP requirement |
---|
Gdi32.dll | 5.2.3790.4033 | 282,624 | 02-Mar-2007 | 06:41 | x86 | SP2 |
Win32k.sys | 5.2.3790.4109 | 1,846,272 | 02-Jul-2007 | 14:39 | x86 | SP2 |
Windows Server 2003 with Service Pack 1, Itanium-based versions
File name | File version | File size | Date | Time | Platform | SP requirement | Service branch |
---|
Gdi32.dll | 5.2.3790.2892 | 909,312 | 02-Jul-2007 | 15:34 | IA-64 | SP1 | Not Applicable |
Win32k.sys | 5.2.3790.2965 | 5,554,688 | 02-Jul-2007 | 15:34 | IA-64 | SP1 | Not Applicable |
Wgdi32.dll | 5.2.3790.2892 | 287,744 | 02-Jul-2007 | 15:34 | x86 | SP1 | WOW |
Windows Server 2003 with Service Pack 2, Itanium-based versions
File name | File version | File size | Date | Time | Platform | SP requirement | Service branch |
---|
Gdi32.dll | 5.2.3790.4033 | 913,408 | 02-Jul-2007 | 15:44 | IA-64 | SP2 | Not Applicable |
Win32k.sys | 5.2.3790.4109 | 5,559,296 | 02-Jul-2007 | 15:44 | IA-64 | SP2 | Not Applicable |
Wgdi32.dll | 5.2.3790.4033 | 290,816 | 02-Jul-2007 | 15:44 | x86 | SP2 | WOW |
Windows Server 2003, x64-based versions
File name | File version | File size | Date | Time | Platform | SP requirement | Service branch |
---|
Gdi32.dll | 5.2.3790.2892 | 617,472 | 02-Jul-2007 | 15:34 | x64 | SP1 | Not Applicable |
Win32k.sys | 5.2.3790.2965 | 4,542,976 | 02-Jul-2007 | 15:34 | x64 | SP1 | Not Applicable |
Wgdi32.dll | 5.2.3790.2892 | 287,744 | 02-Jul-2007 | 15:34 | x86 | SP1 | WOW |
Windows Server 2003 with Service Pack 2, x64-based versions
File name | File version | File size | Date | Time | Platform | SP requirement | Service branch |
---|
Gdi32.dll | 5.2.3790.4033 | 619,520 | 02-Jul-2007 | 15:44 | x64 | SP2 | Not Applicable |
Win32k.sys | 5.2.3790.4109 | 4,536,320 | 02-Jul-2007 | 15:44 | x64 | SP2 | Not Applicable |
Wgdi32.dll | 5.2.3790.4033 | 290,816 | 02-Jul-2007 | 15:44 | x86 | SP2 | WOW |