Intermittent Excel crashes with VBA and VSTO add-ins after Version 2608 update

Raiyan Ahmed 0 Reputation points
2026-10-08T16:13:56.26+00:00

Hello,

Since the initial release of Microsoft 365 Apps Version 2608 around August 18, 2026, multiple users have experienced intermittent Excel crashes.

Affected environment:

  • Monthly Enterprise Channel Version 2608, Build 20326.20142
  • 64-bit Excel on Windows 11
  • Both physical laptops and virtual desktops
  • VBA workbooks and files using the OneStream VSTO/COM add-in

Excel may crash while opening a workbook, running macros, refreshing, or submitting data. The same operation may later succeed without changes. Safe Mode appears stable, and one user reported that downgrading Excel resolved the issue.

Microsoft’s dump analysis identified a VBA stack overflow in VBE7.DLL, but the exact call chain has not been captured yet since TTD trace ends up causing excel hang issues. We also tested an endpoint-security exception without resolving the issue.

Has anyone seen similar VBA or add-in compatibility problems with Version 2608? Is there a recommended earlier build for a controlled rollback test?

Microsoft 365 and Office | Development | Other
0 comments No comments

1 answer

Sort by: Newest
  1. Lin v 1,550 Reputation points Independent Advisor
    2026-10-08T17:01:04.6766667+00:00

    Hi Raiyan,

    Thank you for providing the detailed information.

    Based on your description, may I ask if you have tested with the OneStream VSTO/COM add-in temporarily disabled?

    Since Excel appears stable in Safe Mode, this may help determine whether the issue is related to the add-in itself or its interaction with Version 2608.

    If the issue persists with the add-in disabled, and given the troubleshooting already completed, I would suggest engaging Microsoft Support if you haven't already done so. If you do not have the necessary permissions to open a support request, you may need to work with your administrator or IT team to do so.

    I also noticed that one user reportedly regained stability after rolling back to an earlier build. You may consider validating the same rollback on a small group of affected users. If the older build proves stable, it could serve as a temporary workaround while the issue is being investigated further.

    I hope everything gets sorted out soon.

    Was this answer helpful?


Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.