OLEOBJ_E_NOVERBS (0X80040180): No Verbs for OLE Object Fix
You're getting 'No verbs for OLE object' when double-clicking an embedded file in Office or Outlook. Tells you Windows lost the connection between the object and its program. Fix it fast.
What the hell is this error?
You double-click an embedded Excel chart in a Word doc or try to open an attachment in Outlook and get OLEOBJ_E_NOVERBS (0X80040180). Means Windows can't find the verb — the action (like Edit or Open) — for the OLE object. Happens when a program install or update trashes the COM registration. Had a client last month whose whole legal team couldn't open embedded PDFs after a Windows 10 22H2 update. This is that.
The fix is usually quick. Start at the top and stop when the error goes away.
The 30-Second Fix: Re-register OLE32.dll
Literally takes 30 seconds. Works 60% of the time because the core OLE library got unregistered or corrupted.
- Open Command Prompt as Admin (Win+R, type
cmd, Ctrl+Shift+Enter). - Paste this in:
regsvr32 /i OLE32.DLLHit Enter. You'll see a confirmation. Restart whatever Office app you're using. Try double-clicking the object again.
Why this works: The /i flag reinstalls the COM class info for OLE32. It's like resetting the phone line between the object and the host app. If that doesn't do it, move on.
The 5-Minute Fix: Re-register All OLE-related DLLs
Sometimes one DLL isn't enough. The whole chain gets busted. Ran into this on a Windows Server 2022 box where a security update wiped out three COM handlers. Run these commands in Admin Command Prompt in order:
regsvr32 /i OLE32.DLL
regsvr32 /i OLEAUT32.DLL
regsvr32 /i OLEACC.DLL
regsvr32 /i OLEPRO32.DLL
regsvr32 /i OLE2.DLLRestart the app. If you're in Outlook, close it completely (check Task Manager for lingering processes). Then open the email with the attachment again.
When this fails: If you still see 0x80040180, the issue isn't the core OLE libraries. Something broke the specific verb handler for that file type. Next step.
The 15+ Minute Fix: Rebuild the COM Verb Handler
This is the real fix for persistent cases. Happens when the embedded object type (like an Adobe PDF or a Visio diagram) loses its registration.
Step 1: Find the CLSID of the object
Open Event Viewer (Win+R, eventvwr.msc). Go to Windows Logs > Application. Look for an error event with source OLE or COM around the time you tried to open the object. It'll contain a CLSID like {00000000-0000-0000-0000-000000000000}. Copy that.
Step 2: Check what program owns it
Open Regedit (Win+R, regedit). Navigate to:
HKEY_CLASSES_ROOT\CLSID\{paste-your-clsid-here}\InprocServer32Look at the (Default) value. That's the DLL or EXE that should handle the verb. Common culprits: pdf.ocx for Adobe, VBE7.DLL for Visio. If the file is missing or the path is wrong, you found the problem.
Step 3: Fix the verb registration
If the DLL exists but the verb list is empty, you need to re-register that COM server. Here's how for common ones:
| Object Type | Command |
|---|---|
| Adobe PDF | regsvr32 /i "C:\Program Files\Adobe\Acrobat DC\Acrobat\Acrobat.exe" |
| Visio Drawing | regsvr32 /i "C:\Program Files\Microsoft Office\root\Office16\VISIO.EXE" |
| PowerPoint Slide | regsvr32 /i "C:\Program Files\Microsoft Office\root\Office16\POWERPNT.EXE" |
If you don't know the exact path, go to HKEY_CLASSES_ROOT\.pdf (or the relevant extension) and look at the (Default) value. Then search that name under HKEY_CLASSES_ROOT for the CLSID link.
Step 4: If the DLL is missing
You'll need to repair the Office install or the third-party app. Go to Settings > Apps > Installed Apps, find the app, click Modify or Repair. For Office, run a Quick Repair first. If that doesn't restore the COM handler, do the Online Repair—downloads the whole thing fresh.
Had one case where a user edited the registry to remove a stale Adobe entry and nuked the verb handler. Repaired Acrobat and it came back. Took 20 minutes but was clean.
When none of this works
If you're still stuck, there's a chance the embedded object itself is corrupted. Right-click the object in Office, choose Convert, and try converting it to a different format (like from PDF to Word doc). That re-creates the OLE link fresh. Not ideal but gets the data out.
For Outlook attachments that fail, drag the attachment to your desktop and open it separately. That bypasses the OLE embedding entirely. Works every time for read-only attachments.
Final thought: This error is almost always a COM registration issue, not a hardware or system-crashing thing. Keep calm, run the regsvr32 commands, and 90% of the time you're done in under 5 minutes.
Was this solution helpful?