Fix Copy and Paste Not Working in Remote Desktop and Excel

Quick Answer

When copy and paste stops working in Remote Desktop, first determine whether the failure occurs between the local computer and the remote desktop, inside the remote desktop, or only in Excel. Check the connection's Clipboard option, restart the affected user's RDP Clipboard Monitor process, and reconnect. If necessary, save the user's work, sign out completely, and sign in again.

A planned Windows Server restart can restore clipboard operation when narrower recovery steps fail, particularly when several users are affected. A restart resolved the incident behind this guide. However, that result does not establish the original cause or guarantee a permanent fix. Restarting a shared server interrupts every session and hosted workload, so coordinate it with users and the administrator.

Scope and Symptoms

This guide primarily covers the classic Windows Remote Desktop Connection client connecting to a Windows Server desktop or Remote Desktop Session Host. Windows App, browser clients, Azure Virtual Desktop, and third-party clients can have different controls. Excel instructions apply to the installed Windows desktop application.

Typical symptoms include nothing appearing after Paste, a disabled Paste option, copying working in only one direction, or copying working in Notepad but failing in Excel. RDP Clipboard Monitor may still appear in Task Manager while copying is broken.

Clipboard redirection transfers clipboard data between a local device and a remote session. The process named rdpclip.exe, often displayed as RDP Clipboard Monitor, participates in that redirection. It is a background process: starting it normally does not open a window. A running process is only a preliminary check; a successful copy-and-paste test is the actual verification.

1. Identify Where Copy and Paste Fails

Use a short, non-sensitive word for testing. Try both keyboard shortcuts and the application's Copy and Paste menu commands. If menu commands work but keyboard shortcuts fail, investigate keyboard focus or shortcut handling before changing server settings.

These tests narrow the investigation; they do not prove a particular root cause. Both RDP transfer and Excel can fail at the same time.

2. Check Clipboard Redirection in the RDP Client

For classic Remote Desktop Connection on Windows, perform these steps on the local computer. Administrator privileges are normally unnecessary.

1. Save your work, then disconnect by closing the RDP connection window.
2. Open Remote Desktop Connection from the local Start menu.
3. Select Show Options > Local Resources.
4. Under Local devices and resources, select Clipboard.
5. If you normally use a saved connection file, save the updated settings for that connection.
6. Reconnect and repeat the Notepad transfer test in both directions.

If Clipboard was already selected, reconnecting is still a useful recovery test. Disconnecting normally leaves the remote session running, subject to the server's session timeout policies; it does not create a fresh user session.

Text copying does not require enabling all local drives. File transfer has additional requirements and restrictions. If text works but files do not, investigate file-transfer settings separately rather than repeatedly restarting the clipboard process.

3. Restart RDP Clipboard Monitor for the Affected Session

This is a common recovery technique, not a guarantee. Perform it inside the affected user's remote desktop. Restarting the process interrupts any clipboard transfer in progress; copy the source content again afterward.

Method A: Task Manager When You Cannot Paste Commands

1. Open Task Manager from the remote Start menu. Select More details if needed.
2. Open Details and locate rdpclip.exe. The Processes view may call it RDP Clipboard Monitor.
3. Confirm the username and session before ending the process. If the same account has multiple sessions, use the Session ID column to distinguish them.
4. Select the matching process and choose End task.
5. Use Run new task, or open the Run dialog inside the remote desktop, and manually enter:

rdpclip.exe

Run it normally as the affected user. No application window is expected. Check that the process reappears, then copy fresh text from the source and test Paste.

If clipboard failure prevents sharing diagnostic output, take a screenshot or photograph. Avoid including sensitive workbook data, usernames, or server information unnecessarily.

Method B: PowerShell Restricted to the Current Session

Open Windows PowerShell inside the affected user's remote desktop. Administrator privileges are normally unnecessary for that user's own process. Do not run this from a separate management session and expect it to repair another user's session.

$currentSessionId = (Get-Process -Id $PID).SessionId

Get-Process -Name rdpclip -ErrorAction SilentlyContinue |
    Where-Object { $_.SessionId -eq $currentSessionId } |
    Stop-Process -Force -ErrorAction Stop

Start-Process -FilePath "$env:SystemRoot\System32\rdpclip.exe"

The session filter limits termination to the current PowerShell session. If no clipboard process exists, the last command starts it. If an access error appears, stop and check which account and session you are using.

Verify the current session's process:

Get-Process -Name rdpclip -ErrorAction SilentlyContinue |
    Where-Object { $_.SessionId -eq (Get-Process -Id $PID).SessionId } |
    Select-Object Id, ProcessName, SessionId

A result confirms process presence, not successful redirection. If nothing appears after a few seconds, investigate a launch failure or immediate exit.

Method C: Command Prompt with an Explicit Session Filter

Inside the affected user's session, open Command Prompt and identify the session:

query user

The current session is marked with a greater-than sign. The following example assumes its session ID is 3. Replace 3 with the verified current session ID.

taskkill /F /FI "SESSION eq 3" /IM rdpclip.exe
start "" "%SystemRoot%\System32\rdpclip.exe"
tasklist /FI "IMAGENAME eq rdpclip.exe" /FI "SESSION eq 3"

