Free tools Windows power users keep installed
One-click scans. No signup required.
iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
If Word for Microsoft 365 closes while a document or case-management application is generating a file from a template, the symptom matches a Microsoft-documented Word issue affecting Version 2608 (Build 20326.x). Microsoft says the Word team mitigated that issue and marks it fixed, but its notice does not identify a fixed build or a manual remedy. First verify that your workflow matches the notice, then update Office and use Safe Mode and add-in isolation to investigate any crash that remains.
What Microsoft has confirmed about the crash
Microsoft describes a failure in which Word for Microsoft 365 closes unexpectedly after a third-party document or case-management application attempts to generate and populate a document template. The published issue applies to Word for Microsoft 365 and specifically references Version 2608, Build 20326.x. It does not say that every external application is affected, and it does not name the applications involved.
Microsoft’s issue notice was last updated on September 14, 2026. It states that “The Word Team has mitigated the issue” and marks the incident fixed. That status means Microsoft has applied a mitigation in its service or product delivery process; the notice does not state which build contains the change, whether a particular update channel receives it first, or which button a user must press to install it. Do not infer a specific fixed build from the notice.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →If the behavior continues, treat it as either a remaining instance of the same workflow problem or a different Word, add-in, template, or Office-installation failure. The diagnostic steps below separate those possibilities without assuming that disabling an add-in is the confirmed fix for this particular incident.
#1 Best Overall
- 14" diagonal, 1366x768 resolution, HD BrightView LED, Glossy NON-TOUCH Display
Confirm that your symptom matches the documented issue
Before changing templates or Windows settings, reproduce the failure carefully and compare it with Microsoft’s description. A close match has all of the following characteristics:
- Word for Microsoft 365 on Windows is the application that closes.
- The closure happens while another program is generating a document and inserting data into a Word template, rather than while you are simply typing or opening a normal file.
- The external program is a document-production or case-management application. Microsoft does not publish a list of affected vendors.
- The installation is in the Version 2608 family, shown with a Build 20326.x number.
To check the installed version, open Word and choose File > Account. Under Product Information, read the product name and update channel, then choose About Word to see the complete version and build. Record the values before troubleshooting. If Word cannot remain open long enough to show this screen, open another Office application and check its account page; the installed Office build is normally shared across the suite.
A crash that occurs when you open a .docx manually, print, use a macro, or perform a mail merge may have another cause. The trigger matters more than the fact that Word closes.
Recommended Free Tools
What “fixed” means—and what it does not tell you
The September 2026 Microsoft issue index lists the third-party template-population problem as fixed, consistent with the issue notice’s statement that it was mitigated. Neither page supplies a fixed build number, a download link, or a documented workaround specific to the incident. Consequently:
- Do not tell users to install an unverified build number.
- Do not assume that reinstalling Word is required to receive the mitigation.
- Do not claim that every template-generating application has the same defect.
- Do not present add-in removal as Microsoft’s confirmed incident fix; it is a general diagnostic.
Office update delivery can also vary by update channel and organizational policy. An organization may defer updates through its deployment controls, while a personal installation may receive them on a different schedule. Checking for updates is therefore sensible, but the public status entry does not let you predict exactly when a particular computer received the mitigation.
Step-by-step troubleshooting
1. Capture the exact trigger
Write down the sequence that precedes the closure. Note the name and version of the external application, the template file extension, whether fields, tables, or content controls are being populated, and whether Word closes before or after the generated document appears. Try the same template from Word itself, if the workflow permits, without launching the external application. This comparison helps establish whether the handoff between programs is essential.
Also record whether the failure happens every time, only with one template, or only with a particular record or data set. A single damaged template or malformed field can look like a general application crash but requires a different investigation.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsRank #2
- 256 GB SSD of storage.
- Multitasking is easy with 16GB of RAM
- Equipped with a blazing fast Core i5 2.00 GHz processor.
2. Install available Office updates
Microsoft’s general Office crash guidance recommends making sure Office is current. In Word or another Office application:
- Choose File > Account.
- Under Product Information, open Update Options.
- Choose Update Now and allow the update process to finish.
- Restart Windows if Office requests it, then repeat the same template-generation action.
If Update Options is missing, your organization may manage Office centrally, or the installation may use a different update policy. Contact the administrator rather than downloading an installer from an unrelated site. After updating, check About Word again and retain the new build number in your notes.
3. Test Word in Safe Mode
Safe Mode starts Word without most add-ins and custom startup components. It is a diagnostic, not proof that the documented incident has been fixed.
- Close all Word windows.
- Press Windows key + R to open the Run dialog.
- Enter
winword /safeand press Enter. - In the Safe Mode window, open a harmless copy of the template or perform a controlled test that does not overwrite production documents.
If the crash disappears in Safe Mode, an add-in or startup customization becomes more likely. If Word still closes in Safe Mode, an add-in is less likely to be the immediate cause; continue with Office repair or your organization’s support process rather than repeatedly deleting templates.
4. Isolate Word and COM add-ins one at a time
When Safe Mode changes the behavior, identify the component instead of disabling everything permanently.
- Start Word normally.
- Choose File > Options > Add-ins.
- At the bottom of the window, use the Manage list to select Word Add-ins, choose Go, and note the enabled items.
- Repeat the process with COM Add-ins.
- Clear one add-in’s check box, restart Word, and repeat the same external-app template operation.
- Continue one change at a time, recording which setting was changed and whether the result changed.
Testing one component per restart prevents a false conclusion. If one add-in clearly changes the result, leave it disabled only as a temporary containment measure and ask its vendor for a compatible update. Microsoft recommends vendor contact when an add-in is implicated; that recommendation is separate from the status of the third-party template-population incident.
5. Repair Office when Word also fails in Safe Mode
A crash that occurs with no add-ins loaded points toward the Office installation, a Windows component, a damaged user profile, or a problem in the external application’s automation request. Microsoft’s general Office troubleshooting path moves to repair or reinstall when update checks and add-in isolation do not resolve startup or use failures.
Rank #3
- WINDOWS 11 | STABLE PERFORMANCE: Powered by Intel Celeron N4020 processor and Windows 11 system, this laptop delivers stable performance for everyday computing tasks. It supports web browsing, online learning, document editing, email communication, and basic office work with optimized power efficiency, providing a practical and reliable experience for essential daily use for daily use.
- 15.6” FHD IPS DISPLAY: Features a 15.6-inch Full HD IPS display with narrow bezels, offering wider viewing angles and clearer image details compared to standard panels. The improved screen-to-body ratio enhances visual experience for study, reading, document work, and video playback, making it suitable for both productivity and entertainment use.
- 4GB DDR4 + 128GB eMMC STORAGE: Equipped with 4GB DDR4 memory and 128GB eMMC storage for everyday basics such as browsing, documents, email, and online learning platforms. The built-in TF card slot supports storage expansion up to 1TB, giving you more flexibility for files, photos, videos, and daily documents. TF card not included.
- CONNECTIVITY & PORTS: Includes 1× TF card slot, 2× USB 3.2 Gen1 ports, and 2× full-featured Type-C ports (USB 3.2 Gen1). The Type-C ports support data transfer, charging, and video output, enabling flexible connection with external devices such as monitors, storage, and peripherals for daily work and study use.
- LIGHTWEIGHT DESIGN | ONLINE COMMUNICATION: Designed with a slim, portable profile, this laptop is easy to carry for school, commuting, and travel. A built-in 1MP front camera supports online classes, video meetings, remote communication, and everyday conferencing. The 3300mAh battery works with the low-power system design to support practical daily use, while thermal optimization helps maintain quieter operation during extended tasks.
Use your organization’s approved Office repair procedure. On a personally managed Windows installation, open Settings > Apps > Installed apps, select the Microsoft 365 installation, choose Modify, and follow the available repair choices. A quick repair normally changes fewer local files; an online repair can replace more of the installation and may require a longer download and sign-in. The exact choices can vary by installation type and administrator policy, so save documents and confirm that you know your account credentials before starting.
Repair is a general recovery step, not evidence that the known template incident was caused by corrupted Office files. If repair changes nothing, compare the same workflow on a separate Windows user profile or a managed test computer and provide the results to IT and the external-application vendor.
6. Treat Normal.dotm as a later diagnostic
Word stores many personal defaults in Normal.dotm. Microsoft’s Word troubleshooting guidance says that renaming this file forces Word to create a new copy. The reset can remove or reset custom styles, toolbars, macros, and AutoText, so it should not be the first response to a Microsoft-documented incident.
- Close Word and every process that may be using it.
- Locate the existing
Normal.dotmin the user’s Word templates location. - Rename it rather than deleting it, for example by adding
.oldto the filename. - Start Word and test the workflow with a copy of the template.
- If the problem is unchanged, close Word and restore the original filename. If the reset helps, recover needed customizations selectively from the retained file.
Do not use this step if your organization depends on macros or carefully maintained AutoText without first arranging a backup and a recovery plan.
7. Give the external-application vendor useful evidence
Microsoft does not identify the affected third-party applications, so the vendor needs reproducible details to determine whether its automation layer is involved. Send:
- Word product, update channel, full version, and build.
- Windows edition and whether the computer is managed by an organization.
- The external application’s name and version, with a description of the generation action.
- The template extension and a sanitized copy or minimal reproduction template, if policy permits.
- The exact time of a failure, frequency, and whether Safe Mode changes it.
- The list of Word and COM add-ins tested, including the one-at-a-time results.
- Whether Office Update Now, repair, or a second Windows profile changed the behavior.
Remove confidential case data and personal information before sharing files or logs. A vendor can then compare its automation calls with supported Word behavior instead of treating the report as a generic “Word crash.”
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Use the right diagnostic branch
| Observed behavior | Most useful next step | What the result establishes |
|---|---|---|
| Word closes only while an external document or case-management app populates a template, and the build is Version 2608 (Build 20326.x). | Install available Office updates, retest, and document the external app and template details. | The workflow closely matches Microsoft’s mitigated incident; the public notice still does not provide a fixed build number. |
The same operation works in winword /safe but fails in normal Word. |
Disable Word and COM add-ins individually, restarting after each change. | An add-in or startup customization is a plausible contributor; ask its vendor for an update if one is identified. |
| The operation fails in Safe Mode as well. | Use the Office repair path and test with a controlled template or separate Windows profile. | The failure is not explained solely by the add-ins suppressed by Safe Mode. |
| Word closes during mail merge using a .dot or .dotm template. | Handle it as a separate issue and follow Microsoft’s current Word issue index and general troubleshooting guidance. | Microsoft listed this mail-merge crash as under investigation in September 2026; it should not be labeled the same as the third-party application incident. |
| Only one template or one data record triggers the closure. | Make a sanitized copy, remove fields or content controls in small groups, and ask the template owner or application vendor to test the minimal file. | The evidence points toward template content or input data, not necessarily an Office-wide failure. |
Do not conflate this with the .dot/.dotm mail-merge issue
Microsoft’s September 2026 Word for Windows issue index separately lists a crash during mail merge with .dot or .dotm templates as under investigation. That workflow can involve templates and automation, but it is not automatically the same defect as a case-management application populating a document. The distinction affects what you report: identify the operation, template extension, and program initiating it instead of describing every automated Word crash as one incident.
Actions that are not justified as a first fix
- Registry edits: Microsoft’s incident notice does not prescribe them, and an incorrect edit can create unrelated Windows or Office problems.
- Deleting templates: Removing production templates can destroy formatting, fields, macros, or organization-specific content. Work on copies and preserve originals.
- Immediately replacing hardware: Nothing in Microsoft’s notice indicates that a new computer or component is required.
- Buying repair software: The documented status is mitigation, and Microsoft’s general guidance already provides update, Safe Mode, add-in, and repair diagnostics.
- Disabling every add-in permanently: This can remove required workflow features and does not identify the responsible component.
A practical checklist for administrators and support desks
- Capture the Word version, build, update channel, Windows version, external application version, and template extension.
- Confirm whether the closure occurs during third-party generation and population, not a manual Word action.
- Install available Office updates through the supported File > Account > Update Options > Update Now path.
- Run
winword /safeand record whether the same controlled test succeeds. - If Safe Mode succeeds, test Word and COM add-ins individually and preserve the results.
- If Safe Mode fails, follow the approved Office repair process and test with a clean, sanitized template.
- Use a renamed copy of
Normal.dotmonly as a later diagnostic, retaining the original customizations. - Send reproducible evidence to the external application’s vendor, especially if one add-in or one template is implicated.
- Keep the mail-merge .dot/.dotm issue in a separate ticket from the third-party template-population incident.
When to escalate
Escalate to Microsoft or organizational IT when Word crashes across multiple templates and external applications, fails in Safe Mode, or remains unstable after supported Office repair. Escalate to the document or case-management vendor when the failure is limited to its generation command, disappears after one of its add-ins is disabled, or occurs only with templates its software supplies. Include the evidence checklist rather than only a screenshot of the crash dialog.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
