Outlook not opening after Windows 11 update
- Windows 11
- Windows 10
Quick answer
If Outlook is not opening or responding properly after a Windows 11 update, a disabled or misconfigured Teams Meeting add-in is often the root cause. You can resolve this issue by re-enabling the add-in in Outlook Options or adjusting its LoadBehavior setting in the Windows Registry. If you recently upgraded to the new Microsoft Teams, running the dedicated cleanup PowerShell script will restore add-in functionality.
When Outlook fails to launch or hangs during startup after installing a recent system update, underlying conflicts with COM add-ins—specifically the Microsoft Teams Meeting Add-in—are frequently responsible. Updates can alter application permissions, disable essential background components, or create file pathway mismatches during client upgrades. This issue primarily impacts desktop users running classic Outlook applications alongside Microsoft Teams on Windows 11 and Windows 10 devices.
Understanding what caused the startup failure helps you choose the right fix. In many cases, Outlook automatically disables add-ins that take too long to load during boot. In other instances, upgrading from classic Teams to the new Teams application removes required loader files without registering the new ones. The steps below walk you through resolving these component conflicts from the simplest settings checks to advanced system script repairs.
Method 1: Enable the Teams Meeting add-in in Outlook settings
Use this method if Outlook opens partially or stays open long enough for you to access the top toolbar. System updates occasionally classify active add-ins as unstable and move them to the disabled list upon restart.
- Launch Outlook and select File in the top-left corner of the window.
- In the left-hand menu, click Options to open the Outlook Options configuration window.
- In the Outlook Options dialog box, select the Add-ins tab from the left sidebar.
- Look at the main panel to review the lists. Check whether Microsoft Teams Meeting Add-in for Microsoft Office appears under the Active Application Add-ins section.
- If the add-in is listed under Disabled Application Add-ins, move to the bottom of the window where it says Manage.
- Select COM Add-ins from the drop-down menu and click Go.
- In the COM Add-ins popup box, locate Microsoft Teams Meeting Add-in for Microsoft Office and check the box next to it.
- Select OK on every open dialog box to apply your changes, then restart Outlook.
After restarting, the application will attempt to load the add-in normally on boot. If the add-in stays active, your startup issue is resolved.
Method 2: Check and update the add-in registry load behavior
Use this method if the add-in continuously unchecks itself or disappears from the active list whenever you close Outlook.
Warning: Modifying system registry keys incorrectly can cause serious operating system instability. Follow these instructions carefully, and consider backing up your registry before proceeding.
- Press the Windows Key, type
RegEdit.exein the search bar, and press Enter to launch the Registry Editor. - In the left navigation pane, browse to the following registry path:
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\Outlook\Addins\TeamsAddin.FastConnect. - On the right panel, double-click the LoadBehavior DWORD entry.
- Examine the Value data field. If it displays any number other than 3, change the value to
3and click OK. - Next, check if Group Policy or Cloud Policy settings are overriding your configuration. Navigate to
HKEY_CURRENT_USER\SOFTWARE\Policies\Microsoft\Office\16.0\Outlook\Security(orHKEY_CURRENT_USER\SOFTWARE\Policies\Microsoft\Cloud\Office\16.0\Outlook\Securityif your system uses Cloud Policy). - Look for the
promptoomaddressinformationaccessentry. If its value is set to0, Outlook is set to automatically deny programmatic access requests. - Close the Registry Editor window and restart your computer.
Setting LoadBehavior to 3 forces the Outlook desktop client to load the Teams add-in automatically upon every application launch.
Method 3: Re-register the Teams Addin Loader DLL
Illustration: the About page under Settings > System
Use this method if the add-in registry entries are correct, but Outlook still fails to start due to an unregistered or corrupt loader library file.
Warning: Re-registering dynamic link libraries requires elevated administrative command line access. Ensure commands are typed exactly as shown.
- Close the Outlook desktop client completely and exit the Microsoft Teams application.
- Open File Explorer and enter
%LocalAppData%\Microsoft\TeamsMeetingAddinin the address bar. - Open the subfolder named after the add-in version number. If multiple version subfolders exist, open the subfolder with the highest build number (for example,
1.0.23334.11). - Highlight the address bar and copy the full path to this subfolder.
- Click the Start button, type
cmdin the search box, right-click Command Prompt, and choose Run as administrator. - For 64-bit Office installations, type
%SystemRoot%\System32\regsvr32.exe /n /i:user <path copied in step 4>\x64\Microsoft.Teams.AddinLoader.dlland press Enter. - For 32-bit Office installations, type
%SystemRoot%\SysWOW64\regsvr32.exe /n /i:user <path copied in step 4>\x86\Microsoft.Teams.AddinLoader.dlland press Enter. - Restart the Teams desktop client, sign out of your user account, and sign back in.
- Launch Outlook again, ensuring that Outlook itself is not running in Administrator mode.
A dialog box from RegSvr32 will confirm that the loader DLL was successfully registered to your user profile, restoring startup communication between Teams and Outlook.
Method 4: Reinstall the Teams Meeting add-in via PowerShell
Illustration: the Installed apps page under Settings > Apps
Use this method if you or your organization recently uninstalled classic Teams and upgraded to the new Teams app, causing the meeting add-in to become corrupted or completely removed.
Warning: Running management scripts alters installed application packages. Download script files from official sources and execute them carefully in PowerShell.
- Close both Outlook and the Microsoft Teams application.
- Verify your current add-in installation status by selecting Start > Settings > Apps > Installed apps and searching for
Teams Meeting Add-in. - If no entry appears, or if the installed version of Microsoft Teams Meeting Add-in for Microsoft Office starts with
1.23, download the officialUninstallOldTMA.ps1script. - Click Start, search for
powershell, right-click Windows PowerShell, and select Run as administrator. - At the elevated prompt, run the
UninstallOldTMA.ps1script to remove the legacy add-in installation. - If the installed version does not start with
1.23, downloadUninstallTMA.ps1. Open a standard PowerShell window and executeUninstallTMA.ps1. - Open the new Teams desktop app and wait a few moments until
Teams Meeting Add-inautomatically registers and appears under Start > Settings > Apps > Installed apps. - Restart the Outlook application.
The script clears out leftover configuration files so the new Teams app can perform a clean installation of the add-in component.
If nothing worked
If Outlook still refuses to open or run properly after following the steps above, check these additional requirement criteria:
- Verify system prerequisites: Ensure you are running Outlook 2016 or a later version on your computer. Make sure all available software updates for the Outlook desktop client have been downloaded and applied.
- Confirm desktop installation: Verify that you have the full Teams desktop client installed. The meeting add-in cannot be installed or loaded if you only use the web-based Teams client.
- Check new Outlook compatibility: Note that the new Outlook for Windows app does not support the Teams COM add-in architecture. New Outlook utilizes native Teams meeting scheduling features instead.
- Fix delegate meeting issues: If Outlook opens but delegate meeting requests fail to include URL, Meeting ID, passcode, or dial-in details, the delegator's mailbox may be hidden from the Global Address List (GAL). Have an administrator run the Exchange Online PowerShell command
Set-Mailbox -Identity <delegator’s email address> -HiddenFromAddressListsEnabled $falseto unhide the mailbox, then restart Outlook.
Sources
Frequently asked questions
Does the new Outlook for Windows support the classic Teams COM add-in?
No, the new Outlook for Windows does not support the classic Teams COM add-in. Instead, the new Outlook contains native built-in meeting scheduling capabilities.
Why are Teams meeting join links missing when I schedule on behalf of someone else?
This problem occurs when the delegator's mailbox is hidden from the Global Address List (GAL). Unhiding the mailbox via Exchange Online PowerShell allows Outlook to correctly populate the meeting details.
Which versions of Outlook work with the Teams Meeting add-in?
The Teams Meeting COM add-in requires Outlook 2016 or a later desktop client, along with an installed installation of the Teams desktop client.
Checked against Microsoft's release notes on ; re-checked when a new build ships.
Writes Thea's error-code and app-breakage guides. Each fix is checked against Microsoft's documentation and community reports, and updated when a new Windows 11 build changes the steps.
More from Daniel Okafor