Article ID: 828146 - View products that this article applies to.
This article has been archived. It is offered "as is" and will no longer be updated.
If you try to view or to edit private characters on a computer that is running Microsoft Windows 2000, you may receive the following error message in the Win32k.sys file:
STOP: 0x000000d5 (Fatal System Error)
This problem may occur if the end-user defined characters (EUDC) font list is rebuilt and the character map (Charmap.exe) links to an old font list entry.
Hotfix informationA 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:
PrerequisitesNo prerequisites are required.
Restart requirementYou must restart your computer after you apply this hotfix.
Hotfix replacement informationThis hotfix does not replace any other hotfixes.
File informationThe 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 ----------------------------------------------------------- 03-Dec-2003 18:39 5.00.2195.6824 42,256 Basesrv.dll 21-Sep-2003 00:45 5.00.2195.6824 236,304 Cmd.exe 03-Dec-2003 18:38 5.00.2195.6824 222,992 Gdi32.dll 03-Dec-2003 18:38 5.00.2195.6867 711,440 Kernel32.dll 03-Dec-2003 18:39 5.00.2195.6824 54,032 Mpr.dll 03-Dec-2003 18:39 5.00.2195.6876 334,096 Msgina.dll 03-Dec-2003 18:39 5.00.2195.6824 90,232 Rdpwd.sys 06-Nov-2003 22:29 5.00.2195.6870 5,847,552 Sp3res.dll 03-Dec-2003 18:38 5.00.2195.6869 380,176 User32.dll 03-Dec-2003 18:39 5.00.2195.6876 389,392 Userenv.dll 03-Dec-2003 18:23 5.00.2195.6877 1,629,200 Win32k.sys 11-Nov-2003 00:29 5.00.2195.6873 182,032 Winlogon.exe 03-Dec-2003 18:39 5.00.2195.6873 243,984 Winsrv.dll 03-Dec-2003 18:39 5.00.2195.6867 711,440 Kernel32.dll 03-Dec-2003 18:23 5.00.2195.6877 1,629,200 Win32k.sys 03-Dec-2003 18:39 5.00.2195.6873 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.
For additional information about how hotfix packages are named, click the following article number to view the article in the Microsoft Knowledge Base:
816915For additional information about the terminology that is used to describe Microsoft product updates, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/816915/ )New naming schema for Microsoft Windows hotfix packages
(http://support.microsoft.com/kb/824684/ )Description of the standard terminology that is used to describe Microsoft software updates
Article ID: 828146 - Last Review: October 26, 2013 - Revision: 2.6