Home / Error Lookup / WORD-COMMAND-SEND-PROBLEM

WORD-COMMAND-SEND-PROBLEM

Word There Was a Problem Sending the Command to the Program Applies to: Windows 7, Windows 10, Windows 11

What it means

Windows tried to open a Word file through another program (like double-clicking an email attachment) and Word didn't respond in time — often a leftover invisible Word process.

Quick fix steps

  1. Open Task Manager and end any WINWORD.EXE process already running, then try again.
  2. In Word: File > Options > Advanced > General > untick "Ignore other applications that use Dynamic Data Exchange (DDE)."
  3. Save the attachment to your desktop first and open it directly, rather than opening it straight from the other program.
For the full step-by-step walkthrough, see Word Won't Open At All.

Frequently Asked Questions

Is this related to printing or another program specifically?
It can involve Word trying to communicate with another program or a printer driver that isn't responding correctly — similar in nature to the equivalent Excel error.
Will this happen again after I restart Word?
Not necessarily — if the cause was a temporary communication hiccup with another program, a fresh restart of Word often resolves it without recurrence.

Other error codes

WORD-UNREADABLE-CONTENT — Word Found Unreadable Content

Word detected some form of corruption in the document when opening it.

WORD-CONTENTS-PROBLEM — Word Found a Problem With the Contents

Word's XML parser hit something it couldn't read inside the document's internal structure — usually corruption from an interrupted save or a bad conversion between formats.

WORD-NOT-RESPONDING — Microsoft Word Has Stopped Working / Not Responding

Word crashed or froze completely, usually tied to a specific add-in, a corrupted template, or a very large/complex document — though it can also just be a long operation (a big mail merge, a macro, repagination on a huge document) still genuinely running.

WORD-LOCKED-FOR-EDITING — User Does Not Have Access Privileges / File Locked

Word believes someone else already has the file open, or your account doesn't have write permission on it.