AVD remote desktop app showing on screen but not responding to clicks until you minimize/maximize

[jholmquist]

Over the past couple months and more recently we have had users report issues when opening up office apps as well as other non Microsoft apps from the remote desktop client to access AVD apps.  The window for the application will appear on screen but not respond to anything until you shift+right click on the app icon in the taskbar to minimize and then maximize it again.  We are on version 1.2.4157 of remote desktop.  Anyone else experiencing this issue?

[#2]

Do you know if doing ctrl+alt+del temp fixes it as well? We had a weird similar issue with a user that we chalked up to issues with the Wireless Mouse and Keyboard and it was May 11th.

it's like either AVD quit letting clicks happen or stuff outside AVD like Teams.

[#3]

@jholmquist 

Got almost the same issue. Only with one application.

Most screens fail.

When Pushing Windows + "Arrow down" then "arrow up" the screen is centert and its clickable 

[#4]

We have the same Problem at a customers site with one user. Minimize and maximize the window helps temporarily. If anyone found a solution to resolve the issue permanent would be a great help. I investigated several hours without any progress

[#5]

@patricksteiner92 

Issue just kind of went away or at least hasn't created any more notice for my helpdesk guys to bring it up. The guy it was happening to here is a squeaky wheel so that's how I ran into it.

[#6]

We're seeing this problem too, but with Remote Desktop Connection running as a published application in an AVD host. Accessing it from home. Details from the Remote Desktop Win32 (not UWP) app I'm using are provided below. All machines involved are fully patched and up-to-date.

Has anyone figured out what causes this and how to fix it ?  My colleague actually built a new AVD host / jump box and it's still the same.

[Expanded Information]
Timestamp (UTC): 2023-07-03T14:04:47.879Z
Activity ID: 12a60ff1-1895-4353-87af-379ede880000

[Client details]
Client version: 1.2.4337.0 (x64)
Local OS: Windows 10 Home x64 (10.0, Build 22621)

[Network details]
Transport protocol: UDP
Round-trip time: 23 ms
Available bandwidth: 91.98 Mbps
Frame rate: 0 FPS

[Remote computer details]
Remote session type: RemoteApp
Gateway name: Not in use
Gateway log-on method: Not in use
Remote computer: xxxxx.xxxxx.co.uk
Identity verification method: NTLM

[#7]

We are seeing same issues with two different host pools.

Windows 10 Enterprise multi-session latest updates

Windows 10 PCs with Remote Desktop Client 1.2.4337.0

Applications affected:
Office (Word)
Power BI Desktop

Last 2 months

[#8]

Has anyone discovered a solution to this ? What's the cause ? Could it possibly be caused by Microsoft issuing a defective change / update to the Azure platform ?

[#9]

@huddie is the user on the most current version of the AVD Client? We had 1 users with this for about a day, and then it went away. No other reports. But we keep our clients on the latest releases. They were using a Wireless Logitech Keyboard.

[#10]

Thanks @DBR14. By 'AVD Client' I think you mean the Remote Desktop app. I'm still experiencing this problem and I'm on the latest version (details below). In fact, since my SysAdmin colleagues and I discovered this issue, we have been keeping said client up-to-date. I updated it again yesterday and experienced the same issue this morning.

[Window Title]
Remote Desktop

[Content]
Your connection quality is good and UDP is enabled.

[^] Hide details [Send Diagnostics] [Disconnect] [OK]

[Expanded Information]
Timestamp (UTC): 2023-07-18T09:02:02.314Z
Activity ID: ***

[Client details]
Client version: 1.2.4419.0 (x64)
Local OS: Windows 10 Home x64 (10.0, Build 22621)

[Network details]
Transport protocol: UDP
Round-trip time: 23 ms
Available bandwidth: Greater than 239 Mbps
Frame rate: 0 FPS

[Remote computer details]
Remote session type: RemoteApp
Gateway name: Not in use
Gateway log-on method: Not in use
Remote computer: ***
Identity verification method: NTLM

[#11]

@huddie correct, AVD Client = Remote Desktop Client, but since there's 2 versions of it, I say AVD client to avoid the confusion.

I would suggest you use the ADMX template for AVD and get off the UDP stream and onto TCP and see if that helps. We have not had the mass disconnection issues or this weird non-response issue since doing this.

Some say your users will see a delay in responsiveness due to the change from UDP to TCP, but we actually saw an improvement.

[#12]

We are still experiencing this issue while also keeping the AVD client up to date. We have had a ticket opened with Microsoft since May with no response yet

[#13]

Exact same issue started for us last week with one app. Today, 3 more users reported the same issue with another app. The app just gets stuck and frozen on top left of the screen - unable to interact with the app unless minimized and then maximized.

Tried disabling UDP, tried older version of AVD client, reimaged the app host - nothing helped. 

[#14]

Same problem.
I installed version 1.2.2459.0 and this version works.
I also installed the Remote Desktop App (Not the AVD Desktop) and that version is also working. The problem is that you mis some functions in the RDApp. The Remote App is not visible in the Start Menu and it will be opend in a RDP window. Also adding a Workspace is different from the AVD App.
Hope that Microsoft does something with this in the next update.