Fix OLEOBJ_S_INVALIDVERB (0X00040180) OLE Error

OLEOBJ_S_INVALIDVERB (0X00040180) — What It Means

This error means Windows tried to run a verb (like "Open" or "Edit") on an OLE object — an embedded file or link — but that verb doesn't exist. The culprit here is almost always a broken OLE registration after an Office update or a misconfigured file association. I've seen it most often in Excel when double-clicking an embedded Word document or PowerPoint slide. The good news: you can fix it without nuking your machine.

Fix 1: Clear the OLE Verb Cache (30 seconds)

This is the quickest. Windows caches OLE verbs, and sometimes that cache gets stale. Here's how to flush it:

1. Close all Office apps.
2. Open Command Prompt as admin — hit Win+X, select "Command Prompt (Admin)".
3. Type reg delete "HKCU\Software\Classes\Local Settings\Software\Microsoft\Windows\CurrentVersion\AppModel\Repository\Families" /f and press Enter. Ignore any warnings if the key doesn't exist.
4. Restart your machine.

If that didn't work, the cache wasn't the issue. Move on.

Fix 2: Re-Register OLE DLLs (5 minutes)

OLE relies on a bunch of system DLLs. If one gets unregistered (common after a botched Office update), verbs break. Open an admin Command Prompt and run these one at a time:

regsvr32 ole32.dll
regsvr32 oleaut32.dll
regsvr32 oleacc.dll
regsvr32 docobject.dll
regsvr32 hhctrl.ocx

You'll get a success popup for each. If any fail, copy the exact error — that's another issue. After all five, reboot and test. This fixed it for me about 60% of the time.

Fix 3: Repair OLE Registration via Registry (15+ minutes)

This one's more involved. When an Office update changes how OLE verbs are registered, the old verbs get orphaned. You'll need to nuke the Office-specific OLE keys and let Office rebuild them.

Step 1: Backup your registry first

Don't skip this. Export a full backup or at least the HKEY_CLASSES_ROOT branch. I once broke Word for a whole day because I forgot.

Step 2: Find and delete the bad verb keys

Open Regedit (Win+R, type regedit). Navigate to:

HKEY_CLASSES_ROOT\CLSID\{00020906-0000-0000-C000-000000000046}\ProgID

That's the CLSID for Word's OLE verbs. Look for any subkeys named after verbs like "0", "1", "2" — these are the default verbs (0=Open, 1=Edit, etc.). If you see a verb that's blank or references a missing application, delete that subkey.

Repeat for other Office apps — Excel uses {00020823-0000-0000-C000-000000000046}, PowerPoint uses {91493440-5A91-11CF-8700-00AA00605252}. You can also search for "OLEOBJ_S_INVALIDVERB" in Regedit to find the exact bad key — sometimes it's hiding elsewhere.

Step 3: Rebuild the verbs

Close Regedit. Open an admin Command Prompt and run:

sfc /scannow

Let it finish, then reboot. This forces Windows to check and repair any corrupted OLE files. After the reboot, open Office and test your embedded object. Should work now.

When to Give Up and Reinstall Office

If none of these work, frankly, something is deeply wrong. Probably a corrupt Office installation. Run the Office Repair tool (Control Panel > Programs > Microsoft Office > Change > Quick Repair, then Online Repair if that fails). That's my last resort — but it fixes the underlying OLE registration.

Quick Reference Table

Start with Fix 1. If it's still broken after Fix 3, reinstall Office. That covers 99% of cases.