Forum Discussion

Joedurnal's avatar
Joedurnal
Copper Contributor
Aug 29, 2024

Connection error popup low virtual memory

Getting a strange error occasionally from the Azure Remote Desktop client for my customer.  I don't think it is really about virtual memory on the client computer, and it occurs before any connection is even attempted to the virtual machine.  Using client version 1.2.5620.0 (x64).  I can't seem to produce the error on demand, so far when it has occurred, it has been following a recent disconnection, but it doesn't do it every time.  I'm not finding anything too relevant in the logs on the client machine or the diagnostic logging for the Azure resources.  

 

Remote Desktop
This computer can't connect to the remote computer.

The problem might be due to low virtual memory on your computer. Close your other programs, and then try connecting again. If the problem continues, contact your network administrator or technical support.

 

 

Joe

 

3 Replies

  • denis89's avatar
    denis89
    Brass Contributor
    Hi,
    a lot of people have this error at the moment.
    https://learn.microsoft.com/en-us/answers/questions/1865745/remote-desktop-reconnect-failes
    It is definitely not related to the memory of the avd host.
    The client does not stop the process after disconnection.
    Microsoft should be aware of the problem as there were opened multiple support tickets right now.
    If you wait 2 to 3 minutes before reconnecting it might not occure and the process is released, that would be the reason, why you don't see it every time.
    Even the most recent insider version has the problem.
    • Joedurnal's avatar
      Joedurnal
      Copper Contributor

      Kidd_Ip 

      I found that article when searching. I think it is ruled out.
      The error message is different: "Oops, we couldn't connect to 'SessionDesktop,'" versus "The problem might be due to low virtual memory on your computer."
      The client is different: "When you're trying to connect to Azure Virtual Desktop from the web client" versus we are using version 1.2.5620.0 (x64) of the installer client.
      We are not using the N sku
      TLS 1.2 is enabled all around

Resources