Microsoft has confirmed a frustrating regression in Excel after the September 2026 security update KB5002914: in some cases, normal copy and paste operations simply do not complete. For organizations that rely on spreadsheets for finance, operations, reporting, inventory, scheduling, and day-to-day analysis, this is more than a minor annoyance. A silent paste failure can interrupt workflows and, worse, create uncertainty about whether data moved correctly.
The important point for IT teams is that KB5002914 is not a feature update that can be casually removed. It is a security release for Excel, and Windows Latest reports that it addresses more than two dozen vulnerabilities. That means the safest response is to treat this as a security-update incident with a productivity workaround, not as a reason to broadly uninstall patches.
What is affected
According to Microsoft’s acknowledgement, the issue affects supported desktop versions of Excel, including Excel 2016, Excel 2019, Excel 2021, and Excel 2024. Reports cited by Windows Latest indicate the bug is not limited to one Windows release; users have seen it on both Windows 10 and Windows 11 systems.
The behavior is especially disruptive because it may fail silently. A user copies a cell or range, selects a destination, and tries to paste. Instead of updating the destination, Excel leaves the source selection active and provides no obvious error in many cases. That lack of feedback can make users repeat the operation several times, restart Excel, or assume a workbook is corrupted when the real trigger is the recent Excel security update.
Windows Latest also notes user reports of related symptoms such as trouble dragging cells to copy formulas, though Microsoft’s confirmed issue is the paste operation failure. Some users have also reported crashes, but administrators should treat those as separate evidence to collect rather than assuming every Excel crash has the same root cause.
Why uninstalling the update is a risky fix
It is understandable that affected users will ask to roll back the update. Copy and paste is one of Excel’s most basic functions, and when it breaks, productivity can fall quickly. However, removing a security update across a fleet can reopen vulnerabilities that the patch was designed to close.
A better default posture is to keep KB5002914 installed unless a narrowly scoped business-critical exception is approved. If your organization has a formal patch exception process, use it. Document which machines are affected, what business process is blocked, what compensating controls are in place, and when the exception will be reviewed. Avoid informal one-off removals that leave endpoints in an unknown security state.
For home users and enthusiasts, the same general advice applies: do not rush to uninstall the update just because copy and paste is misbehaving. Try the workarounds first and watch for Microsoft guidance or a follow-up fix.
Practical workarounds to share with users
The most useful workaround reported so far is Paste Special. After copying the needed cells, select the destination cell and press Ctrl+Alt+V to open the Paste Special dialog. From there, choose Values or Formulas depending on what you need.
That distinction matters. Choosing Values pastes the displayed results only, turning calculated results into fixed numbers. Choosing Formulas keeps the formulas but may not preserve all formatting. Users who work with financial models, operational dashboards, or linked workbooks should be told clearly which option is appropriate for their task.
Another workaround is to use Word as an intermediate step: paste the Excel selection into Word, copy it again from Word, and then paste back into Excel. This can help move data, but it is not a perfect substitute. Formatting, formulas, and workbook-specific behavior may not survive the round trip, so it should be used for simple data transfer rather than complex spreadsheet logic.
If Excel crashes rather than silently failing, administrators can check Event Viewer for Excel-related application errors. Record the Excel version, Office channel, Windows version, exception code, workbook type, and whether the issue reproduces in a new blank workbook. That information will be useful for support escalation and for determining whether the environment is seeing only the confirmed paste bug or additional instability.
What administrators should do today
Start by confirming scope. Ask users to test a simple copy-and-paste operation in a new workbook, not only in a production spreadsheet. If the problem appears in a clean workbook, it is more likely to be the Excel regression rather than a damaged file, add-in conflict, or protected workbook setting.
Next, publish a short internal advisory. Include the symptoms, the affected Excel versions, the Paste Special workaround, and the instruction not to remove updates without IT approval. Help desk teams should have a standard response ready so they do not spend hours troubleshooting clipboard services, profiles, or unrelated Windows settings.
Finally, monitor Microsoft’s update channels for a fix. Because this is a confirmed regression in a security update, a servicing update or emergency fix is possible. Until then, the right balance is to preserve security coverage while giving users a reliable way to continue working.
For organizations heavily dependent on Excel, this incident is also a reminder to test Office security updates against representative workflows where possible. Copy, paste, formula fill, add-ins, macros, and exports are not glamorous test cases, but they are exactly the everyday operations that can cause business disruption when they regress.
Source: Windows Latest source