You double-click an embedded object in Word, edit the cell, hit Ctrl+Z, and Word throws INPLACE_E_NOTUNDOABLE (0x800401A0): Undo is not available. Or Explorer gives you the same code when you try to rename a file back. The app isn't broken. What's actually happening is that the COM in-place editing session has already closed its undo record, and you're asking it to roll back something it doesn't remember.
Cause 1: The in-place editing session already committed (most common)
This is the number one reason you'll see 0x800401A0. When you activate an embedded OLE object in Word, Excel, or PowerPoint, the server app opens a special editing window inside the container. While that session is live, the server maintains an undo stack. The moment you click outside the object, press Esc, or switch apps, the server calls IOleInPlaceObject::UIDeactivate and flushes its undo stack. Any Ctrl+Z after that returns exactly this error.
The trigger is almost always muscle memory. You type into an embedded Excel chart, click back into the Word body, then reflexively hit Ctrl+Z. Word forwards the undo to the OLE object, which no longer has a session, and you get the error.
The fix is boring but real: undo inside the embedded object before you click away. If you've already clicked away, use Word's own undo (Ctrl+Z again) — the container keeps its own undo record for the OLE transaction, and that one still works. You can also try File > Info > Manage Document > Recover Unsaved Documents if Word's undo stack is also tapped out.
If Ctrl+Z inside the object never worked in the first place, the embedded server isn't exposing an undo interface. That's a different bug — usually a version mismatch between the Office install that created the object and the one opening it.
Cause 2: A stale COM registration for the OLE server
Second most common, and the one that trips up IT admins. If Office was upgraded in place (say, 2016 to 365, or you ran a repair from a different bitness), the registry keys under HKEY_CLASSES_ROOT\CLSID can point at the wrong binary. The container still activates the object, but the in-place undo handler is registered to a DLL that either doesn't exist or is the wrong version. Every undo attempt returns INPLACE_E_NOTUNDOABLE.
You can confirm this by checking the event log for AppModel-Runtime warnings right before the failure, or by running:
reg query "HKCR\CLSID\{00020819-0000-0000-C000-000000000046}\InprocServer32"That GUID is Excel's worksheet CLSID. If the path resolves to a file that doesn't exist, or points to a 32-bit DLL on a 64-bit Office install, you've found the culprit.
The real fix is to repair the Office installation, not just re-register. Run Control Panel > Programs > Microsoft Office > Change > Quick Repair. If that doesn't rebuild the CLSID entries, do an Online Repair. Skip the regsvr32 dance — it works for about ten minutes and then breaks again after the next Office update.
Cause 3: A third-party add-in hijacking the undo stack
Less common but vicious. Add-ins that hook IOleUndoManager to add their own undo entries (think document-management add-ins, PDF exporters, translation tools) sometimes register a manager that returns E_NOTIMPL for undo, which surfaces as 0x800401A0 to the user. I've seen this specifically with older versions of Nuance Power PDF and a few DocuSign Outlook add-ins from 2019–2021.
Test it by launching the host app in safe mode. For Word:
winword /safeFor Excel:
excel /safeIf Ctrl+Z works in safe mode, you've got a bad add-in. Disable them one at a time under File > Options > Add-ins > COM Add-ins > Go. The trick is to disable half, test, then halve again — doing them one at a time wastes an afternoon.
If the add-in is one you need, check the vendor's site for a build from the last 18 months. Undo handlers were a common break point when Office moved to the Click-to-Run update model, and a lot of small vendors never shipped a patch.
What won't fix it
Running sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth is the reflex answer for every Windows error code, and it does nothing here. Those tools check system files, not Office COM registrations or per-user add-in state. Skip them unless you've also got unrelated corruption symptoms.
Also skip the registry cleaners. Every one I've tested, including the paid ones, will happily delete the InprocServer32 keys you actually need and leave the broken ones alone.
Quick reference
| Symptom | Likely cause | Fix |
|---|---|---|
| Error appears right after you click outside the embedded object | Undo stack flushed when session deactivated | Use the container's Ctrl+Z, or edit before clicking away |
| Error on every undo, even inside the object | Broken CLSID registration for the OLE server | Quick Repair, then Online Repair of Office |
| Error only when a specific add-in is loaded | Third-party IOleUndoManager hook | winword /safe, then disable add-ins in halves |
| Error in Explorer, not Office | Shell extension from a sync client (OneDrive, Dropbox) | Disable the shell extension, restart explorer.exe |
One last thing: if you only see this in a specific document, not all of them, the file itself may have a corrupted OLE stream. Open it with Open and Repair (File > Open > browse > click the arrow next to Open > Open and Repair) before you touch any registry keys. Rebuilding a chopped document is a five-minute job; rebuilding your Office install is an hour you won't get back.