Windows Virtual Desktop Client can't connect

Brass Contributor



We're in the process of rolling out WVD to some users, one of which is me.

I can connect via the Web Client without problems. I can connect to a full desktop and start apps only. So no issues there.


However, with the Remote Desktop Client I receive the following error (screenshot attached):

"Your computer can't connect to the remote computer because a security package error occurred in the transport layer. Retry the connection or contact your network administrator for assistance".


Other colleagues can also connect without problems with the RD Client.

I also can connect from other devices with my account. So it's clearly something on my own device.


Important to note is that I can see all the WVD's and apps in the client.
It's when I try to connect to it that it throws the error.


What I've done:

  • Clear all entries from the Credential Manager
  • No proxy
  • Not blocked on firewall
  • Created this registry entry:
    HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client
    Name: RDGClientTransport
    Type: Dword
    Data: 1 
  • Created this registry key:
    Key: HKLM\SYSTEM\CurrentControlSet\Control\Lsa
    Name: LMCompatilityLevel
    Type: REG_DWORD
    Value: 3


Honestly no idea why it doesn't work.

I don't think that my device differs anything from those of my colleagues and from other domain joined devices.


Normal RDP to on-prem servers is working just fine.


Any thoughts?

8 Replies

@Soo Kuan Teo 


Yes, I'm using the Windows Desktop Client and it's the latest version.
In fact, since I have the problem there have been two updates of the clients, which didn't solve the problem.


And I know, I'm not using mstsc.exe

Can you please:
1. setup log analytics for your WVD workspace.
2. Reproduce your problem.
3. wait for a few minutes, then go to your log analytics.
3. Please share your corelationid for the connection that has the issue.
I will take a look at your connection issue with your corelationid.


@Soo Kuan Teo  Would it even hit the log analytics if it fails right at the client level?

@NidalT  i have same issue and it works with device that is imaged and has same group policy which means TLS and SSL settings should not be causing it. One thing I miss from Citrix  is web version supported multiple monitor, if the client version has bug at least web version should have multi monitor to fall back on 


Is have fixed my issues with IIS Crypto.

I used the option "Best practices" and applied it. It worked immediately after that.

Nartac Software - IIS Crypto

Thanks for your response

@NidalT Best practice enables Tls 1.0 on client side and server side. Did you end up removing them? 

@PrasantChettri I think I've disabled it but I don't remember for sure.

It is disabed now anyway.


I only ran this on my own computer, not on any server.