Microsoft 365 keeps shutting down

If Microsoft 365 keeps closing on Windows, the cause is usually one app, one user profile, one device issue, or a recent update; the quickest clue is whether the crash repeats after sign-out, on another PC, or after rollback. Start with the affected app in Safe Mode, then check the build number before you repair anything. Ignoring the pattern can waste time on the wrong fix and leave files unsaved. This guide shows how to identify the failure source and choose the right repair path.

What the shutdown error means

In this article, “shutting down” means the app closes, freezes and exits, or does not open. Those are different failure modes, and they point to different fixes. One app failing is usually a local problem, while multiple apps failing on one machine points more strongly to the device or installation.

Check the affected app and the build number

Before changing anything, note whether the problem is in Word, Excel, Outlook, PowerPoint, or Teams, and record the Microsoft 365 build number from File > Account. If the issue started right after an update, keep the recent update history in view. A bad build can break one app while the others still open.

Why one-PC-only failures point to the device

If the same account works on another computer, the problem is usually local. Crashes on only one PC usually point to a local issue rather than a widespread outage, and the likely causes include one unstable app, one damaged profile, one bad add-in, or one machine-level problem. That split matters more than the headline symptom.

Likely causes, from most common to less common

Most shutdown problems come from add-ins, profiles, caches, or a recent update. Less often, the device itself is the source: graphics drivers, storage trouble, memory pressure, or security software can push an app over the edge. The right first test depends on whether the fault follows the app, the user, or the PC.

• Add-ins and extensions: Third-party CRM connectors, PDF tools, antivirus email scanners, and e-signature tools can interfere with Outlook and Excel.
• Corrupt profile or cache: Outlook profiles, Teams cache data, and sign-in tokens can break after a sync issue or profile change.
• Recent update or bad build: A Microsoft 365 build change can trigger post-update crashes on one app or one PC.
• Device issues: Outdated display drivers, storage health problems, memory pressure, printer drivers, and security software can close apps unexpectedly.

Say your Outlook window closes as soon as a shared mailbox loads, but Excel stays open. That pattern points away from a full Microsoft 365 outage and toward Outlook-specific data, such as an add-in, profile, cache, or printer driver conflict.

Microsoft 365 shutdown decision table

Why does Microsoft 365 keep shutting down?

The most common pattern is an app-specific fault, usually from add-ins, a damaged profile, or a cache problem. Start by testing the app in Safe Mode so you can bypass add-ins and extensions.

How to test with Safe Mode

1. Press Win + R.
2. Type Outlook /safe for Outlook, or winword /safe for Word.
3. Press Enter and open the same file or mailbox again.
4. If the app stays open, the next step is to remove add-ins, not reinstall the whole suite.

How to disable add-ins

1. Open the app, then go to File > Options > Add-Ins.
2. At the bottom, choose COM Add-ins, then select Go.
3. Clear the check boxes for third-party items such as CRM connectors, PDF tools, antivirus email scanners, and e-signature tools.
4. Close and reopen the app, then re-enable add-ins one at a time only if the app stays stable.

What to note before you repair

Record the exact app, the build number, whether Safe Mode helped, and whether the problem happens on one account or one PC. That short note can separate an app fault from a device fault in minutes. If the same crash appears in multiple Microsoft 365 apps on the same machine, move to repair and driver checks next.

Why does Outlook keep shutting down on my PC?

Outlook can be affected by issues such as profile corruption, cache problems, oversized OST files, search or indexing trouble, and printer driver conflicts. Add-ins are a common trigger, but Outlook can also crash from profile corruption, cache problems, oversized OST files, search or indexing trouble, and printer driver conflicts. Use the pattern to choose the next step, not the label on the app icon.

Test for add-in conflicts

1. Press Win + R, type Outlook /safe, and press Enter.
2. If Outlook opens, go to File > Options > Add-Ins.
3. Choose COM Add-ins, then Go.
4. Turn off every non-Microsoft add-in, then restart Outlook normally and test again.

Rebuild the Outlook profile

1. Open Control Panel > User Accounts > Mail.
2. Select Show Profiles.
3. Create a new profile and set it as the default.
4. Open Outlook with the new profile. If the old profile was damaged, this often stops the crash path.

Clear cache and check search or indexing

1. Close Outlook.
2. Restart Outlook and test search in the mailbox.
3. If search or folder loading still fails, run Outlook Diagnostics or the Classic Outlook Connectivity troubleshooter. On the first screen, select Outlook, and then select Next.
4. If the problem persists, create a new Outlook profile again rather than trying to stack more add-ins.

Check printer drivers

1. Open Settings > Bluetooth & devices > Printers & scanners or Control Panel > Devices and Printers.
2. Set a different default printer, then reopen Outlook.
3. If Outlook stops closing, update or roll back the printer driver in Device Manager.
4. Restart the Print Spooler if printing is also unstable.

Teams keeps shutting down

Teams often fails for a different reason than Outlook or Excel. Local cache corruption, sign-in token problems, and graphics acceleration issues can close the desktop app after launch, during a meeting, or when switching accounts.

Close Teams and clear local cache folders

