Microsoft Outlook Crashes with Teams Meeting Add-in Enabled

Microsoft confirmed on March 17, 2026, that Classic Outlook crashes on startup when the Teams Meeting Add-in is enabled. The company tracked the issue as Microsoft 365 incident EX1254044 under Exchange Online service degradation. The root cause is a compatibility conflict between Teams Meeting Add-in build 1.26.02603 and older Classic Outlook builds.

The crashes began around March 12, 2026, according to Microsoft's support documentation. Users running older builds of Classic Outlook with the newest Teams Meeting Add-in experienced immediate crashes followed by Safe Mode prompts. The faulting module in Event Viewer logs pointed to MSVCP140.dll, a Visual C++ runtime DLL bundled with older Office installations.

Affected Outlook versions include Outlook 2019, Outlook 2021, and Outlook for Microsoft 365 on Current Channel with builds equal to or lower than Version 2402 (Build 17328.20142). The issue affects both 32-bit and 64-bit installations on Windows 10 and Windows 11. New Outlook for Windows, Outlook on the web, and mobile Outlook clients are not affected.

Microsoft developed a fix on the Teams side, included in Microsoft Teams version 26058.712.4527.9297, which began deployment on March 30, 2026. Users can also resolve the issue by updating Classic Outlook to the latest build. Since Outlook may not open normally, Microsoft recommends opening Word first and running the Office update from File > Account > Update Options > Update Now.

For users who need to stay on an older Office build, Microsoft provides a workaround: open Outlook in Safe Mode by holding Ctrl during launch, then navigate to File > Options > Add-ins > Go. In the COM Add-ins dialog, uncheck Microsoft Teams Meeting Add-in for Microsoft Office and restart Outlook. This restores Outlook functionality but removes the ability to create Teams meetings from the calendar.

Enterprise administrators can disable the add-in organization-wide using Group Policy or registry modification. The relevant registry key is HKEY_CURRENT_USER\Software\Microsoft\Office\Outlook\Addins\TeamsAddin.Connect, with the LoadBehavior value set to 0. An Online Repair of Office also resolves the issue by reinstalling the latest Office binaries.

The crash stems from a compatibility mismatch between the Teams Meeting Add-in and the Visual C++ runtime libraries shipped with older Office builds. Teams Meeting Add-in build 1.26.02603, bundled with Teams version 26043.2016.4478.2773, calls functions in MSVCP140.dll that are not present in the older version (14.32.31332.0) included with pre-update Office installations. This triggers an access violation (exception code 0xc0000005) during add-in initialization, crashing the entire Outlook process.

The issue highlights a recurring friction point in Microsoft's ecosystem: Teams and Office ship on independent update cadences. When Teams updates its add-in to depend on newer runtime libraries but Office has not been updated to include those libraries, the mismatch breaks the integration. Microsoft's fix addressed the problem from both sides, updating the Teams add-in for backward compatibility and shipping updated Office builds with the newer runtime.

The new Outlook for Windows was not affected because it does not use COM add-ins. Microsoft has been encouraging enterprises to migrate to the new Outlook client, but many organizations remain on Classic Outlook due to feature gaps and compatibility requirements with existing workflows.

The bug hit enterprise environments hardest. Organizations using Microsoft 365 Business Premium, E3, and E5 licenses include both Classic Outlook and Teams Meeting Add-in by default. For users who schedule Teams meetings through Outlook's calendar, the crash made their primary email client completely unusable.

IT administrators in affected organizations reported widespread helpdesk tickets starting March 12. The workaround of disabling the add-in restored Outlook but broke the Teams meeting scheduling workflow, forcing users to create meetings through the Teams app or Outlook on the web instead. Organizations with strict change management policies that delayed Office updates were disproportionately affected, since the fix required either a Teams or Office update.

The incident adds to a pattern of Classic Outlook stability issues in early 2026. Microsoft also fixed a Gmail and Yahoo sync bug (0x800CCC0F and 0x80070057 errors) in late March and addressed an encrypted email opening issue caused by December 2025 updates. These recurring issues underscore the maintenance cost of running Classic Outlook in enterprise environments.