Fix EVENT_E_INTERNALEXCEPTION (0X80040205) in 3 Steps

What Triggers This Error

You’ll see EVENT_E_INTERNALEXCEPTION (0X80040205) when a COM component raises an unexpected exception. I’ve run into this most often in two places: Outlook add-ins that interact with the Windows event system, and custom VBScript or PowerShell scripts that try to subscribe to COM events. The error means the COM server threw an exception it didn’t handle—so the client gets this generic 0X80040205 instead of something useful. It’s infuriating because the error message tells you nothing about which exception.

Let’s fix it. Start with the fastest check—it takes 30 seconds.

30-Second Fix: Re-register the COM Component

Half the time, the component’s registration got corrupted by a recent update or install. Windows 10 22H2 and Windows 11 23H2 are especially prone to this after cumulative updates.

1. Open Command Prompt as Administrator. Hit Win + X, then select “Terminal (Admin)” or “Command Prompt (Admin)”.
2. Run:

   regsvr32.exe /u msxml3.dll

   This unregisters MSXML3, a common culprit for Outlook event errors.
3. Then run:

   regsvr32.exe msxml3.dll

   to re-register it.
4. Close the command prompt and test your app or script.

Still broken? Move to the moderate fix.

5-Minute Fix: Repair the Windows Event System

This error often means the Event System itself is misconfigured. I’ve seen this on Windows Server 2019 and 2022 after a security patch messed with DCOM settings. Here’s what to do:

1. Open Services: press Win + R, type services.msc, hit Enter.
2. Find “COM+ Event System”. Double-click it.
3. Set Startup type to “Automatic”. If it’s not running, click Start.
4. Next, find “System Event Notification Service” (SENS). Set it to Automatic and start it too.
5. Restart both services. Then restart your app.

Still no luck? Check DCOM permissions. This is the deeper fix.

15+ Minute Fix: Reset DCOM Permissions via Registry

This is the nuclear option, but it works. When third-party software (like an outdated Outlook add-in or a custom VB6 app) installs, it can override DCOM launch permissions. The result? Your app can’t fire events.

Back up your registry first. I can’t stress this enough—one wrong key and you’ll break other COM components.

1. Open Regedit as Administrator.
2. Navigate to:

   HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Ole

3. Look at the values DefaultAccessPermission and DefaultLaunchPermission. If they’re set to something weird (like a single local user instead of SYSTEM or Administrators groups), delete them. They’ll regenerate with defaults on reboot.
4. More targeted: search the registry for the CLSID of the component throwing the error. If you don’t know the CLSID, run your failing script and check the Application Event Log for a COM warning with an AppID.
5. Once you have the AppID, navigate to:

   HKEY_CLASSES_ROOT\AppID\{YourAppID}

   and check the AccessPermission value. If it’s missing or set to a user that doesn’t exist, delete the AccessPermission key (not the whole AppID!).
6. Reboot the machine. Test again.

If you’re dealing with a custom script, also try running it as Administrator. Some COM objects require elevated permissions to subscribe to events—especially on Windows 11 where security tightened up.

When to Give Up and Reinstall

If none of this works, the component itself is likely broken. Uninstall the application that owns the COM object, reboot, then reinstall the latest version. For Outlook add-ins, run the Office repair from “Apps & features” (right-click Office, select Modify, then Quick Repair). That’s saved my bacon more than once.

You got this. And if you’re still stuck, drop a comment with the exact app and Windows version—I’ve probably debugged it before.