AVD clipboard redirection broken after 5/12/2026 updates — rdpclipcdv.exe present but not functioning

Hi Jacob Winkhaus

Based on what you’ve described, the clipboard redirection issue looks tied directly to those May 12th cumulative updates (KB5092762, KB5089549, KB5087054). We’ve seen similar behavior where the update introduces a regression in the rdpclipcdv.exe process, even though it’s running and allowed by policy. Since drive redirection is still fine, that narrows it down to clipboard-specific handling in the patched binaries.

The quickest way to confirm is to temporarily roll back one of those updates (start with KB5092762 since it’s the core cumulative) and retest clipboard. If that restores functionality, you’ve got your smoking gun. Another workaround some customers have used is manually restarting all rdpclipcdv.exe instances after logon not pretty, but it can get clipboard moving again until a hotfix lands. Also worth checking if Microsoft has released a servicing stack update or preview patch that addresses clipboard regression on 24H2 builds; those tend to follow within a couple weeks of a breaking cumulative.

I’d recommend opening a support case if rollback isn’t viable, since this looks like a product bug rather than a config issue. In the meantime, keep an eye on the Azure Virtual Desktop release notes and Windows 11 cumulative updates for any mention of clipboard redirection fixes.

If this explanation helps you move forward, please go ahead and hit “accept answer” so we know it resolved your question.

Hello Jacob,

Thank you for the detailed information and troubleshooting steps you've already completed. This significantly helps narrow down the possible causes. Based on the environment details provided, the issue appears to be related to the clipboard redirection component used by newer Azure Virtual Desktop session hosts.

Microsoft introduced additional clipboard and input channel components in newer RDInfra SxS Network Stack releases, including rdpclipcdv.exe and rdpinputcdv.exe, which are responsible for clipboard redirection and related functionality. Since your environment is running RDInfra SxS version 1.0.2512.08200, these components are actively involved in clipboard channel negotiation.

While the presence of multiple running instances of rdpclipcdv.exe confirms that the process is launching, it does not necessarily indicate that the clipboard virtual channel has been successfully established. Based on the behavior described, the issue may be occurring during clipboard channel initialization or negotiation.

To further isolate the cause, we recommend the following checks:

1. Verify both clipboard-related executables are fully allowed

Please confirm that any security controls, including AppLocker, Microsoft Defender, Defender for Endpoint, or any third-party endpoint protection solution, allow both of the following executables:

• rdpclipcdv.exe

rdpinputcdv.exe

Additionally, verify that any exclusions apply to the full installation path under the RDInfra agent directory and not only to the executable names.

You can validate that both processes are running by executing:

Get-Process rdpclipcdv, rdpinputcdv | Select-Object Name, Id, Path, StartTime

It would also be helpful to review AppLocker and security-related event logs around the time a user session is established.

2. Review Host Pool RDP Properties

Please review the Host Pool RDP Properties and verify whether the parameter below is present:

clipboardblockeddatatypes:s:

If configured, temporarily remove it and test again to rule out restrictions on specific clipboard data formats.

3. Validate the Clipboard Virtual Channel

From within an active AVD session, please check whether the clipboard virtual channel is successfully established:

Get-WmiObject -Namespace root\cimv2\TerminalServices -Class Win32_TSVirtualChannel | Where-Object { $_.ChannelName -like "*clip*" }

If the clipboard channel is absent or not connected, this would indicate a channel negotiation issue rather than a process startup issue.

4. Review Relevant Event Logs

Please review the following logs for any warnings or errors occurring during session connection:

Applications and Services Logs → Microsoft → Windows → AppLocker

Applications and Services Logs → Microsoft → Windows → TerminalServices

Windows Logs → Application

Particular attention should be given to events referencing RDInfra components, clipboard redirection, virtual channels, or process initialization failures.

5. Test with a New User Profile

If possible, create a new test user profile and establish a fresh session. This helps determine whether the issue is tied to a specific user profile or session state.

Based on the timeline provided, we also note that the issue began immediately following the May 2026 update cycle. While we cannot conclusively attribute the behavior to a specific update at this stage, the timing suggests that a recent platform or operating system change may have contributed to the issue.

If the above checks do not identify the root cause, we would recommend opening a Microsoft Support case for deeper investigation and referencing the observed behavior on Windows 11 Enterprise multi-session 24H2 with RDInfra SxS version 1.0.2512.08200. This will allow the engineering team to determine whether a known issue or regression is involved.

Please let us know the results of the above checks, and we will continue working with you on the investigation.

Reference documentations: https://learn.microsoft.com/en-us/windows-app/troubleshoot-known-issues-limitations?tabs=web

https://learn.microsoft.com/en-us/troubleshoot/azure/virtual-desktop/troubleshoot-device-redirections

References thread: https://learn.microsoft.com/en-us/answers/questions/5872635/clipboard-issues-with-azure-virtual-desktops