Fix it now
Explorer started Excel but the request to open your file was never answered, so you get an empty window or nothing at all. The file is fine: the handoff between the shell and the running application is what failed. Reset the association, clear the add-ins, then repair.
- Prove it first. Start Excel from the Start menu and open the same file with Ctrl+O. If it opens that way, the workbook is not damaged and you are looking at the launch path.
- Reset the association the way Microsoft documents it: copy the file to the desktop, right-click it, choose Properties, note the file type on the General tab, select Change, then More apps, pick Excel and tick Always use this app.
- Turn the add-ins off: File > Options > Add-ins, set Manage to COM Add-ins, click Go, clear one at a time and restart Excel between each.
- Clear the elevation mismatch. Right-click the Excel shortcut, open Properties > Compatibility and untick Run this program as an administrator, then do the same under Change settings for all users.
- Look in Excel’s Options, in the Advanced section under General, for the setting that tells Excel to ignore requests from other applications that use Dynamic Data Exchange. If it is ticked, untick it, close every Excel window and try the file again.
- If it survives all of that, run an Online Repair: Settings > Apps > Apps & features, select your Office entry, choose Modify, then Online Repair.
Close every Excel window and confirm no EXCEL.EXE remains in Task Manager before you retest. A leftover process answers the next launch and will make a fixed machine look broken.
If double-clicking opens the file, you are done. If it does not, the next section explains what the shell is asking for and what the four COM codes underneath are actually saying.
Why it happens
Double-clicking a document does two things, not one. The shell starts the application, and then it has to get the file name into the copy of the application that is now running – which may be one you already had open. When the second half of that fails, the first half has already succeeded, so you are left looking at an application that started and did nothing. Nothing about the workbook is involved, which is why opening the same file from inside the application with Ctrl+O works perfectly.
Microsoft publishes no page defining this message, so treat the wording as a symptom rather than a code. What is published are the four COM results that appear underneath it. 0x800401E3 is MK_E_UNAVAILABLE, “Operation unavailable”. 0x800401FD is CO_E_OBJNOTCONNECTED, “Object is not connected to server”, which is what you get when the instance you were talking to has gone. 0x80080005 is CO_E_SERVER_EXEC_FAILURE, “Server execution failed”: the executable was found and would not start.
0x800401F3 is CO_E_CLASSSTRING, “Invalid class string” – the text form of a class identifier could not be parsed into one. That is not the same as a class nobody registered, which is 0x80040154, REGDB_E_CLASSNOTREG, and sends you to a different place in the registry. Reading one as the other is how people end up re-registering components that were never missing.
The file association was rewritten by something else
You have this one if Only certain extensions fail, or the file opens in the wrong application, and a PDF tool, viewer or converter was installed recently.
- Copy the file to the desktop, open its Properties, and use Change > More apps to point the type back at Excel.
- Tick Always use this app so the choice survives the next restart.
- If the association will not stick, run an Online Repair, which rewrites the shell registration Office owns.
Excel is elevated and Explorer is not
You have this one if It started after someone set a shortcut to run as administrator, or it affects one profile on a shared machine.
- Clear Run this program as an administrator on the Excel shortcut, under Properties > Compatibility.
- Use Change settings for all users on the same tab and clear it there too, because the per-machine flag is separate.
- Sign out and back in before retesting, and check no elevated EXCEL.EXE survived.
An elevated application and a standard-user shell run at different integrity levels and cannot exchange this kind of request.
An add-in is holding the application busy
You have this one if The file opens when the add-ins are off, and you may also see a message about waiting for another application to complete an OLE action.
- File > Options > Add-ins, set Manage to COM Add-ins, click Go and untick everything.
- Restart and test the double-click, then re-enable one add-in at a time.
- Repeat with Excel Add-ins, which are a separate list in the same box.
The application is set to ignore requests from other programs
You have this one if Double-clicking gives a blank grey workspace every time, on every workbook, and Ctrl+O from inside Excel always works.
- Open Excel’s Options and look in the Advanced section, under General, for the setting about ignoring other applications that use Dynamic Data Exchange.
- Clear it, click OK, and close every Excel window.
- If it re-ticks itself between sessions, an add-in or a policy is setting it, so go back to the add-in list.
Microsoft publishes nothing about this setting that could be checked here. Treat it as a switch worth looking at rather than as a documented fix.
Full reference
Reading the code you were given
| Code | Published meaning | Where that points |
|---|---|---|
| 0x800401E3 | MK_E_UNAVAILABLE, Operation unavailable | The request could not be completed against the target; commonly nothing to bind to |
| 0x800401FD | CO_E_OBJNOTCONNECTED, Object is not connected to server | The instance you had is gone, usually because it exited between the two halves of the launch |
| 0x80080005 | CO_E_SERVER_EXEC_FAILURE, Server execution failed | The executable exists and would not start – look at elevation, add-ins and a repair |
| 0x800401F3 | CO_E_CLASSSTRING, Invalid class string | The name handed to COM was not parseable as a class identifier |
| 0x80040154 | REGDB_E_CLASSNOTREG, Class not registered | A different fault: the identifier is fine and nothing is registered under it |
The same fault in Word and the other applications
Word, PowerPoint and Access all use the same shell handoff and produce the same message. The association reset, the elevation check and the add-in bisection are identical; only the location of the ignore-other-applications setting differs, because each application keeps its own. If several applications fail at once, stop looking at any one of them and run the repair.
Where the association lives
| Key | What it holds |
|---|---|
| HKEY_CLASSES_ROOT\.xlsx | The class name that this extension maps to |
| HKEY_CLASSES_ROOT\Excel.Sheet.12\shell\Open\command | The command line the shell runs for a modern workbook |
| HKEY_CURRENT_USER\…\AppCompatFlags\Layers | Per-user compatibility flags, including run-as-administrator |
Read these keys to understand what has happened; do not edit them to fix it. An Online Repair rewrites the whole set correctly, and a hand-edited file class can leave documents unopenable for every account on the machine. If you do open Registry Editor, export the key before you touch anything.
When the message follows one user rather than one machine
- Test with a second Windows account on the same machine. If it works there, the fault is in the profile, not the installation.
- Compare the COM add-in list between the two accounts; add-ins register per user as well as per machine.
- Check the compatibility flags under the AppCompatFlags key above, which are per user.
- Check whether the working account has the ignore-other-applications setting in a different state, since it is stored per user too.
What not to do
- Do not reinstall Office before running an Online Repair. Repair does the useful part in a fraction of the time.
- Do not set Office to always run as administrator. It creates this fault rather than curing it, and it breaks drive mappings made by the ordinary session.
- Do not delete file classes by hand to force Windows to rebuild them. It does not reliably rebuild them.
- Do not chase the workbook. If Ctrl+O opens it, the file has already been eliminated.
Every code this article covers
| Code | What it points at | Source |
|---|---|---|
There was a problem sending the command to the program |
The shell started the application but the request to open the document was not answered; the wording itself is not published by Microsoft | not published by the vendor |
0x800401E3 |
MK_E_UNAVAILABLE: operation unavailable | Microsoft Learn |
0x800401FD |
CO_E_OBJNOTCONNECTED: the object is not connected to the server that provided it | Microsoft Learn |
0x80080005 |
CO_E_SERVER_EXEC_FAILURE: server execution failed | Microsoft Learn |
0x800401F3 |
CO_E_CLASSSTRING: invalid class string, so the text form of a class identifier could not be resolved into one. Class not registered is a different code, 0x80040154 | Microsoft Learn |
Confirm the fix worked
- Double-click a workbook in Explorer and confirm the content appears rather than an empty window.
- With that one open, double-click a second workbook and confirm it opens in the same instance.
- Restart the machine and repeat both tests, to prove the settings survived a reboot.
- Re-enable the add-ins you intend to keep, one at a time, retesting the double-click after each.
- Test the same thing in Word if the report mentioned more than one application.
Questions people ask about this
Does fixing this cost anything?
No. Every step is a setting, an association or a repair of software you already have. There is no licence involved and nothing to buy. If an Online Repair does not fix it, the next step is a reinstall of the same product, not a different one.
Why does the file open fine from inside the application?
Because opening through Ctrl+O never uses the shell handoff at all – the application reads the file itself. That difference is the cleanest proof you can get that the workbook is intact and the launch path is what is broken.
Should I leave the ignore-other-applications setting switched off permanently?
For almost everyone, yes. It exists for legacy automation that deliberately drives Excel and wants competing requests ignored. If you do not have such a system, the cleared state is the one you want. Microsoft publishes nothing about the setting that we could verify, so make the change deliberately and note that you made it.
The same thing happens with Word documents. Is it the same fault?
Usually. Word uses the same handoff, and the association, elevation and add-in causes are shared. Check the equivalent setting in Word’s own Options and the same compatibility flags. If three applications fail together, go straight to the repair.
Someone told me to re-register the application with a command-line switch. Should I?
Not as a first move, and not on the strength of a forum post. An Online Repair does the same registration work in a supported way and fixes the file classes at the same time. Reach for anything more manual only after a repair has failed.
