Remote Desktop reconnect failes

D 106

Hi,

recently we see the client freezing after disconnecting a session.
if you try to reconnect to the session or start another session, you get the message that you may not be able to connect because of unsufficient virtual memory.
In the Taskmanager you can see that the process msrdc.exe is still open 2 to 3 minutes after disconnecting.

Is that an known issue which will be targeted? The problem is still present in the newest insider build.

Regards

jacobg 25 Reputation points

2024-08-28T12:25:38.6733333+00:00

We also experience same problem with msrdc.exe that stops responding after logout/disconnect. We've tried downgrading to 1.2.5560 as well as upgrading to Insider release 1.2.5699, both with same issue.
Joe Durnal 15 Reputation points

2024-09-04T16:19:34.31+00:00

My customer seems to be having a similar if not the same issue with their Azure Virtual Desktop environment. Currently using client version 1.2.5620.0 (x64).

It is sometimes associated with the error message pop up:

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.

Other issues that seem to be related are:
User authenticates with the remote desktop app, then double clicks their application group icon and there is no response, nothing seems to happen at all. We see in the WVDFeeds log the feed refresh, but nothing else after that.

User logged into more than one host pool, disconnecting from one causes the other to freeze for a period of time, but it does seem to come back.
NEVES Antonio Luis 5 Reputation points

2024-09-12T14:11:15.9633333+00:00

It looks like with September updates the problem was solved, at least I can't simulate it anymore.
Wout 5 Reputation points

2024-09-18T12:09:46.0633333+00:00

I confirm the above comment of NEVES Antonio Luis: after installing KB5043076 (on my windows 11 x64 laptop), I haven't had the issue anymore since a few days now. Fingers crossed...

15 answers

Rob van den Oever 0 Reputation points

2024-09-03T08:03:55.37+00:00

We see this as well. MSRDC.EXE processes need to be closed in order to have users login properly.
I have seen it on new but also 2 month old releases of the client.

I would almost dare to point (or am I already? :)) to the monthly updates of August.
Since the cumulative updates we've been experiencing this AND also other issues like users who connect their laptops to monitor/kb/mouse docking hubs experiencing USB errors forcing them to shut down and restart in order for it to work again.

Something's messed up. Hope it'll be fixed sooner than the multi-monitor bug the client had over a year ago, because that took months.
Please sign in to rate this answer.
Justin Gross 0 Reputation points

2024-09-05T01:46:07.4433333+00:00

Please try using the newest version of the msrdc client found here, https://video2.skills-academy.com/en-us/azure/virtual-desktop/whats-new-client-windows?pivots=remote-desktop-msi#supported-client-versions. Please note that the version you can download is 1.2.5623.0 but the documentation still lists 1.2.5620 as the newest for now.

D 106 Reputation points

2024-09-05T06:46:22.9833333+00:00

The new version did not fix it.

Wout 5 Reputation points

2024-09-05T06:59:36.13+00:00

Indeed, tried the new version, didn't solve the issue for me

Jongeneel, Gertjan 1 Reputation point

2024-09-05T07:50:35.34+00:00

Version 1.3.278.0 (August 26, 2024) of the Windows App shows 'Fixed an issue that caused Windows App to crash on disconnect.' as one of the fixes. See https://video2.skills-academy.com/en-us/windows-app/whats-new?tabs=windows. Is that helpful?

D 106 Reputation points

2024-09-05T07:59:32.9733333+00:00

Not for us. The last Windows App release has also the bug.

Mathieu LEROY 0 Reputation points MVP

2024-09-10T12:54:10.5033333+00:00

Any update ? Facing the same issue
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
D 106 Reputation points

2024-09-06T16:29:09.61+00:00

Microsoft might have changed something in the background.
This morning the new version and the insider version were not functional and now the bug seems to be gone.
Please sign in to rate this answer.
Jacob Giraud 0 Reputation points

2024-09-09T08:12:52.62+00:00

I tried today and it seems that we still have same problem.

D 106 Reputation points

2024-09-09T09:34:46.1166667+00:00

Yes, it went away on Friday and today we see the same results again. Seems that is is something in the Backend.

ViP 0 Reputation points

2024-09-09T14:44:09.9533333+00:00

I tryed the new version 1.2.5699 (Insider) but the issue is still persists!
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Jakub Wyrembowski 0 Reputation points

2024-09-12T05:06:46.3233333+00:00

Has anyone managed to solve the problem? Has Microsoft released a fix of any kind?
Please sign in to rate this answer.
D 106 Reputation points

2024-09-24T13:05:01.45+00:00

They released the new version which reduces the error but a complete fix is not released yet.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
SirThomsalot 5 Reputation points

2024-09-12T14:14:05.54+00:00

No, the only workaround is to kill the msrdc.exe or to wait for about 2 minutes.
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
D 106 Reputation points

2024-10-09T11:22:46.9466667+00:00

Microsoft released a fix to the backend and the bug is not present anymore.
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Remote Desktop reconnect failes

15 answers

Your answer