Fix it now
A OneNote sync error tells you a notebook has stopped agreeing with the cloud copy, and nothing more: Microsoft publishes no meaning for any of these codes. Diagnose by scope instead – one section, one notebook, one machine or one team – because that is evidence you can actually check.
- Find out what is failing. In the OneNote desktop app, File then Info lists every notebook with its sync state, and the notebook list flags the affected section.
- Force a sync from the notebook list: right-click the notebook and choose to sync it, or use the sync shortcut Shift+F9 for the current notebook and F9 for all of them.
- Copy the pages from the failing section into a brand new section in the same notebook. If the copy syncs and the original still will not, the section itself is the problem: move the pages and delete the empty original.
- Close the notebook from the notebook list, then reopen it from OneDrive or SharePoint in the browser using the option to open it in the desktop app.
- Check the storage location in the browser: open the document library, confirm nothing is checked out, and confirm the library does not require metadata on upload.
- If every notebook is stuck rather than one, sign out of Office and back in, then retest.
Export the affected section from File, Export before you touch any cache. Anything that exists only in the cache is gone when the cache goes.
If File, Info shows every notebook synced, you are done. The next section explains what OneNote is doing when it stops and how to read the scope of the failure.
Why it happens
A notebook is not one file. It is a folder of section files held in OneDrive or a SharePoint document library, plus a local cache on every machine that opens it. Editing writes to the cache immediately, and the client then uploads changed pages section by section. Nothing you type is lost when sync fails; it is sitting in the cache waiting for the upload to succeed. That is the single most useful fact when a user is panicking.
Start with the honest position on the codes. None of the values in this family – 0xE0000007, 0xE0000784, 0xE00001A1, 0xE4020045, 0xE000005E, 0xE0000024 – has a meaning published by Microsoft on Learn or on the support site. Everything you will find attributing a specific cause to one of them traces back to community answers. The same code appears for several different conditions, so treating it as a diagnosis sends you looking for a fault that is not there.
What does discriminate is scope. If one section is stuck and the rest of the notebook is current, the problem is that section file or the library rule applying to it. If a whole notebook is stuck, look at permissions, the notebook’s location, or the library itself. If every notebook is stuck on one machine, look at sign-in, the cache or the network on that machine. If a whole team is stuck on the same notebook, look at the SharePoint site holding it.
Conflict pages are not a fault at all. They are what OneNote produces when two machines edited the same page and neither version can simply win. Merge them and move on; they are the system working, not failing.
The section file is checked out or blocked by the library
You have this one if The notebook lives in SharePoint or in a Teams channel, and one section will not upload while the rest are fine.
- Open the document library in a browser and navigate to the notebook’s folder.
- Look for a file showing as checked out and either check it in or discard the checkout.
- Confirm the library does not require a value in any column; required metadata blocks uploads outright.
- Check that versioning limits and retention settings are not preventing new versions being written, then sync again.
A notebook created in a Teams channel lives in that team’s SharePoint site. Fix it in SharePoint, not in the Teams client.
The notebook was moved, renamed or restored
You have this one if The whole notebook fails, and the location shown in its properties does not match where the files actually are.
- Close the notebook in OneNote so the client stops trying the old location.
- Open it from its current location in the browser and choose to open it in the desktop app.
- Confirm the old entry has gone from the notebook list rather than sitting alongside the new one.
- If pages exist only in the closed local copy, open that copy and move the pages across before removing it.
One page or embedded file the service will not accept
You have this one if One page consistently blocks its section, and it usually holds a large embedded attachment, a very large image, or a printout of a long document.
- Move the offending page into a new section of its own to isolate it and let the rest of the notebook sync.
- Remove the large embedded file from the page, store it in OneDrive, and link to it instead of embedding it.
- Sync, confirm the section clears, then move the page back if you want it where it was.
The local cache has become inconsistent
You have this one if Sync fails on this machine only, and the same notebook is perfectly current in the browser and on another device.
- Confirm every other notebook is fully synced, and export the affected section as a safeguard.
- Close OneNote entirely, including any background process.
- Rename the cache folder rather than deleting it, so you can put it back if something was only there.
- Start OneNote and reopen each notebook from its cloud location, letting it download fresh.
Do this last, not first. It is the only step in this article that can lose work, and only if something was in the cache and nowhere else.
Full reference
Where to look, by scope
| Pattern | Where the block is |
|---|---|
| One section stuck, the rest current | That section file in the storage location |
| A whole notebook stuck | Permissions, the notebook’s location, or the library |
| Every notebook stuck on one machine | Sign-in, cache or network on that machine |
| A whole team stuck on the same notebook | The SharePoint library holding it |
| Conflict pages appearing | Simultaneous edits from two devices, not a fault |
What the codes are worth
Every one of the six values in this article’s code list is recorded as not published by the vendor, and that is a finding rather than an omission. If you search one of them you will find confident explanations on answer sites, each contradicting the next, because nobody writing them had a source either. The practical consequence is simple: do not let a code choose your next step. Let the scope of the failure choose it.
There is one exception worth making. If the same code appears on every machine for every user against one notebook, that consistency is itself evidence, and it points at the storage location rather than at any client. That is a conclusion drawn from the pattern rather than from the number.
Isolating a section without risking anything
- Open the failing notebook and select the section that will not sync.
- Use File, Export and save the section to a local file. This is your insurance and it takes seconds.
- Create a new section in the same notebook and copy the pages into it a few at a time.
- Sync after each batch. The batch that stops syncing contains the page causing the problem.
- Move that page into a section of its own, remove the large embedded content from it, and sync again.
- Once the notebook is clear, delete the empty original section.
Checks on the storage side
- Confirm the account still has write access to the library. A permission change made for another reason is a common trigger and produces no useful message on the client.
- Confirm no required column has been added to the library. Required metadata blocks any upload that does not supply it, including OneNote’s.
- Check whether the site has hit a storage limit, which stops writes without explaining itself to the client.
- Check whether a retention or hold policy is preventing new versions being written.
- Where the notebook is in a Teams channel, remember that the fix belongs in that team’s SharePoint site.
If it is stuck on one machine only
- Sign out of Office on that machine and back in, then retest before touching the cache.
- Confirm the machine can reach the storage location in a browser as the same account.
- Check whether a security product is scanning the cache folder, which produces intermittent stalls that look like sync failures.
- Rename rather than delete the cache, and only after exporting anything that might exist there alone.
- If a new Windows user account on the same machine syncs the same notebook cleanly, the fault is in the original Windows profile rather than in OneNote.
Every code this article covers
| Code | What it points at | Source |
|---|---|---|
0xE0000007 |
Reported by OneNote when a notebook stops syncing; no published meaning | not published by the vendor |
0xE0000784 |
Seen on notebooks that will not upload; no published meaning | not published by the vendor |
0xE00001A1 |
Seen where a section stays behind the stored copy; no published meaning | not published by the vendor |
0xE4020045 |
Seen against notebooks held in SharePoint or a Teams channel; no published meaning | not published by the vendor |
0xE000005E |
Seen where sync cannot complete against the storage location; no published meaning | not published by the vendor |
0xE0000024 |
Seen after a notebook has been moved, renamed or restored; no published meaning | not published by the vendor |
Confirm the fix worked
- File, Info shows every notebook as synced, with no warning icons in the notebook list.
- An edit made on a second device appears on the first within a reasonable time.
- The previously failing section shows no sync warning after a full sync.
- No new conflict pages appear after a day of normal use across the devices involved.
- The exported section file can be discarded, which is the point at which you know you are finished.
Questions people ask about this
Will I lose notes if sync never recovers?
Not usually. Unsynced changes sit in the local cache and can be exported from the machine holding them. The order matters: export the affected section before you touch the cache, not after.
What does my error code mean?
Microsoft does not publish a meaning for any of the codes in this family. Anything you read that assigns one is somebody’s inference. Work from the scope of the failure instead, which is why this article is organised that way.
Does fixing this cost anything?
No. Every fix here is a permission, a location or a cache. The only licensing angle is the reverse case, where the account has lost access to the site entirely, which is a different problem with a different symptom.
The browser shows a newer version than my desktop app. Why?
Because upload from another device succeeded and download to this one has not. When it is the other way round, this machine’s upload is what is stuck. Which side is behind tells you which machine to work on.
Can I keep notebooks on a plain file share?
The current apps expect OneDrive or SharePoint. Notebooks on an ordinary file share are a legacy arrangement rather than something to build on, and moving them removes a whole category of sync problems permanently.
