That OLE_E_CANTCONVERT (0x80040011) error is one of those classic Windows headaches that pops up right when you're trying to paste an object into Excel or Word. The message usually reads something like "Not able to convert object" and it stops you cold. If you've ever copied a chart from an old app and tried embedding it into a report, you know the drill.
I've seen this dozens of times. The good news: it's almost always one of three things. Let's take them in order of how often they actually cause the problem.
The source program is missing or not registered
This is the #1 culprit. OLE (Object Linking and Embedding) requires the original application that created the object to be installed and registered on your machine. If you're pasting a chart from, say, an older version of Excel that isn't on this computer anymore, Windows has no idea how to render it.
You'll see this a lot on fresh installs or when someone sends you a workbook with embedded objects from software you don't have. For example: you open a dashboard in Excel, and it contains an embedded WordArt object from Office 2003. If the old Office components aren't available, the conversion fails immediately.
The fix: Install the application that created the object. If it's an Office object, make sure the full Office suite is installed and updated. If it's a third-party app (Visio, Project, etc.), install that. Once the source app is present, restart Excel or Word and try again.
If you can't install the original app, try converting the object to a static image instead. In many cases you can right-click the object and choose "Convert" — if that fails too, you're stuck deleting it and recreating it manually.
Broken COM registration or OLE subsystem corruption
Even if the source app is installed, Windows might have lost the registration that tells it which program handles a particular object type. This happens after Windows updates, botched uninstalls, or registry cleaners that got a little too enthusiastic.
The classic symptom: you try to paste an OLE object and get OLE_E_CANTCONVERT even though the source app is clearly installed. That's your clue.
The fix: Re-register the OLE libraries. Open Command Prompt as administrator and run these one at a time:
regsvr32 ole32.dll
regsvr32 oleaut32.dll
regsvr32 actxprxy.dll
regsvr32 comcat.dll
You should get a "DllRegisterServer in ... succeeded" message for each. If one fails, note which one — that DLL might be corrupted and needs to be restored from a working machine or via sfc /scannow.
After that, run the built-in Office repair. For Office 2016/2019/365: Settings > Apps > find your Office install > Modify > Quick Repair. If that doesn't work, run Online Repair. It takes longer but fixes deeper issues.
I also recommend running sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth if you suspect system file corruption. It's a bit of a shotgun approach, but it catches things regsvr32 misses.
Corrupted clipboard or temporary files
The third most common cause is a corrupted clipboard or temp files that are holding onto a bad OLE object. This often happens after you've been copying and pasting a lot, or if an application crashed while an object was on the clipboard.
A real-world trigger: you copy a chart from Excel, then Excel crashes. You reopen it and try to paste that chart into Word — boom, OLE_E_CANTCONVERT. The clipboard still thinks it has a valid OLE object, but the underlying data is toast.
The fix: Clear the clipboard completely. You can do this by opening a blank Notepad and copying a single space, or by running:
cmd /c "echo off | clip"
Then clear your temp folders. Press Win+R, type %temp%, and delete everything you can. Some files will be in use — skip those. Also clear C:\Windows\Temp if you have permission.
Restart your computer. Yes, really. A reboot forces Windows to rebuild the OLE cache and releases any file locks on temp files.
If the problem persists, try creating a new user profile. A corrupted profile can cause bizarre OLE errors that nothing else fixes. It's a pain to set up, but it's a reliable last resort.
Quick reference: OLE_E_CANTCONVERT fixes
| Cause | Fix | Difficulty |
|---|---|---|
| Source program missing | Install the original app that created the object; update Office | Easy |
| Broken COM registration | Run regsvr32 on OLE DLLs; repair Office; run sfc /scannow |
Intermediate |
| Corrupted clipboard/temp files | Clear clipboard, delete temp files, reboot, create new profile | Easy |
One more thing: if you're working with files from an old version of Office (like .xls or .doc), try saving them as .xlsx or .docx first. The newer formats handle OLE objects better and sometimes sidestep the conversion error entirely.
I know this error is infuriating — it always seems to hit when you're on a deadline. Start with the source program check, then move to registration fixes, and clear that clipboard before you pull your hair out. Nine times out of ten, one of these three gets you back to work.