Excel 2016 copy/paste issue is back after KB5002934 update
Is anyone else experiencing copy/paste issues in Excel 2016 after the KB5002934 update? We're seeing this issue on workstations across our organisation. What's frustrating is that this is the same issue we encountered before, which was supposedly fixed in a previous update. Now it's back, barely a few weeks later. For now, we're using an uninstall script to temporarily remove the update from affected workstations. However, this isn't a reliable long-term solution because Windows Update will push the update again. Is anyone else experiencing the same thing? Has Microsoft provided any explanation for why this issue keeps coming back? Has anyone found a more permanent solution that doesn't involve repeatedly uninstalling the update? I'd like to know if other organisations are dealing with this and how they're handling it.
Can't edit cells in Excel 2010 since Sept 2026 patch Tuesday
I can't edit cells in Excel 2010 spreadsheets since Sept 2026 patch Tuesday. How do I reverse this back to the former working software. There was one comment that said it might be caused by a Windows 10 security update. Since Windows 10 isn't supposed to get security updates anymore, how can that be an issue? Ron
Excel 2016 & 2019 - Conditional Formatting Affecting Pasting with Formats
As of this week, I'm having a problem with conditional formatting preventing me from pasting copied cells with any paste options that include formatting. This issue is occurring on three Win 10 and 11 computers with Excel 2016 and/or Excel 2019. For example, I can open a new excel workbook, input data into cells, format the cells and then copy and paste to new cells with the formatting pasted. But if I add conditional formatting anywhere in the sheet, I cannot paste any cell (with or without the conditional formatting) when formatting is included in the paste option is included. For, example, I can paste-values, paste-formulas, but not regular paste or paste-formatting. If I clear the conditional formatting from the sheet, the problem still exists. However, if I clear the conditional formatting from the sheet, save the file and then reopen it, the pasting of the formats gets restored. A similar issue occurred a few windows updates ago and I rolled back the update for excel and/or applied the patch KB5002914. But this is a new issue and that patch doesn't work -- the message I receive is that "The update is already installed on this system". Is this happening to anyone else? Is there a solution to fix this behavior in excel with conditional formatting? Thanks!
copy paste issue in excel 2016
Dear Microsoft Team, We have been experiencing a copy-paste issue in Microsoft Excel since 14 October 2026, following the installation of Windows Security Update KB5127648 and Microsoft Excel 2016 Security Update KB5002934. The issue is specific to Sheet1 in the affected Excel workbook. The observed behavior is as follows: Copying any cell from Sheet2 and pasting it into Sheet1 works correctly. Copying any cell from Sheet1 and pasting it into another sheet or even within the same sheet does not work. No action is performed, and no error message is displayed. Copying content from Sheet1 and pasting it into Notepad works correctly. Copying text or content from Notepad and pasting it into Sheet1 also works correctly. Based on these observations, the issue appears to be specific to copying cells from Sheet1 rather than a general clipboard malfunction. Kindly investigate this issue and advise on a permanent resolution, as it started after the installation of the aforementioned security updates.copy paste issue in excel 2016
Dear Team, the copy paste issue comming since yesterday 14 oct 2016 after updating security update kb5127648 and security update for microsoft excel 2016 kb5002934, if i copy any cell from sheet2 and paste it on sheet1 it work well but if copy any cell from sheet1 and paste on the other sheet or on the same sheet is not performing while it paste normaly in notepad file, also copy anything from notepad and paste in the sheet1 is work wellExcel x64/VBE execute AV: live segment-heap entry is PAGE_READWRITE (Windows 26H2)
Please assess this case with the Excel/VBA runtime and Windows heap teams and identify a supported serviced build or mitigation. The failure is intermittent; we are not claiming a confirmed Microsoft product defect or a specific permission-change mechanism. Environment - Windows 11 26H2, build 26300.9550; ntdll.dll 10.0.26100.9549. - Microsoft 365 Click-to-Run, Current Channel, Excel x64 16.0.20430.20146. - VBE7.DLL 7.01.1158, SHA256 8AD9E8D123B4FD84DE6DF7FC931D69A556540B38317DFCEF3B4CF7A5535D48E8. - Microsoft signatures of Excel, VBE7 and ntdll validated locally. - Kaspersky 21.27 com_antivirus.dll and product_info.dll were loaded. Their involvement is unknown; antivirus/AMSI and Windows mitigations were not disabled. - No Excel-specific heap override or AppCompat Layers override was found in the inspected locations. Excel IFEO contains MitigationOptions=256; this was not modified. Captured failure on 13 October 2026, 13:05 CEST A normally launched, separate Excel instance opened a read-only copy of a macro-enabled binary workbook. Startup and its initial data refresh completed, followed by four CalculateFullRebuild calls with EnableEvents=False, True, True, False. Each returned xlDone and ScreenUpdating=True. A first external COM helper released its references and exited. After approximately 65 seconds idle, a fresh external COM helper invoked a public Boolean status getter using Application.Run. The getter body only returns a module-level Boolean variable. CDB caught first-chance C0000005 before execution of that VBA getter body: - Exception parameter 0: 8 (execute); target 0x00000260bb2b947c. - !address: MEM_COMMIT, MEM_PRIVATE, PAGE_READWRITE (0x04), not executable. - !heap -x: live LFH Allocated block in segment heap 0x0000026091000000. - Block address 0x00000260bb2b8d70; requested size 4144; block size 4352; unused 208. - Entry bytes contain movq xmm5,r12, a load referring to VBE7!g_PPExSP, and a jump to VBE7!ProcCallEngine. - Call chain includes oleaut32!DispCallFuncAmd64, DispCallFunc, VBE7!DispCallFuncWrap, EpiInvokeMethod, CDispVbaStdMod::Invoke, EXCEL!HrGuardedDispatchInvoke, HrBookCallMacro and _HrGlobalRun. After allowing normal exception handling, Excel started its recovery process and the failing process exited with code 0. The COM caller received DISP_E_EXCEPTION (0x80020009). Thus exit code 0 and absence of a Windows crash dialog were not evidence of a healthy session. An earlier capture on the same machine showed an execute AV at another generated VBA entry during SheetCalculate dispatch. Users also reported black worksheet regions before unexpected Excel exit. We have not established that all rendering symptoms share this native cause. What has and has not been established The workbook source has no VirtualProtect/VirtualAlloc or heap-allocation calls. The runtime fault at a simple status getter is not explained by a long VBA loop or ScreenUpdating=False. The actor and moment that produced PAGE_READWRITE have not been captured. A subsequent monitored repetition, watching 18 initially executable VBA entry pages and then 22 pages after recalculation, completed without the AV or an observed matching protection-change call. Monitoring included selected overlapping NtAllocateVirtualMemoryEx/NtAllocateVirtualMemory/NtProtectVirtualMemory calls. This negative run does not retract the captured failure. A separate synthetic blank-workbook event/ordinary data-allocation test also did not reproduce this execute AV; we do not have a reliable minimal reproducer. Requested guidance 1. Is this generated VBA entry in a live 4144-byte segment-heap allocation, currently PAGE_READWRITE, consistent with a known serviced issue? 2. Which supported Office or Windows build, if any, addresses this precise failure class? 3. Which targeted next trace or supported mitigation should be used, preserving DEP/ASLR/AMSI and normal workbook functionality? 4. If further evidence is needed, please specify the minimum sanitized trace and a private support route. Full dumps and workbooks have been retained locally only. This report contains no workbook data, account identifiers, local user paths, credentials or full dump attachments. Any request for those files requires a separate decision by the owner. Related unconfirmed first-hand report under a different Windows version: https://techcommunity.microsoft.com/discussions/excelgeneral/excel-x64vbe-event-entry-loses-execute-permission-in-the-default-segment-heap/4563077 . I have not traced the same permission-changing call in my own process.
