When you start a terminal session to a computer that is running Windows Server 2008 and that has the terminal server role installed, the full Windows desktop starts instead of the program that is specified by the terminal server

Applies To
Windows Server 2008 for Itanium-Based Systems Windows Server 2008 Datacenter Windows Server 2008 Enterprise Windows Server 2008 Standard

Symptoms

Consider the following scenario:

  • You start a terminal session to a computer that is running Windows Server 2008 and has the terminal server role installed.
  • A specific program is configured to start on this terminal server when a terminal session is started.
  • You end the terminal session while the terminal session is still being established. For example, you close the terminal session window when you see the "Preparing your desktop" screen.
  • You start another terminal session to the same terminal server by using the same user account.

In this scenario, the full Windows desktop starts instead of the specified program.

Cause

When a terminal session starts, the userinit.exe program determines which program to start. However, when this issue occurs, the server does not correctly log off from the terminal session. Therefore, the userinit.exe program cannot locate the specified program. Instead, the program starts the explorer.exe process. Therefore, the full Windows desktop appears in the terminal session.

Resolution

A hotfix is available to resolve this issue. After you apply this hotfix, the userinit.exe program logs off the current terminal session if it cannot locate the specified program.

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:

http:⁠//support.microsoft.com/contactus/?ws=support 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.

Important Windows Vista and Windows Server 2008 hotfixes are included in the same packages. However, only one of these products may be listed on the “Hotfix Request” page. To request the hotfix package that applies to both Windows Vista and Windows Server 2008, just select the product that is listed on the page.

Prerequisites

To apply this hotfix, your computer must be running one of the following operating systems:

  • Windows Server 2008
  • Windows Server 2008 Service Pack 2

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other previously released 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.

Windows Server 2008 file information note

The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are
listed separately. MUM and MANIFEST files, and the associated security catalog (.cat) files, are critical to maintaining the state of the updated component. The security catalog files (attributes not listed) are signed with a Microsoft digital signature.

For all supported x86-based versions of Windows Server 2008

File name File version File size Date Time Platform SP requirement
Userinit.exe 6.0.6001.22425 25,088 04-May-2009 10:16 x86 SP1
Userinit.exe 6.0.6002.22128 25,088 04-May-2009 10:03 x86 SP2

For all supported x64-based versions of Windows Server 2008

File name File version File size Date Time Platform SP requirement
Userinit.exe 6.0.6001.22425 28,672 04-May-2009 10:38 x64 SP1
Userinit.exe 6.0.6002.22128 28,672 04-May-2009 10:18 x64 SP2

For all supported Itanium-based versions of Windows Server 2008

File name File version File size Date Time Platform SP requirement
Userinit.exe 6.0.6001.22425 60,928 04-May-2009 10:31 IA-64 SP1
Userinit.exe 6.0.6002.22128 60,928 04-May-2009 10:11 IA-64 SP2

Workaround

To work around this issue, you log off the terminal session, and then start a new one.

Status

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

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

Additional file information for Windows Server 2008

Additional files for all supported x86-based versions of Windows Server 2008

File name File version File size Date Time Platform
Package_for_kb969940_sc_0~31bf3856ad364e35~x86~~6.0.1.0.mum Not Applicable 1,421 06-May-2009 13:33 Not Applicable
Package_for_kb969940_sc_1~31bf3856ad364e35~x86~~6.0.1.0.mum Not Applicable 1,361 06-May-2009 13:33 Not Applicable
Package_for_kb969940_sc~31bf3856ad364e35~x86~~6.0.1.0.mum Not Applicable 1,701 06-May-2009 13:33 Not Applicable
Package_for_kb969940_server_0~31bf3856ad364e35~x86~~6.0.1.0.mum Not Applicable 1,425 06-May-2009 13:33 Not Applicable
Package_for_kb969940_server_1~31bf3856ad364e35~x86~~6.0.1.0.mum Not Applicable 1,365 06-May-2009 13:33 Not Applicable
Package_for_kb969940_server~31bf3856ad364e35~x86~~6.0.1.0.mum Not Applicable 1,713 06-May-2009 13:33 Not Applicable
Package_for_kb969940_winpesrv_0~31bf3856ad364e35~x86~~6.0.1.0.mum Not Applicable 1,422 06-May-2009 13:33 Not Applicable
Package_for_kb969940_winpesrv~31bf3856ad364e35~x86~~6.0.1.0.mum Not Applicable 1,430 06-May-2009 13:33 Not Applicable
X86_microsoft-windows-userinit_31bf3856ad364e35_6.0.6001.22425_none_dca1be2cead945df.manifest Not Applicable 7,930 04-May-2009 14:03 Not Applicable
X86_microsoft-windows-userinit_31bf3856ad364e35_6.0.6002.22128_none_de8b30f2e7fce708.manifest Not Applicable 7,930 04-May-2009 14:04 Not Applicable

