MK_E_NOPREFIX (0X800401EE) - No common prefix fix

When this error hits you

You're dragging a file from SharePoint or Windows Explorer into Outlook, or maybe you're trying to link data from Excel into a Word document. Suddenly, a pop-up says MK_E_NOPREFIX (0X800401EE). You click OK, nothing works. The file doesn't land where you want. You probably restart the app—doesn't fix it. I had a client last month whose entire sales team couldn't drag PDFs from their SharePoint library into Outlook emails. Cost them an hour of productivity each.

What's actually happening

Windows uses COM (Component Object Model) to let programs talk to each other. When you drag a file, the source app creates a moniker—think of it like a temporary address label. The moniker has a prefix that tells the target app where the data comes from and how to handle it. MK_E_NOPREFIX means the target app (Outlook, Word, whatever) doesn't recognize the prefix. It's like handing someone a package with a shipping label in a language they don't read. The error code 0X800401EE is COM's way of saying, 'I can't understand this address.'

The real fix: Registry tweak

Skip reinstalling Office or running sfc /scannow—that's time wasted. The issue is usually a corrupted or missing registry key that defines how COM monikers work for your Office version. I've seen this mostly on Windows 10 22H2 and Office 365, but it happens on Office 2019 and 2021 too.

1. Close all Office apps. Outlook, Word, Excel—everything. Even the little icon in the system tray.
2. Open Registry Editor. Press Windows + R, type regedit, hit Enter. Click Yes if UAC asks.
3. Back up your registry first. File > Export. Save a .reg file somewhere you'll remember. If something goes sideways, you can double-click that file to restore.
4. Navigate to:

   HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Ole

5. Look for a DWORD called EnableDCOM. If it's not there, create it. Right-click in the right pane, New > DWORD (32-bit) Value. Name it EnableDCOM.
6. Set EnableDCOM to Y. Double-click it, change the value to Y (yes, that's the letter Y, not a number). Click OK.
7. Now navigate to:

   HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Ole\AppEndPoint

   If this key doesn't exist, you probably need to create it. Right-click on Ole, New > Key, name it AppEndPoint.

8. Inside AppEndPoint, create a new DWORD called DefaultLaunchPermission. Set it to 1 (not really a permission value, but it triggers COM to reinitialize its launch permissions).
9. Restart the machine. Yes, full restart. Just ending Explorer or restarting Office won't reload the COM settings.

If that still doesn't work

Try this alternative path I've used twice in the last year:

1. Open Command Prompt as Administrator.
2. Run: reg add "HKLM\SOFTWARE\Microsoft\Ole" /v DefaultAccessPermission /t REG_SZ /d "" /f
3. Reboot again.

This clears any corrupted access permission string that might be blocking the moniker prefix. I've seen this fix work when EnableDCOM tweak alone didn't.

What to check if it still fails

• Antivirus interference. Some security suites block COM calls between Office apps. Temporarily disable your AV (not Windows Defender, the third-party one) and retest the drag-and-drop.
• Corrupt Office installation. Run a Quick Repair: Control Panel > Programs and Features > right-click Microsoft 365 (or Office) > Change > Quick Repair. If that fails, go for Online Repair—it's slower but deeper.
• User profile corruption. Rare, but I've seen it. Create a new local admin user, log into that account, test the drag-drop. If it works, migrate your data to the new profile.
• Third-party shell extensions. Tools like Dropbox, OneDrive, or Google Drive can hijack drag-drop events and mess up monikers. Disable them one by one using ShellExView (free tool) to isolate the culprit.

Most of the time, that EnableDCOM and AppEndPoint registry fix does the job. I've deployed it on maybe 30 machines over the years—only two needed the command-line permission reset afterward. Don't overthink it. Try the registry first, reboot, test. If you're still stuck, hit the profile or AV angle. This error is a pain, but it's solvable in under 10 minutes once you know where to poke.