Copilot Plugin Crash Loop in Word: Diagnostic and Reset Steps

Official documentation checked October 14, 2026.

If Word closes repeatedly when you open Copilot, first distinguish a Word application crash from an unresponsive Copilot pane. Microsoft’s Copilot in Word is an integrated Microsoft 365 experience; this guide does not assume it is a separately installed COM “Copilot plugin” that can be uninstalled or reset. A third-party add-in with a similar name needs its own vendor’s diagnosis.

Why Copilot in Word Can Appear to Enter a Crash Loop

Note whether Word itself exits, hangs, or remains open while Copilot fails to answer. Also record whether the problem starts at Word launch, at document opening, or only after a specific Copilot action. Add-ins, templates, a particular document, application faults, and Copilot connectivity can require different checks; the symptom alone does not prove any one of them.

Protect the work before testing. If Word responds, save a copy in an approved location. After an unexpected closure, review any Document Recovery files, compare their timestamps and contents, and save the versions you need. Keep undecided recovery files for later review. Recovery depends on what was saved; it cannot guarantee that all unsaved edits survived.

Diagnostic Steps to Isolate the Cause

1. Record the crash pattern. Note Windows and Word versions, the time, the account type, and the last action before the failure. Give IT any available crash report through the approved support route. Avoid repeatedly forcing Word to end while it has unsaved work; if it cannot respond, tell support what remains at risk.
2. Compare an ordinary blank document. After preserving your files, start Word normally and open a blank document without invoking Copilot. Then test Copilot with a harmless drafting request in an authorized test document. If ordinary Word also crashes, investigate the application first. If Word stays open and only Copilot fails, start with its service, account, or connection checks instead of resetting Word’s configuration.
3. Compare the affected document carefully. If only one document triggers a crash, keep the original and test an approved copy. File-specific failure is a clue, not proof of corruption. For an actual corruption/opening error, Microsoft documents File > Open > Browse > Open and Repair, using the arrow beside Open. Do not discard the original after copying text into a new file.
4. Install an appropriate update. On Windows, use File > Account > Update Options > Update Now when available, or your organization’s managed update process. Save and close documents before restarting. The Office update guidance explains these controls. A reinstall is not the first diagnostic step.
5. Use Office Safe Mode for a Word startup test. Close Word after saving and reviewing recovery files. Press Windows+R, enter winword /safe, and select OK. Compare whether Word can start and open a permitted test document. Microsoft documents Safe Mode restrictions: features and customizations are restricted and recovered documents do not open automatically. Do not use Copilot’s availability in this mode as a pass/fail test of its license or service. Exit and restart Word normally afterward.

If Word is stable only in Safe Mode, a component omitted or changed in that mode warrants investigation. It does not conclusively identify one add-in. In normal Word, File > Options > Add-ins lets you inspect installed components; for COM add-ins, select COM Add-ins under Manage and choose Go. With IT or vendor guidance, record the original state and test one identified, nonessential add-in at a time, restoring it if the test does not help. Do not disable security, document-protection, or organization-managed components to make Copilot work.

Targeted Repair Instead of a Complete Copilot Plugin Reset

Microsoft’s general Word startup guide includes targeted add-in, template, and configuration tests. It is not a Copilot-specific reset procedure. If support identifies a startup template, preserve its contents and original location before a reversible test. Do not move every template or delete the entire Word registry branch; those changes can remove useful customization without identifying the fault.

Do not manually delete OfficeFileCache or empty temporary folders as a routine crash cure. Microsoft specifically warns that manual or programmatic Office document-cache deletion can cause crashes or unrecoverable data loss. Pending uploads and recovery files require attention before any support-directed cleanup.

For persistent Word application faults, save or recover your work and arrange an Office repair with IT. Microsoft’s repair guidance for Windows 11 uses Installed apps, the installed Microsoft 365 or Office product’s menu, and Modify. Click-to-Run installations offer Quick Repair and Online Repair; available choices depend on the installation. Repair affects the Office suite, even if only Word is failing. Plan the interruption and follow the diagnosed repair path, without a promise of a permanent fix.

If Copilot Still Has Issues After the Main Checks

If Word now stays open but Copilot remains unavailable, investigate that separate symptom. Check the expected account and current license, and use the app’s current Copilot entry point. Organizational support can check service health; on Windows, Get Help offers Copilot license and connectivity troubleshooters for their respective symptoms.

Send support the original crash pattern, test results in normal and Safe Mode, Word build, affected document type, and the single component or repair tested. Include a sanitized reproduction rather than the private original. That evidence helps identify the next action while retaining documents, recovery copies, templates, and organizational protection.