A Microsoft application for managing email, calendars, contacts, and tasks across devices and platforms.
Error 440 in this context is an Automation error raised by Outlook when accessing an object or property during startup. It is typically caused by a failure in an add-in, profile-specific data, or a disabled component for that specific account.
Because Outlook works in Safe Mode and with a new profile, but fails only with the existing account in normal mode, the problem is isolated to data or components tied to that original profile/account.
Based on the available information, the supported actions are:
- Treat this as an Automation error (440)
- Error 440 occurs when a method or property on an Automation object fails and the error is reported by the application that created the object.
- Use error handling to identify the failing object if running VBA or custom code: enable
On Error Resume Nextbefore the suspected call, then inspect theErrobject immediately after to see the source and description. - If any custom VBA, COM automation, or macros are associated with this Outlook profile, disable or remove them for that account and test again.
- Check for disabled or blocked add-ins at the admin level
- Error 440 can also occur if an Office add-in required by that account has been disabled by a system administrator.
- Confirm with the administrator (or local policy) that no required Outlook add-ins for that mailbox are disabled.
- Use the working profile as a workaround
- Since a new Outlook profile works, continue using that new profile for the affected mailbox as a practical workaround while investigating any custom automation, macros, or add-ins tied to the old profile.
If the environment uses Exchange Online or Outlook.com and the issue persists only for that mailbox, and no custom automation is present, open a support case through the Microsoft 365 Admin portal so support can review service-side issues for that specific mailbox.
References: