logo
search
Office for Mac Issues

How to Fix OneNote for Mac Crashing Immediately After Launch

WPS Content ManagerWPS Content Manager Sep 28, 2026 871 views

Question details

The user needs to fix an issue where Microsoft OneNote for Mac crashes right after opening, likely due to local notebook sync conflicts or corrupted files.

Fix OneNote for Mac Crashing Immediately After Launch
Product
Microsoft OneNote for Mac
Device & OS
Mac
Scenario
Attempting to open OneNote on a Mac after experiencing notebook conflicts, deletions, or synchronization problems.
Observed behavior
OneNote crashes immediately upon launch, preventing the user from accessing their notebooks locally on the Mac.
Before you start

Log in to OneNote Online through your web browser and verify that all your recent notes are fully synced and accessible before making any changes to local app data.

Solution 1Recommended

Reset OneNote Local Container Data

Clearing the local cache folder for OneNote forces the app to rebuild its database and resolves most startup crash loops without affecting cloud data.

macOS stores application cache and temporary files in a specific Container folder. When OneNote encounters severe sync conflicts, these local files can become corrupted, leading to instant crashes.

1
Quit Office Applications

Ensure OneNote and all other Microsoft Office applications are completely closed on your Mac.

2
Open the Go to Folder Menu

Open Finder, then press Command + Shift + G on your keyboard to launch the 'Go to the folder' search bar.

3
Locate the Containers Folder

Type ~/Library/Containers into the search box and press Return to access your Mac's application container directory.

4
Move the OneNote Folder

Find the folder named Microsoft OneNote (or com.microsoft.onenote.mac). Drag this folder out of the Containers directory and drop it onto your desktop.

5
Relaunch OneNote

Open OneNote again from your Applications folder. It will recreate a fresh container and prompt you to sign in and re-sync your notebooks.

Reset OneNote Local Container Data
Safe Deletion: Keep the old folder on your desktop until you have confirmed that OneNote launches correctly and all notebooks have successfully synced from the cloud. Once verified, you can safely delete the desktop folder.
Free Microsoft Office alternative

Experience a Stable and Lightweight Productivity Suite

If Microsoft Office applications continue to crash on your Mac, consider switching to WPS Office. It provides a highly stable, lightweight, and free alternative with excellent cross-platform compatibility.

  1. 1. Download the Installer: Visit the official WPS Office website and download the free macOS installation package.
  2. 2. Install on Your Mac: Open the downloaded .dmg file and drag the WPS Office icon into your Applications folder.
  3. 3. Start Creating: Launch WPS Office, sign in to activate cloud features, and enjoy a seamless, crash-free editing experience.
Highly compatible with Microsoft Office formats including Word, Excel, and PowerPointLightweight installation that runs smoothly on macOS without heavy resource usageFree to download with an intuitive, familiar interface that requires no learning curveBuilt-in cloud sync for securing your documents and notes across all your devices
microsoft office alternative - wps office

Frequently Asked Questions

Can I delete the Microsoft OneNote folder from my desktop after moving it?

Yes, but only after you have successfully relaunched OneNote and confirmed that all your notes have downloaded and synced correctly from OneNote Online. Once verified, you can safely drag the desktop folder to the Trash.

Will I lose my unsynced notes if OneNote keeps crashing?

If your recent notes were not synced to OneNote Online before the crashes began, moving the container folder might remove those local offline changes. This is why you must always check the web version first to see what was safely backed up.

Why does OneNote for Mac suddenly start crashing on startup?

Startup crashes in OneNote are commonly caused by corrupted local cache files, conflicting notebook sync states, or interfering background applications on macOS. Resetting the app container usually resolves these database corruption issues.