Copy and paste stops working in Excel when the clipboard is being held open by another program, when Excel is in Edit mode or a modal dialog is active, when protected sheets or filtered ranges block the operation, or when a COM add-in or corrupted Office cache interferes with clipboard hooks. Clearing the clipboard, pressing Esc or Enter, and restarting Excel resolves most cases.
Excel does not own the clipboard outright. It negotiates with the Windows clipboard chain, a shared queue managed by the operating system, and any program that grabs that queue without releasing it can silently break every paste in Excel. That single architectural fact explains the majority of "copy works, paste doesn't" complaints, and it is why restarting Excel fixes the symptom while leaving the root cause untouched. This guide walks through the mechanisms, the measurable triggers, the edge cases reviewers usually miss, and the specific steps that actually clear the fault.
Clipboard ownership and the broken clipboard chain
The Windows clipboard holds data in multiple formats at once. When you copy a range in Excel, the program registers several representations: plain text, rich HTML for formatting, a bitmap image, and a private "Excel 8.0" format that carries formatting, column widths, and formulas. The paste operation reads whichever format the destination and modifier keys call for. Ctrl+V takes the richest available format; Paste Special lets you force a specific one.
The clipboard is a chain of "clipboard viewers," each program that wants notification of clipboard changes. Each viewer must pass the notification to the next link. If one viewer hangs, crashes, or fails to forward, the chain breaks, and every paste request after that point stalls or fails. Excel is the most frequent victim because it is a heavy clipboard consumer that reads and writes constantly. A background clipboard manager, a screenshot utility, a remote-desktop tool, or a password manager's auto-clear feature can each occupy a link in that chain.
The practical signature of a broken chain is that Ctrl+C appears to work (the marching-ants border still displays) but Ctrl+V does nothing, produces stale data from an earlier copy, or pastes into the wrong location. Clear the clipboard immediately after copying from another program, then retry inside Excel. This is the single most effective first step and it costs about two seconds.
Edit mode, modal dialogs, and filtered ranges
Excel cannot accept a paste while it is waiting for you to finish something else. Three states block paste silently, with no error message. The first is cell edit mode: the cursor is active inside a cell rather than on the cell border. Press Enter or Esc to exit, and the normal cell-borders cursor confirms you are out of edit mode.
The second is an open modal dialog. Any modal window, including a warning about a circular reference or a data-validation prompt, suspends the worksheet beneath it. The paste keystroke goes to the dialog, not the grid. Closing the dialog restores paste behavior immediately. A subtler version occurs during a calculation-heavy recalculation, when Excel briefly defers user input; pressing Ctrl+Shift+Alt+F9 forces a full rebuild and often clears the stall.
The third, and most underdiagnosed, is a filtered or hidden range. Copying visible cells after applying a filter, then pasting without choosing Paste Special, can paste into hidden rows and shift data unpredictably. Excel's filtered paste requires explicit handling. Select the visible cells only (Alt+; on Windows), then paste; the sub-menu options for Paste Special include skip-blanks and transpose, which behave differently on filtered data.
Beyond the workstation: environment factors that fail
The same fault appears at predictable rates across environments, and the pattern points at infrastructure rather than Excel itself. Corporate machines with more than one clipboard-touching add-in show paste failures far more often than clean installs. Remote Desktop and virtual-desktop sessions (Citrix, Windows Virtual Desktop) route the clipboard through a redirection layer; when that layer drops or throttle-limits large payloads, paste fails only in the RDP window, never locally. This is a diagnostic clue: if paste fails in one browser tab but works in another program, the clipboard chain is local; if it fails only in the remote session, redirection is the cause.
Protected sheets and restricted editing account for another recurring cluster. A sheet marked as protected blocks paste into locked cells but still allows paste into unlocked cells, so the failure looks intermittent: some cells accept paste, others appear dead. Unprotecting the sheet or adjusting the allowed operations resolves it. The same applies to shared workbooks, which have restricted paste rights and frequently lock editing during another user's session.
Table: cause, typical symptom, and first fix
| Cause | Typical behavior | First action |
|---|---|---|
| Stuck clipboard chain | Copy works, paste does nothing | Clear clipboard, restart Excel |
| Cell in edit mode | No paste, cursor inside cell | Press Enter or Esc |
| Modal dialog open | All input routes to dialog | Close the dialog window |
| Protected sheet | Selective paste failure | Unprotect sheet or unlock cells |
| Filtered range | Paste lands in hidden rows | Select visible cells with Alt+; |
| COM add-in conflict | Paste fails after add-in loads | Disable add-ins, retest |
| Corrupted Office cache | Paste fails after update | Repair Office, clear clipboard cache |
Quantifying how often this is an add-in conflict
Add-ins sit between Excel and the clipboard and are the second most common root cause after a held clipboard. COM add-ins load at startup and hook clipboard events; if an add-in's hook misbehaves, paste breaks at the moment it loads, not at click time. The diagnostic pattern is timing: does paste fail on a fresh Excel session that has run for under a minute, or only after several minutes of work? A failure that appears mid-session, with no new copy action, points to an add-in or a background process rather than the clipboard chain itself.
The controlled test is to start Excel in safe mode with Ctrl held at launch. In safe mode no add-ins load and paste behavior reverts to the bare program. If paste works in safe mode and fails normally, an add-in is responsible. Re-enable add-ins one at a time until the failure returns; that identifies the culprit in a single pass, usually within one or two tests. Do not disable every add-in permanently, since the safe mode is a diagnostic state, not a working configuration. Once the add-in is identified, check for an update first, because a stale build is the usual cause.
Under the Microsoft 365 storage model, the clipboard cache is a file on disk rather than only an in-memory queue. When Excel crashes or a session is killed, the cache can be left half-written, so the next launch sees a corrupt cache and refuses paste until it is rewritten. Clearing the clipboard through Clipboard Manager or rebooting performs the rewrite. In Excel for Microsoft 365 current-channel builds, the "clipboard is corrupt" behavior is generally recoverable by closing all Office apps, waiting a few seconds, and reopening; enterprise users in a long-lived session may need to restart the machine rather than just the app.
Timeline of a clipboard fault
| Stage | What happens | Observability |
|---|---|---|
| Copy | Excel writes multiple clipboard formats | Marching-ants border appears |
| Chain handoff | Each clipboard viewer forwards notification | Typically invisible |
| Blocked chain | A viewer fails to forward | Paste begins failing silently |
| Edit mode | Excel pauses clipboard reads | No error shown |
| Safe-mode test | Add-ins skipped at launch | Paste restored |
| Cache rewrite | Disk cache regenerated on restart | Fault cleared |
Misconceptions worth correcting
The most common misconception is that copy and paste is a single operation. It is not; copy is a write to the clipboard and paste is a negotiated read from it, and each can fail independently. Second, the "paste is broken" label usually describes a partial failure: paste into the same sheet works, but paste into another workbook, another Office app, or the browser does not. Third, many users assume the marching-ants border proves the clipboard contains data; it proves only that Excel requested a copy, not that the chain was preserved. Fourth, a machine restart is not always needed: clear the clipboard and relaunch Office first, because the cache rewrite succeeds in the majority of cases without a reboot.
The counterintuitive detail is that pasting with the keyboard versus the mouse can break differently. Ctrl+V routes through the richer-format handler and is more sensitive to a corrupt format entry; the right-click Paste menu uses a different path and may succeed where the keystroke fails. Similarly, Paste Special with a narrower format (values only) frequently works when Ctrl+V does not, because it bypasses the format that is corrupt. The professional caveat is that this asymmetry makes a "fixed" system look healthy while the broken format remains latent; leaving values-only pasting as a habit can mask a clipboard that will fail again on the next formatting copy.
Practical actions and thresholds
Work through these in order; each is cheap, and most cases clear before step five. Start with the least invasive step and stop the moment paste returns. If two steps fail, jump to the safe-mode test, because that separates local causes from Office damage faster than any other check.
Clear the clipboard from another program or via Clipboard Manager, then retry in Excel. Exit edit mode with Enter or Esc, and close any open modal dialog before pasting. Copy with a narrower route when needed: use Paste Special, values only. Restart Excel first; if paste returns, restart the machine only if it fails again within the same session. Launch Excel in safe mode (Ctrl at launch) to test add-in interference, and re-enable add-ins one at a time. After an Office update, run Office repair (quick repair first, online repair only if quick fails) when paste failure coincides with the update.
Excel changing no copying can be a port monitoring or clipboard-manager issue on machines under IT control; check with the administrator before assuming Office is at fault. The repair path also has an order: quick repair preserves settings and completes in minutes, while online repair re-downloads and takes longer; do not skip to online repair unless quick repair fails. If paste failed immediately after a Windows feature update, test paste in two other programs that hold the clipboard; if it fails everywhere, the fault is in Windows, not Excel, and the Office repair will not help.
Set a personal threshold for escalation. If the failure persists after clearing the clipboard, exiting edit mode, a restart, and a safe-mode test, treat it as a corrupt Office installation or a Windows clipboard-chain fault. That combination points away from user error and toward repair or an IT ticket. The reverse also holds: if paste works in safe mode, do not repair Office; the add-in is the confirmed cause, and repair will not fix it.
What the evidence cannot settle
Clipboard failures are not rigorously studied in controlled trials, and Microsoft does not publish error rates for paste failures by version or configuration. The mechanism explanation above rests on the documented clipboard-chain architecture and the observable behavior of Office under test conditions, not on vendor statistics. The consequence is that any claim of "fixed" should be treated as provisional: the fault can return when the add-in updates, when a background utility reconnects, or when a long session accumulates clipboard state. When the cause cannot be isolated, the safe-mode test plus a registrable diagnostic log is the strongest practical evidence available, and an IT ticket describing that test result gets faster resolution than a report of "copy and paste doesn't work."
Your first move is always to answer the question the way the snippet does: clear the clipboard, exit edit mode, and restart Excel. The mechanisms behind that answer, from the clipboard chain to the disk cache to add-in hooks, determine whether the fix sticks or the problem comes back tomorrow.