Thanks for reaching out to Microsoft Q&A forum support and apologize for the inconvenience.
Based on your description and from my own research, the root cause of this issue is a memory access violation in the VBA runtime environment when the interrupt command attempts to halt execution, leaving hidden breakpoints or corrupted memory states that Excel cannot recover from, especially under the Windows 11 23H2 environment. This is recognized as a critical VBA runtime instability issue affecting enterprise usage and there is currently no permanent fix, but you can follow the workaround methods below to mitigate this issue.
Option 1: Recompile VBA code
- Open Excel first with a blank workbook.
- Hold the Shift key while opening your .xlsm file(s) to prevent auto-run macros.
- Press Alt+F11 to open the VBA Editor.
- Go to Debug > Compile VBAProject (repeat if errors appear, fixing any highlighted issues).
- Save the file and close/reopen normally.
- Repeat for all affected workbooks. This clears corruption in the VBA binary and has resolved similar random crashes. If crashes persist, export all modules/forms, create a new workbook, and import them back.
Option 2: Disable macro interruptions temporarily
- In your macro code, add
Application.EnableCancelKey=xlDisabledat the beginning. - Add
Application.EnableCancelKey=xlInterruptat the end. - This prevents Ctrl+Break from triggering the crash but still allows manual stops via the VBA Editor's Reset button if needed. Use this as a workaround for production macros, but test thoroughly, it's not ideal for debugging endless loops
In case after trying both of the above options but the problem is still not resolved, you can try to check if your software systems are fully updated by:
- Update Office to the latest build via File > Account > Update Options > Update Now.
- Test on a different machine or user profile to rule out profile-specific issues.
- Use Process Monitor (from Sysinternals) to log
Excel.exeactivity during a crash reproduction, filtering forVBE7.DLLaccesses
If these don't resolve it, could you please provide more details like a code snippet from the problematic macro or full Event Viewer XML for deeper analysis.
I am looking forward to hearing update from you
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.