Fix it now
Two different published meanings sit on 0x80040111: the COM table calls it CLASS_E_CLASSNOTAVAILABLE, and the Exchange protocol documentation calls the same value LogonFailed. 0x80040154 is unambiguous – REGDB_E_CLASSNOTREG, class not registered. An Office repair is the supported fix for both.
Outlook.exe /safe
- Close Outlook and end any Outlook process still listed on the Details tab of Task Manager.
- Start Outlook without add-ins with the command above. Microsoft documents this as the way to start Outlook in safe mode.
- If safe mode fails too, repair Office from the installed-apps list in Windows Settings: choose your Microsoft 365 or Office entry, then Modify, then Quick Repair.
- If Quick Repair does not clear it, run the same wizard and choose Online Repair. That reinstalls the product and re-registers its COM classes; you will need to be online and to sign in again afterwards.
- If it is a third-party program failing rather than Outlook, compare bitness. A 32-bit process cannot load a 64-bit MAPI provider inside itself, and no amount of re-registering changes that.
Do not run regsvr32 against Office libraries on a Click-to-Run installation. The components are serviced as a package, and hand-registering pieces of one leaves the installation inconsistent.
If Outlook starts and the failing application can send again, stop here. The next section explains what is registered where, and how to tell machine-wide damage from a per-user problem.
Why it happens
These codes come from the component layer beneath Outlook rather than from Outlook itself. When a program asks Windows for a messaging object, it asks by class identifier. Windows looks that identifier up, finds the library that implements it, loads the library and hands back the object. 0x80040154 is that lookup failing outright: REGDB_E_CLASSNOTREG, class not registered. The identifier has no registration, or its registration names a file that is no longer on disk.
0x80040111 is the interesting one because it carries two published readings at the same numeric value. In the COM error table it is CLASS_E_CLASSNOTAVAILABLE, described as the class factory being unable to supply the requested class – the registration exists but the object cannot be produced. In Microsoft’s Exchange protocol documentation the same value is LogonFailed, a client that was unable to log on to the server. Which one you have depends on what raised it, and the practical consequence is the same: repair rather than edit.
0x80040155 sits one level below 0x80040154. REGDB_E_IIDNOTREG, interface not registered: the class is there, but the specific interface being asked for is not registered against it. That is the signature of a partly applied update, where some components were replaced and some were not.
0x80004005 is E_FAIL, unspecified error, and it says nothing at all on its own. When it appears alongside the others, read it as the caller having no better status to report, and go looking in the logs rather than in the code. 0x80040605 is NotInitialized in the protocol documentation – the subsystem is not ready – which is what you see when a component loaded but was never brought up.
An Office update was interrupted or only half applied
You have this one if The error appeared on the first launch after an update, and Outlook fails identically in safe mode.
- Open any Office application and let the update finish cleanly from File, Account, Update Options, Update Now.
- Run a Quick Repair from the installed-apps list in Windows Settings.
- If that does not clear it, run the same wizard and choose Online Repair.
- Restart before testing, so any pending file replacements complete.
Online Repair removes and reinstalls the Click-to-Run package. Allow time for the download and expect to sign in again afterwards.
Another program took over the mail client registration
You have this one if The trouble started after installing or removing a second mail client, a CRM connector, or a scan-to-email or fax utility.
- Confirm Outlook still holds the mail associations in Windows Settings, under default apps.
- Run an Office Online Repair. It rewrites the registration from the installer’s own record.
- Reinstall the other product afterwards if it is still needed, and retest both.
Repair is safer than typing a library path into the registry by hand, because the installer knows what the value should be and you are guessing.
Bitness mismatch between Outlook and the calling program
You have this one if Outlook opens normally, but a line-of-business application, scanner utility or PDF tool reports the class is not registered when it tries to send mail.
- Read the installed Office bitness in any Office application under File, Account, About.
- Check the failing application’s bitness on the Details tab of Task Manager, which marks 32-bit processes.
- Install the matching build of the application where one exists, or move Office to the matching bitness, which needs an uninstall and reinstall.
- Where the application supports it, have it send by SMTP submission or the Graph API instead of in-process MAPI.
This is a design limit rather than a fault. A 32-bit process cannot load a 64-bit library, so re-registering will not change the outcome.
The damage is per-user rather than machine-wide
You have this one if A different Windows user signs in on the same machine and Outlook starts without any error.
- Create a fresh Outlook profile from the Mail item in Control Panel, using Show Profiles and then Add.
- Set the new profile as the one always used and start Outlook.
- If the new profile works, move any local data files across and retire the old one.
- If the new profile fails too, create a new Windows user account and test there to separate profile damage from machine damage.
Full reference
Which failure belongs to which layer
| Code | Constant | Published text |
|---|---|---|
0x80040111 |
CLASS_E_CLASSNOTAVAILABLE | ClassFactory cannot supply requested class |
0x80040111 |
MAPI_E_LOGON_FAILED | A client was unable to log on to the server |
0x80040154 |
REGDB_E_CLASSNOTREG | Class not registered |
0x80040155 |
REGDB_E_IIDNOTREG | Interface not registered |
0x80004005 |
E_FAIL | Unspecified error |
0x80040605 |
MAPI_E_NOT_INITIALIZED | The subsystem is not ready |
Telling machine-wide damage from per-user damage
| What you see | Where the fault is |
|---|---|
| Outlook starts, a third-party application fails | Bitness mismatch, or that application’s own registration |
| Outlook fails for one Windows user only | Per-user registration or that user’s Outlook profile |
| Outlook fails for every user on the machine | Machine-wide registration, or a damaged installation |
| It started on the first launch after an update | An interrupted update; repair is the fix |
| It started after another mail client was installed | The mail client registration was reassigned |
Why repair rather than registry surgery
There is a well-travelled internet answer to these codes that involves editing the registry key describing the machine’s mail client and pointing it at a library path by hand. Resist it. Microsoft does not publish the value names or the expected data for that key, which means anyone giving you a path is reciting it from a machine that happened to work. Get it wrong and you break every mail-capable application on the machine rather than one of them.
Quick Repair reapplies the installed package’s own registration data without downloading anything, so it is quick and safe to try. Online Repair removes and reinstalls the package. Between them they cover every registration fault that a repair can fix, and if neither works the problem is not registration.
Two repairs later and still failing
- Check the Application log in Event Viewer for the failing module name. A repeated failure naming a third-party DLL points at that product, not at Office.
- Check whether a security product is blocking the load. Attack surface reduction rules and application control policies both stop libraries loading and both report as a class that cannot be produced.
- Test with a new Windows user account. If a brand new profile works, the machine is fine and the old profile is not.
- For a program that only ever worked on one machine, check whether it shipped its own copy of a messaging library and expects to find it where a newer Office no longer puts it.
- If the failure is in a scheduled or service context rather than an interactive one, remember that Outlook is not supported as an unattended or server-side component, and that is a design boundary rather than a bug to work around.
Every code this article covers
| Code | What it points at | Source |
|---|---|---|
0x80040111 |
CLASS_E_CLASSNOTAVAILABLE, the class factory cannot supply the requested class; the same value is published as MAPI_E_LOGON_FAILED, a client unable to log on to the server | Microsoft Learn |
0x80040154 |
REGDB_E_CLASSNOTREG: class not registered | Microsoft Learn |
0x80004005 |
E_FAIL: unspecified error, carrying no detail of its own | Microsoft Learn |
0x80040155 |
REGDB_E_IIDNOTREG: interface not registered | Microsoft Learn |
0x80040605 |
MAPI_E_NOT_INITIALIZED: the subsystem is not ready | Microsoft Learn |
Confirm the fix worked
- Outlook starts normally and reaches the mailbox with no dialog.
- The application that was failing can send a test message, not just Outlook itself.
- No new Outlook or Office errors appear in the Application log during the test.
- File, Account still shows the expected product and the correct signed-in account.
- A second Windows user on the same machine also starts Outlook cleanly.
Questions people ask about this
Do I need a new Office licence to fix this?
No. Registration and entitlement are separate. Your subscription, key and sign-in state are untouched, and an Online Repair reinstalls the same product against the same licence at no cost.
Is it safe to run regsvr32 against the Outlook libraries?
Not on a Click-to-Run installation. The components are serviced as a package and hand-registering pieces of it usually fails outright or leaves the installation inconsistent. Repair is the supported route.
Will Online Repair delete my mail?
It reinstalls the application, not your data. Outlook profiles and personal data files are left in place, and a cached file is rebuilt from the server if it is removed. Take a copy of any .pst holding local-only mail first, as a habit.
My application is 32-bit and Office is 64-bit. Can I keep both?
Yes, but they cannot talk over in-process MAPI. Move one of them to the matching bitness, or have the application send by SMTP or Graph, neither of which cares about bitness.
Why does the same code mean two different things?
Because the numeric value is reused across two published error tables. The COM table defines it as a class-factory failure; the Exchange protocol documentation defines it as a logon failure. Both are real, and which one you are looking at depends on which component raised it.
