The color depth is unexpectedly changed to 8-bit when a high screen-resolution setting is used in a terminal-server session that is connected to a Windows Server 2003-based computer

Consider the following scenario:

• You establish a terminal-server session to a Windows Server 2003-based computer.
• You use a high screen-resolution setting in the terminal-server session.

For example, you use the following command to establish the terminal-server session at a screen resolution of 3840 by 1024 pixels:In this scenario, the terminal-server session unexpectedly displays only 8-bit color depth (256 colors).

This problem occurs if one of the following is installed on the Windows Server 2003-based computer:

• Windows Server 2003 Service Pack 2 (SP2)
• The hotfix that is described in the following Microsoft Knowledge Base article:
  918679 You cannot connect to a Windows Server 2003-based terminal server when the screen resolution for the Remote Desktop Web Connection ActiveX control is higher than 1600 by 1200 pixels

After you install hotfix 918679 or Windows Server 2003 SP2, Terminal Services restricts the color depth of terminal-server sessions to 8-bits if the specified resolution is higher than 1600 by 1200 pixels.

After you apply the following hotfix, the color depth of a terminal-server session that has a high resolution can be up to 16-bits.

Note When this hotfix is applied, terminal-server sessions that have high resolutions and high color depths may exhaust resources on the terminal server. If you experience this problem, contact Microsoft Customer Support Services. For a complete list of Microsoft Customer Support Services telephone numbers and for information about support costs, visit the following Microsoft Web site:

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 SP2 installed on the terminal server. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

Registry information

The hotfix automatically adds the following registry entry to the system:

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 2, x86-based versions

Windows Server 2003 with Service Pack 2, Itanium-based versions

Windows Server 2003 with Service Pack 2, x64-based versions

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: