Fix OLEOBJ_S_CANNOT_DOVERB_NOW (0x00040181) fast

You're staring at this error, and it's annoying

It usually pops up when you try to open an embedded object—like a spreadsheet in a Word doc or a PDF in an email—and Windows says “verb number is valid but verb cannot be done now”. The object exists, the action is defined, but something's blocking it.

Skip the fluff—here's the real fix

This is almost always a DCOM permission problem. The COM object that owns the verb (like Excel or Adobe Reader) doesn't have the right launch or access permissions for the current user. I've seen this on Windows 10 Pro and Windows 11 after a security update or a user account change.

Step 1: Kill any stale COM processes

Open Task Manager, go to the Details tab, and look for dllhost.exe processes. End any that are using high memory or CPU. Also kill excel.exe or acrobat.exe if they're hanging. Restart the app that triggered the error. Try again. If it works, you're done—it was a stale COM instance. But most times this doesn't help.

Step 2: Fix DCOM permissions for the object's server

The real fix is in Component Services. Here's the exact path:

Start > Run > dcomcnfg
Component Services > Computers > My Computer > DCOM Config

Find the application that owns the object. If it's an Excel object, look for “Microsoft Excel Application” or “Microsoft Office Excel”. If it's a PDF, look for “Adobe Acrobat” or “Adobe Reader”. Right-click it, go to Properties.

Go to the Security tab. Under Launch and Activation Permissions, click “Customize”, then “Edit”.

Make sure the user account that's running the parent application (like Word or Outlook) has Local Launch and Local Activation checked. If you're running as a domain user, add “Everyone” or “Authenticated Users” temporarily to test. Apply, close, restart the parent app.

Step 3: If that didn't work—check the Identity tab

Still failing? Go back to that application's Properties in DCOM Config. Click the Identity tab. Change it from “Launching User” to “Interactive User”. This tells the COM object to run as the logged-in user, which usually has all the permissions it needs. Apply, restart.

Why this works

The error code 0x00040181 comes from OLE (Object Linking and Embedding). The verb number—like “Open” or “Edit”—is valid, but the COM server that handles it can't run because it doesn't have permission to launch or access the object. Changing the launch permissions or identity lets the COM server run under the right context. I had a client last month whose entire print queue died because of a similar COM permission issue—same root cause, different error.

Less common variations of the same issue

Sometimes the error fires inside a specific app, not the system. Here are two I've hit:

• Adobe Reader embedded in Outlook: The verb “Open” fails because Adobe's COM server is set to run as “Launching User” but the user doesn't have local launch permission. Fix is the same—change Identity to Interactive User.
• Excel object in a PowerPoint slide: You double-click the table and get the error. This is often caused by a corrupted Office installation or a permissions issue after an Office update. Run the Office repair (Quick Repair, then Online Repair if that fails) before touching DCOM.

How to prevent it from coming back

This tends to reappear after Windows updates or Office updates. To stop it:

1. Don't run as a local admin unless needed. Launch and Activation permissions are often stripped for non-admin accounts. Use Interactive User identity for the COM server.
2. Set a system restore point before any Windows update. If the error returns, roll back.
3. Use the same user account for both the parent app and the embedded object server. Switching accounts mid-session causes permission mismatches.
4. Keep Office and Adobe up to date—outdated versions have permission bugs that trigger this.

That's it. No registry edits, no rebuild of the COM cache. Fix the permissions, restart, and get back to work.