Skip to Content

Solved: Bug with Remote Desktop Client Application drop down list break when connected to AVD workspace

By: Author Alex Lim

Posted on  - Last updated:

Categories Troubleshooting

Troubleshooting Question

I’m encountering a problem with the Remote Desktop client application when connecting to an Azure Virtual Desktop (AVD) workspace. Specifically, when I connect using the Remote Desktop client, it disrupts the dropdown lists in desktop applications, pushing them to the upper right corner of the screen.

This problem is exclusive to the Remote Desktop client; when we use the web client to access the AVD workspace, everything functions correctly. It’s worth noting that we’ve observed this issue on both Windows 10 and Windows Server 2019. Our Windows 10 version is 22H2 (Build 19045.2965), and we’re using Remote Desktop client version 1.2.4240.0 (x64).

Solved: Issue with Remote Desktop Client Application and AVD Workspace

I’m seeking assistance in resolving this problem and ensuring that the dropdown lists behave as expected when using the Remote Desktop client to connect to the AVD workspace. Any guidance or solutions would be greatly appreciated.

Solution

Microsoft support has offered a solution to resolve the issue with dropdown lists in desktop applications when using the Remote Desktop client with an Azure Virtual Desktop (AVD) workspace. Here are the details:

Workaround

Key: HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\RdpCloudStackSettings
Value: RAILDVCActivateThreshold
Type: REG_DWORD
Data: 0

This workaround involves modifying a registry key and its associated value. By setting “RAILDVCActivateThreshold” to a value of 0, you can temporarily address the issue with dropdown lists.

Resolution

Microsoft has acknowledged the problem and is actively working on a permanent fix for the issue associated with the SXS (side-by-side) update. The fix is expected to be implemented in the upcoming month; however, there is no specific estimated time of arrival (ETA) provided at this time.

Once the fix is released, it will automatically update the registry key mentioned in the workaround, ensuring a more permanent solution. Therefore, users experiencing this problem should apply the workaround as needed, and they can anticipate a permanent fix from Microsoft in the near future when the SXS update is addressed.