The empty quoted string is the title argument used by Command Prompt's start command. A process-not-found message from the first command can mean there was nothing to stop; continue with the start command. Other errors require investigation.

4. Resolve “Not Recognized,” Missing File, or No Window

The message “is not recognized as an internal or external command, operable program or batch file” means Command Prompt could not resolve the entered command. The exact text before that message matters. Check spelling, the shell in use, and the executable path.

In Command Prompt, check the file:

dir "%SystemRoot%\System32\rdpclip.exe"

In PowerShell, use:

Test-Path "$env:SystemRoot\System32\rdpclip.exe"

If it returns True, the file exists at that path. Start it with PowerShell syntax:

Start-Process -FilePath "$env:SystemRoot\System32\rdpclip.exe"

• No window: Expected for this background process; check Task Manager.
• File missing: Confirm the host and Windows installation path. Ask the administrator to investigate Windows component health; do not download a replacement executable from an unofficial site.
• Access denied: Check the account, session, and application-control or security logs.
• Process immediately exits: Review relevant Application events and compare with a new session.

Command Prompt uses percent-sign environment variables; PowerShell uses its own environment-variable syntax. Pasting one shell's command into the other can cause misleading results.

5. Sign Out Completely and Sign In Again

If restarting the process and reconnecting do not help, create a fresh user session.

1. Save documents and close applications in the affected remote session.
2. Use the remote Windows Start menu's account option to select Sign out.
3. Connect again and sign in.
4. Test Notepad transfer before opening the usual applications, then test Excel.

If copying works initially and fails after a particular application opens, record that sequence. If the issue occurs only from one local computer, save local work and restart that computer before considering a server-wide restart.

6. Check Server Policies and Deployment Settings

Administrator task: Check the effective clipboard policy, especially when many users are affected or clipboard transfer has never worked. A process restart cannot override a policy that blocks redirection.

In the applicable Group Policy, navigate to:

Computer Configuration
  Policies
    Administrative Templates
      Windows Components
        Remote Desktop Services
          Remote Desktop Session Host
            Device and Resource Redirection

The local policy editor omits the Policies level. Review Do not allow Clipboard redirection: Enabled blocks redirection; Disabled removes this policy's block. Not configured does not guarantee access when another management layer restricts it.

For domain-managed servers, inspect the policy that actually applies rather than relying only on the local editor. In an elevated Command Prompt on the server, create a computer-policy report:

gpresult /scope computer /h "%TEMP%\RDP-Computer-Policy.html" /f

Open the report from the administrator's temporary folder. Review user-scoped restrictions for the affected user where applicable; a report for the administrator does not represent another user's policies. Keep reports private because they can contain environment details.

For an RDS deployment, also inspect collection Client Settings and applicable RD Gateway redirection restrictions. For Azure Virtual Desktop, inspect host-pool RDP properties. The most restrictive applicable control can determine the result.

Follow the relevant policy's activation requirements. Microsoft's clipboard configuration procedure includes restarting the session hosts after the policy applies; a reconnect alone should not be assumed sufficient for every policy change.

Rollback: Restore the original value in the same management policy, allow it to apply, and repeat any required restart and verification. Avoid editing unrelated registry values to counter a managed restriction.

7. Troubleshoot Excel Separately When Needed

If copying between remote Notepad windows works but copying cells entirely inside remote Excel fails, use a blank workbook to separate application-wide failures from a problem in one workbook. Finish cell editing with Enter and use a simple unmerged cell in an editable sheet.

1. Save and close the affected user's Excel workbooks, reopen Excel, and retest.
2. If a blank workbook works, investigate the original workbook's protection, selected range, and exact error message.
3. If Excel still fails, close that user's Excel windows and start Excel in Safe Mode through the remote Run dialog:

excel /safe

Safe Mode bypasses several startup customizations and add-ins. If it helps, record the current configuration and investigate COM add-ins through File > Options > Add-ins > Manage: COM Add-ins > Go. Disable them for isolation, restart normally, and re-enable them individually to identify a reproducible trigger. Restore unrelated add-ins afterward.

If the failure persists, have the administrator review Office updates and repair options. Office repair on a shared server can affect other users, so schedule it appropriately. Do not terminate every Excel process on the server to fix one user's workbook.

8. Handling Clipboard Problems Across All RDP Users

An administrator's ordinary process-start command does not launch a separate clipboard process in every logged-in user's desktop. Each session needs the correct user security context and interactive session.

Finding a user's Explorer process and invoking Win32_Process.Create does not make the new process inherit that user's session. Microsoft also documents that this WMI method cannot start an interactive process remotely. Parsing session IDs alone does not solve that problem.

Advanced implementations can obtain a session user's token and launch in that user's interactive desktop with Windows APIs. A scheduled task running only as SYSTEM is not, by itself, a solution: the clipboard process must run in the intended user's session. Likewise, a task associated with a username does not necessarily select a particular session when the account has several.

Test custom automation on one identified session first, confirm the process owner and session ID, and verify actual copying. Do not deploy an untested script to all sessions merely because it reports that process creation succeeded.

