Fix Word 'Problem Sending Command' Error (Fast)

Word throws this when its own file associations or COM hooks break. Start with disabling add-ins, then rebuild the registry key. Most people fix it in under a minute.

Why This Happens

What's actually happening here is that Word's shell integration—the part that lets Windows talk to the program when you double-click a .docx file or hit Print—has gotten out of sync. This usually comes from a broken Office update, a leftover add-in, or a corrupted registry entry that defines how Word handles file associations. The error pops up randomly when opening a document, printing, or even just clicking the Word icon.

I've seen this on Windows 10 and 11, with Office 2016, 2019, and Microsoft 365. It's not a file corruption issue—your document is fine. The problem is in how Word receives the command from the OS.

Below is a troubleshooting flow. Start with the first fix—it takes thirty seconds and resolves about half of all cases. If it doesn't work, move to the next. You can stop as soon as your error disappears.

Fix 1: The 30-Second Fix—Disable Add-ins

The most common trigger is a COM add-in that hooks into Word's startup routine. Something like an Adobe PDF maker, a citation manager, or a third-party toolbar. These add-ins can intercept the command and drop it, causing the exact error message you're seeing.

Here's how to test it without completely uninstalling anything:

Press Win + R, type winword /safe, and hit Enter. This starts Word in Safe Mode, which loads no add-ins.
If Word opens fine in Safe Mode, the add-in is your culprit.
Now go to File → Options → Add-ins.
At the bottom, next to Manage, select COM Add-ins from the dropdown and click Go.
Uncheck everything in the list, then click OK and restart Word normally.

If that clears the error, re-enable add-ins one by one to find the troublemaker. The reason step 4 works is that you're disabling the same components that Safe Mode bypasses, but now you're doing it permanently—not just for that one session.

If the error still appears in Safe Mode, move on to Fix 2.

Fix 2: The 5-Minute Fix—Reset Word's Registry Key

When add-ins aren't the issue, the next suspect is the registry key that holds Word's data. This key stores your user preferences, toolbar settings, and file association states. If it's corrupted, Word can't properly receive commands from the shell.

Here's the fix—it's safe and only affects Word's settings, not your documents:

Close all Office apps, including Outlook if you have it.
Press Win + R, type regedit, and hit Enter.
Navigate to this key (copy and paste it into the address bar):
HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Word
Right-click the Word folder and rename it to WordOld.
Close Registry Editor and open Word again.

Word will recreate a fresh key with default settings. You'll lose your custom dictionary and some personalized options, but your documents are untouched. The reason this works is that the corrupted data is now bypassed—Word builds a new, clean state.

If you're on Office 2013, the path is 15.0 instead of 16.0. For Office 2010, it's 14.0.

Still seeing the error? Go to the advanced fix.

Fix 3: The 15-Minute Fix—Repair Office and File Associations

If the registry reset didn't help, the problem is likely deeper—either Office itself is corrupted, or the file association for .docx files is misconfigured at the OS level.

Step 1: Run Office Repair

This is the official fix and it rarely fails. It's just slow.

Go to Settings → Apps → Installed apps (or Apps & features on older Windows).
Find Microsoft 365 or Microsoft Office in the list.
Click the three-dot menu (or select it) and choose Modify.
Select Quick Repair first—it takes about five minutes and doesn't require a download.
If the error persists, run Online Repair, which does a full reinstall and takes longer but fixes almost everything.

What's actually happening here is that the repair process re-registers all the COM components and restores the shell hooks that Word needs to receive commands. That directly addresses the root cause.

Step 2: Reset File Associations

Sometimes the repair misses the file association. Worth checking because it's quick:

Right-click any .docx file and choose Open with.
Pick Word from the list, and check the box for Always use this app.
Click OK.

That's it. The reason this matters is that if Windows is trying to hand the file to a shell extension that's registered under a stale path, you get that exact error. Reassigning the handler clears the stale data.

When to Try Something Else

If you've done all three and still get the error, consider a couple of edge cases:

**Printer driver corruption**—if the error only appears when printing, update or reinstall your printer driver. A bad driver can crash Word's Print dialog, which triggers the same message.
**Antivirus interference**—some security apps block Word from creating temporary files. Temporarily disable your AV and test. If it works, add an exception for Word.
**Corrupted user profile**—if nothing else works, create a new Windows user account and test Word there. If it works, your profile is toast.

Don't waste time reinstalling Windows or Office completely—that's overkill. Start with add-ins, then the registry, then repair. Nine times out of ten, you'll be done in the first two steps.