You're trying to open a Word doc and instead of seeing your text, you get that infuriating pop-up. Don't worry, I've fixed this for dozens of users and the solution is usually simpler than you think.
The fastest fix: close stuck processes and disable add-ins
Most of the time, this error appears because Word's process is still running in the background, or a COM add-in is messing things up. Here's what to do, step by step.
Step 1: Kill any stuck Word processes
- Press Ctrl + Shift + Esc to open Task Manager.
- Look for any process named Microsoft Word or WINWORD.EXE under the Processes tab.
- Select each one and click End Task. If you see more than one, kill them all.
- Now try opening your document again. If it works, you're done. If not, continue to the next step.
After killing the processes, you should see a fresh start. If the error pops up again, it's likely an add-in.
Step 2: Start Word in safe mode to confirm add-in issues
Hold down the Ctrl key and double-click the Word icon on your desktop or start menu. Keep holding Ctrl until Word opens. If Word asks about safe mode, click Yes.
If the document opens fine in safe mode, then an add-in is the culprit. This is the most common cause, especially if you've installed PDF converters or document management software.
Step 3: Disable COM add-ins
Now let's get rid of the troublemaker:
- Close Word if it's open.
- Open Word in normal mode. If the error appears, click OK to dismiss it, then go to File > Options.
- Click Add-ins on the left sidebar.
- At the bottom, next to Manage, select COM Add-ins from the dropdown and click Go....
- Uncheck every add-in in the list. Don't worry, you can re-enable them later. Click OK.
- Close Word and open your document again.
If the error disappears, you found the problem. Now re-enable add-ins one by one to find which one breaks Word. It's tedious but worth it.
Why this works
The error comes from a broken COM add-in registration. When Word starts, it tries to load every registered add-in. If one of them fails, it doesn't just skip it—it throws that "sending the command" error and aborts the launch. Killing the process clears the lock, and disabling add-ins removes the trigger.
This happens a lot after you install or uninstall other Office-related software, like Adobe Acrobat, or a printer driver that includes a Word toolbar. Even a failed Windows update can corrupt the registration.
Less common variations of the issue
Sometimes the add-in fix doesn't cut it. Here are two other scenarios I've seen.
Variation 1: The document is stuck in a network location
If the error only happens when opening files from a network drive or SharePoint, it's likely a file lock. Copy the file to your local desktop and try opening it. If that works, ask your IT team to check the permissions or the server's file locking settings.
Variation 2: Word's settings are corrupted
Rarely, the entire Word data key gets corrupted. In that case, you need to reset Word's registry settings, but I always try the less invasive option first: run a repair on Office.
- Go to Control Panel > Programs and Features (or Settings > Apps on Windows 10/11).
- Find Microsoft Office in the list, click it, and choose Change.
- Select Quick Repair first. It takes a few minutes and doesn't touch your files.
- If that doesn't help, select Online Repair—it's more thorough but needs a stable internet connection.
After the repair, reboot your computer. The error should be gone.
How to prevent this from happening again
The best prevention is to keep your Office installation clean. Be careful about installing too many free add-ins or utilities that integrate with Word. Stick to reputable ones from Microsoft or major vendors.
Also, always close Word properly. Don't just click the X in the corner; use File > Exit. If you force-quit or your system crashes, Word's process can linger and cause exactly this error next time.
Another tip: when you uninstall an add-in, use the official uninstaller, not just delete files. Leftover DLLs and registry entries can break Word's startup.
If you've tried all this and the error still shows up, you might have a deeper problem with Windows itself. Run sfc /scannow in an elevated Command Prompt to check for system file corruption.
That's the complete breakdown. You should have your documents opening again in under ten minutes. If not, check if the issue happens with all documents or just one—that changes the diagnosis completely.