Forum Discussion

jkimble5's avatar
jkimble5
Copper Contributor
Aug 14, 2026

Word crashes when Add-In attaches a template

We have been running a Word Add-In successfully for decades.  Since Version 2606 (Build 20131.20154) the app is crashing when it loads a Macro-enabled template to a document.  This crash happens without any warning or error message and when opening Word again, if brings up a message to disable the Add-In.  In Version 2606 (Build 20131.20154) and earlier, this did not happen.  What has change since Version 2606 (Build 20131.20154) that could be causing this issue?

5 Replies

  • jkimble5's avatar
    jkimble5
    Copper Contributor

    Thanks for all the insights.  We have determined that the root cause was an 8-byte memory overflow in the plug-in code.  The issue was initially introduced with the x64 release, but still not a problem until the 2607 version of Word.

  • NikolinoDE's avatar
    NikolinoDE
    Platinum Contributor

    This is likely a regression introduced in Word Version 2606 (Build 20131.20154), which was a Current Channel build from July 14, 2026 and included multiple Word security updates. A silent crash when a COM add-in programmatically attaches a macro-enabled template—with no error message and Word later disabling the add-in—strongly points to a Word-side issue rather than your decades-old add-in or template.

    The earlier response suggesting “attaching vs. loading” is not the root cause here, although loading the template as a global add-in may serve as a temporary workaround. If your add-in uses AttachedTemplate, the crash likely occurs during that call, not simply because you are loading the template as a global template.

    To confirm and resolve:

     1. Check the faulting module
    Reproduce the crash, then open Event Viewer → Windows Logs → Application. Look for Event ID 1000 with WINWORD.EXE. Note the Faulting module name (e.g., vbe7.dll, wwlib.dll, mso.dll) and Exception code.

     2. Test with an empty macro-enabled template
    Create a brand-new .dotm with no code and attach it via your add-in.

    • If it crashes → the problem is the attachment call itself.
    • If it works → the existing template’s VBA project is triggering the bug.

     3. Roll back to the last good build
    If you have admin rights, close all Office apps, then run this command on a test machine to revert to the previous Current Channel build (20131.20126):

    "%ProgramFiles%\Common Files\Microsoft Shared\ClickToRun\OfficeC2RClient.exe" /update user updatetoversion=16.0.20131.20126

    This will confirm whether the crash is build-specific.

     4. Report to Microsoft
    Use the Word Feedback button (or the Feedback Hub) and include: build number, crash details from Event Viewer, and the exact steps to reproduce. Microsoft does monitor these reports, even if they do not reply directly.

    Do not modify your add-in or rebuild the template yet. The evidence points to a Word regression, and changing your working components now could mask the real issue.

    If you can provide the Event Viewer entry from one of the crashes, it may be possible to analyze it against likely Word/VBA/COM failure paths. That will be much more informative than doing speculative template repairs.

    My answers are voluntary and without guarantee!

     

    Hope this will help you.

  • jkimble5's avatar
    jkimble5
    Copper Contributor

    Understood.  Thanks for the suggestions.  Mainly just trying multiple avenues on this one to see if anyone has experienced this or something similar with the latest build.

  • Charles_Kenyon's avatar
    Charles_Kenyon
    Bronze Contributor

    This is a user-to-user support forum.

    Microsoft is not hearing about your problems from what you post here. You are discussing a problem with your fellow users here. We can give good advice about how to work with Word as it is and give suggestions for making it work properly. Such troubleshooting, advice, and suggestions may be exactly what you need.

    If you want to send a message to Microsoft, though, designers and their supervisors do see feedback. (You will almost certainly not get a direct response to that feedback but they do see it.)

    Here is more about that:

    https://answers.microsoft.com/en-us/msoffice/forum/all/giving-feedback-on-microsoft-word-or-other/8df81a9b-84aa-46ef-bf88-24fb7fec96ba

    I suggest using the public feedback portal so other users can see your feedback, comment and vote. If you want, you can post the URL of your feedback with your question here to lead others with the same problem to your feedback. Be the “squeaky wheel” that gets fixed!

  • Charles_Kenyon's avatar
    Charles_Kenyon
    Bronze Contributor

    No one here can tell you what has changed since 2606.

    Your title talks about attaching a template. Your text talks about loading one. These are very different functions.

    Attaching means it becomes the attached template for the document. Macros and other resources in the template are available in the document. the Attached Document Template (https://www.addbalance.com/usersguide/templates.htm#attached)

    Loading means the template is added to the Add-Ins collection in the Word application and is available in all documents. Global Template (https://www.addbalance.com/usersguide/templates.htm#Global)

    From the message you get when restarting Word, my guess is that you are loading it as an Add-In.

    As a workaround, consider doing what you currently are not. I.e., load if currently attaching and vice versa.