Score:2

Remote Desktop stuck at Loading Virtual Machine

lu flag

We have a Terminal Services environment with following configuration

Server A - RD Gateway + Connection Broker Server 1 to 20 - RD Session Host

We have 7 collections and session hosts servers are assigned to different collections based on application version we require. All servers are running Windows Server 2016 Standard. We have wildcard certificates installed on Server A for all services.

Our environment does not uses virtual machine based deployment. Never had any. It has been working fine but lately lot of users get stuck at LOADING VIRTUAL MACHINE.

When we check in the event log in the gateway - there is an event 801 like following

RD Connection Broker successfully processed the connection request for user XX. Redirection info: Target Name = XX Target IP Address = 192.168.110.72 Target Netbios = XX Target FQDN = XX Disconnected Session Found = 0x0

After around 1 min there is an event 819 like following:

This connection request has timed out. User could not log on to the end point within the alloted time. Remote Desktop Connection Broker will stop monitoring this connection request.

There is absolutely no event on the session host server. We are able to connect to the session host server directly. We have tried almost everything but could not find a solution.

Some urgent advise will be helpful.

Thanks, RJ

17-04-2022 Upon more investigation, this is not happening on all clients. On the client where this is happening there are errors like following in the local Terminal Services - Client ActiveX Core

Component name:CAAClientAdapter, :: 'm_spHelper->ReadCreds failed' in CAAClientAdapter::CreateTunnel at 380 err=[0xffffffff], Error code:0xFFFFFFFF

Component name:CClientProxyTransport, :: 'm_ClientAdapter->CreateTunnel failed' in CProxyRawTrans::CreateProxyConnection at 2132 err=[0x800759d9], Error code:0x800759D9

Component name:CClientProxyTransport, :: 'Gateway connection time out is 90' in CClientHTTPProxyTransport::Connect at 1098 err=[0x800759d9], Error code:0x800759D9

Component name:CClientProxyTransport, :: 'CreateConnection failed' in CClientHTTPProxyTransport::Connect at 1107 err=[0x800759d9], Error code:0x800759D9

cn flag
I’m voting to close this question because it was caused by a specific preview version of Windows 11 that still has been retired. The issue has been fixed.
Swisstone avatar
cn flag
Can you tell us which event log you checked on the session host? I recommend checking at least all the logs starting with "RemoteDesktopServices" and "TerminalServices"
lu flag
Hello, yes we checked all logs.
Score:0
de flag

This solved the same issue for us:

  • Open Registry editor Navigate to HKEY_CURRENT_USER > Software > Microsoft > Terminal Server Client.
  • Navigate to the right-hand pane, right-click, and choose New > DWORD (32-bit value). Name this option as “RDGClientTransport.”
  • Double-click this newly-created file. Its properties will open, and here, look for an option to set the value data. Enter the value 1. Click OK and close the Windows registry

Source: https://learn.microsoft.com/en-us/answers/questions/809031/remote-desktop-stuck-at-loading-virtual-machine.html

Score:0
lu flag

The problem has been identified to have been caused by latest update of Windows 11 Insider Preview Beta version 22598.ni_release.220408-1503

We are seeing if removing this will resolve or we will wait for next update.

Thanks

Score:0
sa flag
  1. Go to Start > Settings > Update and Security and click Advanced Options on the right pane.

  2. Then click Recovery and click Go back under the Recovery Options.

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.