If Ctrl+C / Ctrl+V randomly stopped working in Excel this month and you assumed you were losing it — you're not. Microsoft broke it. With a security update. On the single most-used keyboard shortcut on Earth.
Here's the whole thing in 60 seconds so you can get back to work.
What broke
The September 2026 security update KB5002914 makes copy-paste silently fail in Excel. You press Ctrl+C, select a destination, press Ctrl+V — and nothing happens. The source stays selected, the destination is unchanged, and there's no error, no beep, no dialog. Just… nothing. Which is why it drives people up the wall — it looks like you did something wrong.
It's not only paste. AutoFill, formula dragging, and number-series fill can break the same way.
Who's affected
Excel 2016, 2019, 2021, and 2024. For MSI Office 2016, the offending update is specifically KB5002914.
The fix (do this, not the obvious thing)
The obvious move — uninstall the update — technically restores copy-paste, but don't. It's a security update; removing it re-opens whatever it patched. You'd be trading a paste bug for a real vulnerability.
Instead:
Install KB5002665 (released September 16, 2026). It specifically fixes the KB5002914 copy-paste regression for Excel 2016 — while keeping the security fix in place.
Run your update check and pull KB5002665. If your build isn't covered yet, the temporary workarounds are right-click → Copy/Paste (the ribbon and context-menu paths still work) or Paste Special, until you can patch.
The 15-second version
- Symptom: Ctrl+C/Ctrl+V silently does nothing in Excel; AutoFill/drag-fill too.
- Cause: security update KB5002914 (Sept 2026).
- Affected: Excel 2016 / 2019 / 2021 / 2024.
- Fix: install KB5002665. Do not just uninstall the security update.
- Meanwhile: right-click copy/paste still works.
There's a small, dark lesson in here too: a security patch quietly broke the most basic thing a spreadsheet does, and shipped with no visible error when it failed. The scariest bugs aren't the ones that crash — they're the ones that fail silently and let you blame yourself.
Did KB5002914 get you too — and did KB5002665 actually fix it on your build? Confirm below so the next person Googling this at 2pm knows it works. 👇
I write about the tools we all depend on and the ways they quietly break. Follow me here if that's your lane. 👋
Top comments (0)