Build1 publisher3 min readPublished
September's Office update stops Excel pasting on perpetual and volume installs
A dev.to writeup pins silent copy/paste failures in Excel 2016 through 2024 on KB5002914, and says MSI machines can drop the patch while volume Click-to-Run installs have to be moved back a whole build.
The Engineer · Build desk
What happened
- Excel accepts Ctrl+C and then does nothing on Ctrl+V: the copied cells keep their moving border, the destination cell stays empty, and Excel shows no error and no warning.
- A dev.to post says Microsoft has confirmed the problem in KB5002914 and that it can affect Excel 2016, 2019, 2021 and 2024.
- AutoFill, formula dragging and number series can fail on the same machines, so a dragged fill handle may not extend 1, 2, 3, 4 correctly and copied ranges can come out wrong or missing.
- On the MSI edition of Office 2016, the named culprit is Excel security update KB5002914, and removing it restored normal copy/paste behaviour on affected installations.
- Click-to-Run Office cannot uninstall a single patch, so the remedy there is moving the entire Office installation back to the last known-good build.
Compiled by The EngineerSomething wrong?How this is made
Why it matters
- exposure A failed fill or a copied range can leave wrong or missing values in a saved workbook, and the screen looks normal while it happens.
- cost The rollback price is security content: the patch being removed on Office 2016 MSI machines is an Excel security update, so the fix buys a working clipboard by giving that up.
- constraint On Click-to-Run, a one-application bug becomes an estate-wide build change, and every other Office application on the machine moves back with Excel.
- decision A paste that also fails in Notepad changes the triage order: it belongs with the clipboard and endpoint stack. Office build management stays out of most of these tickets.
The differential diagnosis comes first, because it decides which team owns the ticket. On affected machines Ctrl+C and Ctrl+V still work in Notepad and other applications, and failure confined to Excel makes the Office regression the strong candidate, according to the dev.to post [5]. If pasting fails everywhere, the same post sends you to the keyboard, the clipboard service, RDP redirection, endpoint protection, or a third-party clipboard manager [6].
Identification after that is a registry read. Run PowerShell elevated and pull ProductReleaseIds, VersionToReport, Platform and ClientFolder from HKLM:\SOFTWARE\Microsoft\Office\ClickToRun\Configuration and its WOW6432Node twin [7]. The sample output in the post is ProductReleaseIds Standard2021Volume, VersionToReport 16.0.14334.20914, Platform x64 [8].
Set that against the pre-incident target the post gives for Office LTSC 2021 Volume, 16.0.14334.20848 [14]. Both strings start 16.0.14334, and only the last field moves, by 66 [19]. An inventory query that groups machines on major.minor.build will therefore count broken and known-good LTSC 2021 machines as one population. The other two targets are 16.0.10417.20197 for Office 2019 Volume and 16.0.17932.20910 for Office LTSC 2024 Volume [14].
If the ClickToRun keys return nothing, the install may be MSI-based, and the post enumerates the Uninstall hives filtering DisplayName on 'Microsoft Office|Microsoft 365' [9]. Before removing anything, verify the update is present in installed programs or that EXCEL.EXE is the affected build. Then take it out through Settings, Apps, Installed apps, or Control Panel's View installed updates, and reboot [11]. KB5002914 is the Office and Excel update, not a Windows cumulative update, and the post is explicit about not blindly uninstalling LCUs [12].
Microsoft documents the Office Deployment Tool method for reverting Click-to-Run. Anyone running a large environment should drive it through ODT, Group Policy or their endpoint-management platform, the post says, instead of typing a different build number by hand [15].
For smaller estates the author published a PowerShell helper called Excel-CopyPaste-Issue-Fixer. It detects the 2019, 2021 and 2024 Volume Click-to-Run editions and the Office 2016 MSI case, sets the approved target build, starts the installed Click-to-Run client and waits for the expected build. On unsupported products it stops [16]. The repository reference in the post is followed by the line "Replace that URL with your real repository URL before publishing this post" [17]. You cannot audit a script you cannot fetch. One detail in the invocation is right and often misread: -ExecutionPolicy Bypass applies only to that PowerShell process and does not permanently loosen the machine's execution-policy setting [18].
The record here is a single dev.to post, which reports Microsoft's confirmation in KB5002914 without reproducing the article's text [2]. Its own guidance is to test on one machine first, especially for a fleet [4].
What to watch
- Whether Microsoft supersedes KB5002914 with a corrected Excel update. A corrected update sets the end date for pinned builds.
- Whether subscription Microsoft 365 Apps channels show the same failure; the known-good list stops at 2019, LTSC 2021 and LTSC 2024 volume builds.
- Whether machines moved back to 16.0.14334.20848 are re-offered the same update by the channel that delivered it.