Additional files for all supported x64-based versions of Windows Server 2008

File name File version File size Date Time Platform
Amd64_microsoft-windows-userinit_31bf3856ad364e35_6.0.6001.22425_none_38c059b0a336b715.manifest Not Applicable 7,964 04-May-2009 14:21 Not Applicable
Amd64_microsoft-windows-userinit_31bf3856ad364e35_6.0.6002.22128_none_3aa9cc76a05a583e.manifest Not Applicable 7,964 04-May-2009 13:36 Not Applicable
Package_for_kb969940_sc_0~31bf3856ad364e35~amd64~~6.0.1.0.mum Not Applicable 1,429 06-May-2009 13:33 Not Applicable
Package_for_kb969940_sc_1~31bf3856ad364e35~amd64~~6.0.1.0.mum Not Applicable 1,369 06-May-2009 13:33 Not Applicable
Package_for_kb969940_sc~31bf3856ad364e35~amd64~~6.0.1.0.mum Not Applicable 1,711 06-May-2009 13:33 Not Applicable
Package_for_kb969940_server_0~31bf3856ad364e35~amd64~~6.0.1.0.mum Not Applicable 1,433 06-May-2009 13:33 Not Applicable
Package_for_kb969940_server_1~31bf3856ad364e35~amd64~~6.0.1.0.mum Not Applicable 1,373 06-May-2009 13:33 Not Applicable
Package_for_kb969940_server~31bf3856ad364e35~amd64~~6.0.1.0.mum Not Applicable 1,723 06-May-2009 13:33 Not Applicable
Package_for_kb969940_winpesrv_0~31bf3856ad364e35~amd64~~6.0.1.0.mum Not Applicable 1,430 06-May-2009 13:33 Not Applicable
Package_for_kb969940_winpesrv~31bf3856ad364e35~amd64~~6.0.1.0.mum Not Applicable 1,438 06-May-2009 13:33 Not Applicable

Additional files for all supported Itanium-based versions of Windows Server 2008

File name File version File size Date Time Platform
Ia64_microsoft-windows-userinit_31bf3856ad364e35_6.0.6001.22425_none_dca36222ead74edb.manifest Not Applicable 7,947 04-May-2009 13:53 Not Applicable
Ia64_microsoft-windows-userinit_31bf3856ad364e35_6.0.6002.22128_none_de8cd4e8e7faf004.manifest Not Applicable 7,947 04-May-2009 13:23 Not Applicable
Package_for_kb969940_sc_0~31bf3856ad364e35~ia64~~6.0.1.0.mum Not Applicable 1,425 06-May-2009 13:33 Not Applicable
Package_for_kb969940_sc_1~31bf3856ad364e35~ia64~~6.0.1.0.mum Not Applicable 1,365 06-May-2009 13:33 Not Applicable
Package_for_kb969940_sc~31bf3856ad364e35~ia64~~6.0.1.0.mum Not Applicable 1,706 06-May-2009 13:33 Not Applicable
Package_for_kb969940_server_0~31bf3856ad364e35~ia64~~6.0.1.0.mum Not Applicable 1,429 06-May-2009 13:33 Not Applicable
Package_for_kb969940_server_1~31bf3856ad364e35~ia64~~6.0.1.0.mum Not Applicable 1,368 06-May-2009 13:33 Not Applicable
Package_for_kb969940_server~31bf3856ad364e35~ia64~~6.0.1.0.mum Not Applicable 1,718 06-May-2009 13:33 Not Applicable
Package_for_kb969940_winpesrv_0~31bf3856ad364e35~ia64~~6.0.1.0.mum Not Applicable 1,426 06-May-2009 13:33 Not Applicable
Package_for_kb969940_winpesrv~31bf3856ad364e35~ia64~~6.0.1.0.mum Not Applicable 1,434 06-May-2009 13:33 Not Applicable