OneNote users have been grappling with error 0xE000005E—a sync failure formally labelled ReferencedRevisionNotFound—that leaves a notebook section stubbornly out of sync. The error can surface after a network hiccup, an offline edit, or a revision conflict, but it rarely signals data loss. A methodical rebuild of the affected section, rather than a panicked reset, is the most reliable way to restore harmony across devices.

What Error 0xE000005E Actually Means

OneNote syncs notebooks as collections of sections and pages, each tracked by a chain of revisions. Error 0xE000005E means the desktop app is trying to reconcile a change with a revision reference that no longer exists in the cloud. Think of it as a broken link in the sync chain. The problem is typically confined to a single section, which is why nuking an entire notebook or reinstalling Office is overkill.

Guiding Tech recently recapped the error and its remedies, noting that it often appears as a temporary glitch. But for users who see the same stubborn warning across multiple manual sync attempts, the underlying revision mismatch must be addressed. The good news? The local copy of the section usually holds all recent edits, even if they haven’t uploaded yet.

Why It Hits Your Notebook

OneNote’s cloud-first architecture is a marvel of real-time collaboration, but it comes with fragile dependencies. The app coordinates between a local cache, your Microsoft account, and a cloud repository—usually OneDrive or SharePoint. A brief service outage, a flaky connection while writing offline, or concurrent edits from multiple logged-in devices can all leave a section in limbo. Microsoft has baked many improvements into recent Office updates, so an outdated build can also be a contributing factor.

Account confusion is another frequent trigger. A user might open a notebook with the wrong profile—personal instead of work, or vice versa—and find that OneNote can’t locate the expected revisions. Checking which identity is active can solve the mystery before any heavy lifting begins.

What It Means for You

For the home user who relies on OneNote for household budgets or recipe collections, error 0xE000005E means you might glance at your phone and panic that a recent edit vanished. Take a breath: the content is almost certainly safe on the device where it was written. The danger comes only if you blindly delete the section or clear the app cache without first preserving unsynced pages.

For IT pros and shared-notebook owners, the stakes are higher. A single broken section can confuse an entire team if colleagues see stale information. Here, verifying that the notebook location and account permissions are correct should be step one. If the error only appears for one person, the fix is almost certainly a client-side section rebuild; if it’s widespread, the SharePoint site or OneDrive library may need admin attention.

How We Got Here

When Microsoft moved OneNote to the cloud and adopted the .one file format as a synchronized container, it enabled co-authoring and device-hopping that local-only apps could never match. The trade-off is a complex synchronization engine that must juggle version histories, merge conflicts, and attachment updates. Error codes like 0xE000005E are essentially the engine’s way of throwing up its hands when it can’t prove that the server’s revision list matches the client’s.

The error isn’t new. It has appeared in community threads for years, often after a major Office update or a OneDrive outage. Microsoft’s own support documentation rarely calls out ReferencedRevisionNotFound by name, but the company has addressed related sync robustness in subsequent updates. The practical takeaway for users: if you haven’t updated OneNote in a while, you’re running a build that may lack these fixes.

What to Do Now

The loudest advice from every expert source, including the Guiding Tech guide that resurfaced this topic, is to protect your unsynced notes before attempting any repair. Here’s a sequence of increasingly deliberate steps that balances safety and effectiveness.

1. Locate the Real Copy of Your Notes

Open the notebook in OneNote for the web. This browser version reads directly from the cloud, bypassing your local cache entirely. Compare what you see online with what the desktop app shows. If the web has everything current, your local sync state is stale and can be rebuilt. If the desktop holds newer pages, those are precious—copy them into a safe temporary section before doing anything else.

2. Force a Manual Sync

Press Shift+F9 to prod OneNote into syncing the current notebook. Give it time, especially if the notebook is large. This alone resolves a surprising number of transient errors. If the error vanishes, verify the sync by checking the notebook on another device. If it persists, open Notebook Sync Status (right-click the notebook name) and drill down until you spot the exact section that’s failing. Write down its name.

3. Rebuild the Section—Without Destroying Data

When the error won’t budge, the most trusted fix is to create a brand-new section in the same notebook and copy all pages from the broken section into it. Follow this routine to the letter:

  • Right-click in the section list and choose New Section. Name it something temporary like “Recovered.”
  • Open the problematic section and select every page. Right-click and choose Copy, then paste into the new section.
  • Wait a few moments and sync with Shift+F9. Open the notebook on the web or another device to confirm the new section appears with all content intact.
  • Only after full verification, delete the old broken section. Rename the recovered section to its original name if you like.

This works because the new section gets a clean revision history from the moment it’s created. OneNote uploads the copied pages as fresh content, side-stepping the broken reference.

4. Update Office and Windows

Open any Office app like Word, go to File > Account > Update Options > Update Now. This pulls the latest sync improvements from Microsoft. Also run Windows Update and reboot. While an update alone won’t fix an already-corrupted section, it can prevent the same mismatch from happening again in other notebooks.

5. Know When to Repair Office

If the error returns in multiple notebooks, or OneNote crashes outright, you might have deeper app corruption. On Windows 11, go to Settings > Apps > Installed apps, find Microsoft 365, and choose Modify > Quick Repair. An Online Repair is more thorough but requires you to sign back into all your accounts—use it only if Quick Repair fails.

For shared work notebooks, loop in your IT admin with precise details: the error code, the exact section and notebook names, and whether the web version works. That data beats a vague “OneNote won’t sync” ticket.

Outlook

OneNote’s sync engine gets sturdier with each Office update, but the very nature of cloud collaboration means occasional mismatches are inevitable. The good news is that error 0xE000005E is almost never a data-loss event—it’s a synchronization glitch that rewards a calm, structured response. By adopting habits like regularly checking sync status and avoiding monster sections full of PDF printouts, you can keep your notebooks humming along. And if that red icon ever appears, you’ll know exactly where to start.