Fix New Outlook & Teams Not Opening After KB5121003

If Outlook and Teams fail to open on ARM-based Windows PCs after installing KB5121003, the fix is to uninstall that specific update, then reinstall it after applying a registry workaround that restores the blocked execution of ARM64 binaries. This article explains why the update breaks these apps, how to apply the fix safely, and how to prevent the problem from recurring.

Background: What Is KB5121003 and Why Does It Matter?

KB5121003 is a Windows update released for ARM64 devices (such as Surface Pro X and other Snapdragon-powered laptops) that was intended to improve the performance and reliability of the operating system on that architecture. The update itself is not a feature update; it is a cumulative servicing stack or compatibility update that modifies how Windows handles certain executable files. On some ARM PCs, the update introduced a conflict with the way Microsoft 365 apps (Outlook and Teams) are packaged and launched, causing them to fail immediately after the update is installed.

The issue is specific to ARM64 because Windows on ARM uses an emulation layer (x64 emulation on ARM) to run apps that are not natively compiled for the ARM architecture. KB5121003 changed a policy that governs which binaries are allowed to run in that emulated environment, and the change inadvertently blocked the main executables of Outlook and Teams. The result is that clicking the app icon does nothing, or the app shows a brief splash screen and then closes without an error message.

How the Update Breaks Outlook and Teams

Outlook and Teams are distributed as Click-to-Run applications, meaning they are installed and updated through a streaming mechanism that keeps the core files in a protected folder. On ARM PCs, these apps run through the Windows on ARM emulation layer because Microsoft has not yet released fully native ARM64 versions of all Microsoft 365 components. The KB5121003 update introduced a stricter check on the digital signature and architecture of executables that are allowed to run under emulation. The check incorrectly flags the Outlook.exe and Teams.exe files as incompatible, even though they were working before the update.

The failure is not a corruption of the app files themselves; it is a policy-level block. That is why simply reinstalling Outlook or Teams does not solve the problem. The block persists because the policy change remains in the registry after the update is installed. Understanding this distinction is important because many users waste time uninstalling and reinstalling the apps before discovering that the update is the culprit.

Step-by-Step Fix: Uninstall the Update and Apply the Registry Workaround

The most reliable fix is to remove KB5121003, then add a registry key that restores the previous behavior, and finally reinstall the update. Follow these steps in order:

Open Settings > Windows Update > Update history > Uninstall updates.
Locate KB5121003 in the list, select it, and click Uninstall. Restart your PC when prompted.
After reboot, verify that Outlook and Teams open normally. If they do, proceed to the registry step.
Press Win + R, type regedit, and press Enter. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags.
Right-click on the AppCompatFlags key, choose New > Key, and name it Layers (if it does not already exist).
Inside the Layers key, create a new String Value for each app that is broken. Use the full path to the executable, for example:

C:\Program Files\Microsoft Office\root\Office16\OUTLOOK.EXE
C:\Program Files\WindowsApps\Microsoft.Teams_...\Teams.exe (the exact path may vary; find it by right-clicking the Teams shortcut and selecting “Open file location”)

Set the value data of each string to ~ WIN7RTM (without quotes). This tells Windows to run the app with Windows 7 compatibility settings, which bypasses the emulation block.
Close the Registry Editor and restart your PC.
Reinstall KB5121003 by going to Settings > Windows Update > Check for updates. The update will download and install again.
After the update installs, restart once more and test Outlook and Teams. They should now open normally.

If you prefer not to reinstall the update, you can leave it uninstalled, but that may leave your system missing important security fixes. The registry workaround allows you to keep the update while restoring app functionality.

Alternative Fixes and When to Use Them

If the registry method seems too technical, or if it does not work for you, try these alternatives in order of simplicity:

Run the apps in compatibility mode directly from the app’s Properties dialog. Right-click the Outlook or Teams shortcut, select Properties > Compatibility tab, check “Run this program in compatibility mode for” and choose Windows 7. This achieves the same effect as the registry key but applies only to the shortcut, not the actual executable, so it may not work for all users.
Use the web versions of Outlook and Teams while the issue persists. This is a temporary workaround that lets you continue working, but it is not a permanent fix.
Repair the Office installation via Settings > Apps > Microsoft 365 > Modify > Quick Repair. This will reinstall the app files but will not remove the registry block, so it only works if the block was somehow removed separately.

If none of these work, consider waiting for Microsoft to release a subsequent update that addresses the regression. In the meantime, the uninstall-and-registry method is the most dependable.

Common Mistakes and Misconceptions

One common mistake is trying to fix the problem by uninstalling and reinstalling Outlook or Teams. As explained earlier, the issue is not with the app files but with the system policy. Reinstalling will not change the registry entry that blocks the executables.

Another misconception is that the update is harmful and should be permanently avoided. KB5121003 contains important security and stability fixes for ARM64 systems. The registry workaround allows you to keep the update and still use your apps, so you do not have to choose between security and functionality.

A third mistake is entering the registry path incorrectly. The Layers key must be created under AppCompatFlags, not under Windows or any other location. Also, the value name must be the full path to the executable, including the drive letter and file extension. If you get the path wrong, the compatibility flag will not apply.

Frequently Asked Questions

Will this fix work for other apps that break after KB5121003?

Yes, the same registry workaround can be applied to any executable that fails to run after the update. Simply add a string value with the full path to the executable and set it to ~ WIN7RTM. This is a general compatibility override that tells Windows to treat the app as if it were running on Windows 7, bypassing the emulation check.

Is it safe to edit the registry?

Editing the registry is safe if you follow the steps carefully and only modify the keys specified. Always back up the registry before making changes (right-click the key and select Export). If you make a mistake, you can restore the backup. Do not delete other keys or values, as that could cause system instability.

Why does the registry workaround use Windows 7 compatibility?

Windows 7 compatibility mode is a legacy compatibility layer that disables many of the newer security and emulation checks. By forcing the app to run in this mode, you bypass the specific check that KB5121003 introduced. It is a well-known workaround for similar issues on ARM devices.

What if I don’t see KB5121003 in the uninstall list?

If the update is not listed, it may have been automatically removed or replaced by a newer update. Check the Windows Update history to confirm it was installed. If it is not present, try the registry workaround directly, as the block may still be in place even if the update is no longer listed.

Will Microsoft fix this permanently?

Microsoft typically addresses such regressions in a subsequent cumulative update. Keep Windows Update enabled and install any new updates that appear. The registry workaround is a temporary solution until an official fix is released.

Can I use the 64-bit version of Outlook instead?

If you are using the 32-bit version of Microsoft 365, switching to the 64-bit version might avoid the issue because the 64-bit executables are handled differently by the emulation layer. However, this is not a guaranteed fix, and you should only switch if your other add-ins and plugins are compatible with 64-bit Office.

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →