Fix Word 'Problem Sending Command' Error from SharePoint

You're in a SharePoint document library, click a Word file, and instead of opening, Word fires back a tiny dialog: "There was a problem sending the command to the program." Then nothing. Or the file opens blank. This usually happens when you double-click a .docx in a SharePoint Online or on-premises library, but it can also pop when you try to open a file from a OneDrive synced folder. It's infuriating, especially when you're in a rush.

The root cause is almost always a mismatch between how Windows handles the file association and how Office expects to receive the command. When you click a file in SharePoint, the browser or explorer sends a command to Word via DDE (Dynamic Data Exchange). If Word's registry keys are broken—often after an Office update or a failed install—the command gets lost. I've also seen this happen when stale temp files clog up the Office cache, confusing Word into thinking it's already busy.

Here's the fix. Do these in order—they're tested on Windows 10 and 11 with Microsoft 365 and Office 2016/2019.

Step 1: Set Word as the default app for .docx files

This sounds obvious, but Windows sometimes resets the default to another program (like WordPad or a PDF reader) after an update. Here's the quick way:

1. Right-click a .docx file anywhere, choose Open with → Choose another app.
2. Select Microsoft Word. Check the box that says Always use this app to open .docx files.
3. Click OK.

If Word isn't listed, click More apps and scroll down. If you still don't see it, you might have a broken Office install—jump to Step 4.

Step 2: Disable DDE (Dynamic Data Exchange) for Word

DDE is a legacy protocol that Office uses to talk to the OS. It's often the culprit. Disabling it forces Word to open files directly, bypassing the broken handshake. Here's how:

1. Open Word (any blank document).
2. Go to File → Options → Advanced.
3. Scroll down to the General section.
4. Uncheck the box that says Ignore other applications that use Dynamic Data Exchange (DDE).
5. Click OK and restart Word.

Wait—that checkbox is confusing. The label says "Ignore", but when it's checked, Word ignores DDE requests, which is what we want. So leave it checked. If it's already checked, uncheck it, click OK, then re-check it and OK again. That refreshes the registry setting.

Step 3: Clear the Office cache

Stale temp files from previous failed opens can cause Word to hang. This is one of those fixes that's easy to skip but often the real solution.

1. Close all Office apps.
2. Press Win + R, type %temp%, and press Enter.
3. Select everything in that folder (Ctrl+A) and delete it. Ignore any files that are in use—skip them.
4. Also clear the Office cache by going to %localappdata%\Microsoft\Office\16.0\OfficeFileCache (for Office 2016+). Delete the contents, but keep the folder.

If you're not sure which version you have, check %localappdata%\Microsoft\Office\ and look for a folder like 16.0 (that's Office 2016/2019/365). For Office 2013 it's 15.0.

Step 4: Repair Office

If the above didn't fix it, the installation itself might be corrupted. Run a repair—it's painless and often fixes registry issues.

1. Open Control Panel → Programs and Features.
2. Find Microsoft 365 (or Microsoft Office) in the list.
3. Right-click and choose Change.
4. Select Quick Repair first. If that doesn't work, go back and do an Online Repair (takes longer but is more thorough).

Online Repair will download and reinstall Office files, so make sure you have a stable internet connection.

Step 5: Adjust Internet Explorer settings (for SharePoint Online)

This sounds weird, but Word uses IE's engine to talk to SharePoint in some setups. If you're still stuck, try this:

1. Open Internet Explorer (even if you never use it—it's still on Windows).
2. Go to Settings (the gear icon) → Internet Options.
3. On the Advanced tab, scroll to Security and check Enable Integrated Windows Authentication.
4. Click OK and restart your browser.

If it still fails

Here are three more checks before you throw your laptop out the window:

• Check if the file is checked out. In SharePoint, if someone else has the file checked out, Word might throw this error. Look for a lock icon next to the file name in the library.
• Use the "Open in App" option. In SharePoint Online, click the ellipsis (...) next to the file, choose Open, then Open in Word. This sometimes bypasses the broken command path.
• Try a different browser. I've seen this error happen in Edge but not Chrome, and vice versa. If you're using Edge, try Chrome or Firefox for a quick test.

Also, if you're on a corporate machine, your IT team might have a group policy that blocks DDE or restricts file associations. That's beyond your control, but worth mentioning to them.

I know this error is annoying, but 90% of the time Step 2 (the DDE trick) or Step 3 (clearing the cache) solves it. Start there and you'll likely be back to editing in two minutes.