You cannot log on to a virtual machine that is running Windows 8 or Windows Server 2012 in a VDI environment

Consider the following scenario:
  • You deploy a Virtual Desktop Infrastructure (VDI) environment in a network.
  • You enable the Remote Desktop Virtualization Host (RD Virtualization Host) role service on the Windows Server 2012-based computers.
  • You try to log on to a virtual machine that is running Windows 8 or Windows Server 2012 in the VDI environment.
In this scenario, you cannot log on to the virtual machine. The logon screen appears but the logon process cannot be completed.


  • The previous corresponding remote session to the RD Virtualization Host does not log off.
  • You may receive the following error message when you try to manually logoff the session in the Server Manager console:

    RD Connection Broker failed to process the connection request for user <domain>\<userid>.
    Failed while checking for disconnected session.
    Error: User is trying to connect to the same Pool more than once simultaneously.

This issue occurs because the host computer does not receive a notification that the previous session has ended during the logoff operation. Therefore, the previous session does not log off successfully.

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.

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 website: 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.


To apply this hotfix, you must be running Windows Server 2012.

Registry information

To apply this hotfix, you do not have to make any changes to the registry.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows Server 2012 file information notes
Important Windows 8 hotfixes and Windows Server 2012 hotfixes are included in the same packages. However, only "Windows 8" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 8" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
  • The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
    VersionProductMilestoneService branch
    6.2.920 0.20 xxxWindows Server 2012RTMLDR
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2012" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x64-based versions of Windows Server 2012
File nameFile versionFile sizeDateTimePlatform

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 about software update terminology, 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

Additional file information for Windows Server 2012

Additional files for all supported x64-based versions of Windows Server 2012
File nameAmd64_microsoft-hyper-v-integration-rdv-core_31bf3856ad364e35_6.2.9200.20623_none_b0f3c2599d29cdc3.manifest
File versionNot applicable
File size1,843
Date (UTC)02-Feb-2013
Time (UTC)09:25
PlatformNot applicable

Article ID: 2795531 - Last Review: 03/13/2013 06:57:00 - Revision: 1.0

Windows Server 2012 Datacenter, Windows Server 2012 Essentials, Windows Server 2012 Foundation, Windows Server 2012 Standard

  • kbqfe kbfix kbhotfixserver kbautohotfix kbsurveynew kbexpertiseadvanced KB2795531