9. Restart the Windows Server When Appropriate

Why a Restart Can Help

A server restart ends existing user sessions and running processes, restarts Windows and its services, and lets users establish new RDP sessions. That broader reset can clear a temporary condition that survives restarting a single clipboard process. A restart may also be needed to activate an approved policy change or complete maintenance.

In the incident behind this guide, the user reported that restarting the server resolved the issue after clipboard troubleshooting. That is evidence of successful recovery in that incident. It does not prove whether the cause was a stalled process, an application interaction, a session problem, or another Windows component.

A restart is therefore a legitimate recovery option, especially for widespread disruption. It does not correct a deliberately blocked clipboard policy, and repeatedly rebooting without investigation can hide a recurring fault.

Before Restarting a Shared Server

1. Notify all affected users and agree on a maintenance window. Ask them to save work and sign out.
2. Review logged-in sessions, including disconnected users who may still have open applications. An administrator can run:

query user

3. Check scheduled jobs and other workloads on the host. Follow the operational procedure for those services.
4. Confirm an appropriate recovery path, such as hypervisor or remote management console access, in case RDP does not return.
5. If the issue recurs, capture the failure time and relevant logs before restarting, provided that doing so does not unreasonably delay recovery.
6. For a managed RDS farm, coordinate host draining and capacity with the deployment administrator.

Restart Procedure

Administrator procedure: After the maintenance checks, use the server's Start menu power options to select Restart. Enter an appropriate reason if Windows Server requests it. A graceful Windows restart is preferable to abruptly resetting power.

Alternatively, an administrator with the required shutdown right can run this in Command Prompt on the intended server to schedule a restart in five minutes:

shutdown /r /t 300 /d p:0:0 /c "Planned restart to recover RDP clipboard functionality"

This requests a restart, sets a 300-second delay, and records a planned reason. To cancel during the countdown, run a separate command on that server:

shutdown /a

Once shutdown has begun, cancellation may no longer be possible. A restart cannot restore unsaved application work.

Verify After the Server Returns

1. Confirm that the server and expected services are available.
2. Reconnect with a previously affected user account.
3. Test short text from local Notepad to remote Notepad and in the opposite direction.
4. Test copying between remote applications, then between cells in a blank remote Excel workbook.
5. If several users were affected, have more than one of them confirm recovery.
6. Record the recovery time and whether the failure returns after normal applications are opened.

If only Excel remains affected, return to Excel troubleshooting. If RDP transfer still fails, review effective policy and client settings instead of immediately repeating the reboot.

10. Investigate Recurring Failures

If a restart restores copying only temporarily, record enough information to distinguish repeated symptoms from a confirmed cause:

• Which users, session IDs, client devices, and session hosts are affected.
• Whether the failure involves text, cells, images, files, or a particular transfer direction.
• The first failure time and any preceding application launch, reconnect, update, or policy change.
• Whether a fresh session works and how long recovery lasts.
• Relevant Application and System events, RDS operational events where available, and resource pressure at the time.

Compare Windows and Office update levels with vendor guidance, and investigate reproducible application or add-in triggers. Missing system files or repeated crashes justify a separate Windows component-repair investigation. Do not disable antivirus, data-loss prevention, or application-control protections as a blanket clipboard fix.

Frequently Asked Questions

Should I restart Remote Desktop Services instead of the server?

Restarting Remote Desktop Services can interrupt connections and remove the administrator's remote access. Treat it as an administrator-controlled maintenance operation with console access available, not a routine first step for clipboard problems. Restarting one user's clipboard process has a much smaller impact.

Does Windows clipboard history need to be enabled?

No. Clipboard history and cloud clipboard synchronization are separate features from ordinary RDP clipboard redirection. Enabling them is not a substitute for checking the RDP connection and its policies.

Why does text copy successfully while files fail?

File transfer has additional restrictions. Microsoft documents that disabling drive redirection can also block clipboard file transfer while leaving text and images unaffected. Investigate the file-transfer path and policy rather than assuming the entire clipboard is broken.

Is a scheduled nightly restart a permanent solution?

No. An agreed restart schedule can be a temporary operational workaround, but it creates downtime and does not identify a recurring defect. Track recurrence and pursue the underlying application, session, policy, or operating-system issue.

What should be recorded when a reboot solves the problem?

Record that clipboard functionality was restored after a planned server restart, list the verification tests that passed, and state that the root cause remains unconfirmed unless logs or reproducible testing establish it.

Sources

• Microsoft Learn: Configure clipboard redirection over the Remote Desktop Protocol
• Microsoft Learn: taskkill command and session filters
• Microsoft Learn: start command syntax
• Microsoft Learn: PowerShell Start-Process
• Microsoft Learn: query user
• Microsoft Learn: gpresult
• Microsoft Learn: Remote Desktop policy definitions
• Microsoft Support: Excel not responding, hangs, freezes, or stops working
• Microsoft Learn: Win32_Process.Create limitations
• Microsoft Learn: WTSQueryUserToken and session user tokens
• Microsoft Learn: shutdown command, restart timeout, and cancellation