1. Quit Teams completely from the system tray, then open Task Manager and end any remaining Teams process.
2. Open File Explorer and go to the Teams cache location under the user profile.
3. Remove the local cache folders: blob_storage, databases, GPUCache, IndexedDB, Local Storage, and tmp.
4. Restart Teams and sign in again.

Remove GPUCache, indexedDB, and local storage data

1. If Teams still closes, delete the remaining cache data in the same local profile path.
2. Open Teams again and let it rebuild the local files.
3. If the sign-in loop returns, remove stored credentials in Windows Credential Manager and sign in again.
4. If the issue returns on the same PC, move to graphics and driver checks.

Check sign-in tokens and restart

1. Sign out of Teams.
2. Close the app, then restart Windows.
3. Sign in again and test the same meeting or channel.
4. If the crash happens only after a token refresh, a full cache rebuild is the next practical step.

Microsoft 365 repair and graphics fixes

Repair is the right next step when Safe Mode and profile checks do not stop the crash. Quick Repair is generally the lighter repair option. Online Repair is the deeper repair option and is used when files or components stay broken. Office repair options are found in Installed apps or Programs and Features; the Control Panel path in Microsoft’s Outlook guidance is Uninstall a program.

Run Quick Repair first

1. Open Settings > Apps > Installed apps on Windows 11, or Control Panel > Programs and Features on Windows 10.
2. Select Microsoft 365, then choose Modify or Change.
3. Select Quick Repair and follow the prompts.
4. Reopen the affected app and test the same file or mailbox.

Use Online Repair when files stay broken

1. Return to the Microsoft 365 entry in Installed apps or Programs and Features.
2. Select Online Repair.
3. Let the installer finish, then restart the PC.
4. If the crash survives a full repair, rebuild the user profile or move to driver checks instead of repeating the same repair.

Disable hardware graphics acceleration

1. Open the affected app and look for a graphics or display setting that disables hardware acceleration, if the option is present.
2. For older devices or unstable display drivers, this can stop freezing, lag, or crashes.
3. If you change the registry, back it up first and edit only the Office graphics key that applies to the installed version.
4. Restart the app and test again.

Update display drivers and Windows

1. Open Device Manager and update the display adapter driver, or roll it back if the crash started after a driver change.
2. Check Windows Update and install pending updates.
3. If storage or memory pressure is suspected, run chkdsk and Windows Memory Diagnostic.
4. If security software seems involved, test a clean boot with msconfig and retry the app.

Suppose Excel starts closing only when a workbook with heavy formulas opens on a laptop with an older display driver. That points to the device path first, not the workbook itself. In that case, driver updates and hardware graphics acceleration changes make more sense than reinstalling Microsoft 365 immediately.

Still not working?

If the crash keeps coming back after Safe Mode, add-in removal, profile rebuild, cache cleanup, and repair, the next step is a more invasive device check or vendor support. Reconfirm the build number, test the app on another account, and compare behavior on another PC. If only one machine fails, the issue is still local.

1. Run sfc /scannow from an elevated Command Prompt.
2. Run DISM /Online /Cleanup-Image /RestoreHealth.
3. Check the disk with chkdsk and memory with Windows Memory Diagnostic.
4. If the issue affects only one app after all repairs, contact Microsoft support with the exact build number, affected app, and the steps already tried.

Prevention is limited, but one practical step helps: keep troublesome third-party add-ins disabled until you confirm they are stable after an Office update.

Frequently asked questions

What should I do first when Microsoft 365 keeps crashing?

Check whether the problem follows one app, one profile, or one PC, then launch the affected app in Safe Mode. Use Outlook /safe or winword /safe, and note the Microsoft 365 build number before repairing. That sequence separates add-in faults from device faults quickly.

Does Microsoft 365 keep shutting down because of add-ins?

Often, yes. Outlook and Excel are common trouble spots, and add-ins are one of the biggest offenders. Start at File > Options > Add-Ins, choose COM Add-ins, select Go, then turn off non-Microsoft items such as CRM connectors, PDF tools, antivirus email scanners, and e-signature tools.

How do I fix Microsoft 365 after an update?

Check the build number first, then run Quick Repair from Settings > Apps > Installed apps on Windows 11 or Control Panel > Programs and Features on Windows 10. If the crash started right after the update and stays after Quick Repair, use Online Repair and then restart the PC.

Why does Microsoft 365 only shut down on one computer?

That pattern usually points to a local issue, not a service outage. Compare the same account on another PC, then check the local profile, display driver, storage health, and memory pressure on the failing machine. If only one device fails, repair or profile rebuild is usually more useful than reinstalling everywhere.

Should I repair Microsoft 365 or reinstall it?

Start with repair. Quick Repair is the lighter pass, and Online Repair is the deeper option when files stay broken. Reinstalling should come later, after Safe Mode, add-in checks, profile rebuilds, and repair have failed. Use Installed apps or Programs and Features to reach the repair options.

Why did my Microsoft 365 stop working?

Most often, one app stopped because of an add-in, profile damage, cache corruption, a bad build, or a device problem such as graphics or printer drivers. Check which app fails, whether it happens on one PC only, and whether it began after an update. That pattern tells you which fix to try first.