OneNote Web Version - "Unsaved Changes (Internal Error)" - On All Devices

Question

I need to update a OneNote notebook on OneNote for Web since it handles file printouts a little differently than the standalone apps. However, every time I try to upload a file printout, the document icon that appears never stops its loading animation, and I eventually get a sync error.

The page will sync soon afterward, but will never load the document into the page. Any other device that tries to access the page in question will see the document icon with a red x on it, and pages present but empty.

Insert File Attachment works just fine. This is only an issue with Insert File Printout.

• I have tried the entire process with alternate files to ensure it is not an issue with a specific file.
• I have tried clearing my cache and data and restarting my browser.
• I have tried logging out and in again.
• I have tried restarting my computer.
• I have tried using a different computer.
• I have tried using the web version on a mobile device.

All of the above things end in the same result (and I have done them all multiple times).

Standalone apps, whether on computer or mobile devices, will upload the same files without issue - but since the size they load in at is different, and their behavior when deleting pages is different, I need the web version to work.

I am using a work account (different from the one I am posting from), and on a Mac, using Chrome (though those details shouldn't matter since I have used another computer, and an Android phone, all with the same end result).

Answer 1

Hi, coffeeGrounds

Since attachments sync fine and only printouts fail, the problem seems to be in the web app's step that converts your file into page images. That doesn't explain why the standalone apps work, but it does give you a few ways around it.

Here are some suggestions you can try:

Insert the printout in the standalone app, then open the same page in OneNote for the web and resize the printout images there. A printout is basically a stack of images, so once it syncs you can drag each one to the size you want in the web version. If it doesn't show up right in the web view, it is recommended to copy the printout from the app and paste it onto the page in the web version.

Skip the printout feature and use Insert > Picture instead. Save each page of your file as a PNG or JPG first. On a Mac, you can export PDF pages as images from Preview. Pictures don't go through the conversion step that's failing, so they should load right away in the web version.

If your files are Word or PowerPoint docs, export them to PDF first and insert the PDF as the printout. Also try a short file name with no special characters.

Delete the stuck page with the red X before you try again, since a broken printout can keep failing to sync. Copy anything you need from it to a new page first.

Answer 2

Because the failure occurs in OneNote for the web across multiple devices and files while the desktop and mobile apps can insert the same printouts, ask the work account’s Microsoft 365 administrator to check tenant service health and open a Microsoft support request if no relevant incident is listed.

Administrator action

1. In the Microsoft 365 admin center, go to Health → Service health.
2. Check:
   • Active issues Microsoft is working on
   • Issues for your organization to act on
   • Issue history, covering the date the problem began
3. Look for incidents or advisories involving Office for the web, OneNote, OneDrive, or SharePoint.
4. If nothing matches, select Report an issue from Service health. Microsoft correlates these reports across organizations and creates an incident or advisory when the problem is service-originated and sufficiently widespread. Service Support and Helpdesk administrators can view service health. ^1^
5. Have the administrator create a support request from the admin center. Include:
   • The exact message: “Unsaved Changes (Internal error)”
   • The work account and affected notebook location
   • Date, time, and time zone of a recent reproduction
   • Affected browser and devices
   • The screenshot
   • Several example file types and sizes
   • Confirmation that File Attachment succeeds
   • Confirmation that File Printout fails in the web client across devices
   • Confirmation that the same files work in standalone OneNote

There is no Microsoft-published notice identifying this exact OneNote for the web/File Printout/Internal error combination as a named known issue. The public web help index also does not provide a dedicated repair procedure for this printout failure. ^2^

Isolate notebook scope before escalation

Run these tests in OneNote for the web using the same work account:

1. Create a new blank page in a different section of the affected notebook and insert a small, ordinary PDF printout.
2. If that fails, create a temporary new notebook in the same work OneDrive and repeat the test.
3. Record the result:
   • Only the original page fails: discard that incomplete page after copying any valid content elsewhere.
   • All pages in one section fail: create a new section and copy—not move—the valid pages into it.
   • The original notebook fails but the temporary notebook works: report the original notebook as the affected resource.
   • Every notebook fails: report it as an account/tenant-level OneNote web printout-conversion failure.

Microsoft documents copying pages into a new section as the workaround when one section or its pages stop syncing while the rest of a notebook remains current. Back up unsynchronized content before closing notebooks or deleting affected pages. ^3^

Conditional checks

• Permissions: File Printout requires edit permission on the destination section. Because ordinary attachments and page synchronization work, this is less likely, but test the temporary notebook under the same account to distinguish section permissions from a broader failure. ^4^
• Sensitivity labels: If the tested documents carry organizational sensitivity labels, tell the administrator. Microsoft states that printouts of labeled files require sensitivity labels to be enabled for OneNote in the organization. This check applies only if the source files are labeled; do not change tenant labeling configuration merely from the internal-error message. ^4^

Do not repeat cache clearing, sign-out/sign-in, computer restarts, or additional browser/device tests; those paths have already been ruled out. Until support resolves the web conversion failure, the safe workaround is to insert the printout through a standalone OneNote app and avoid editing the incomplete red-X page.

---

References

1. How to check Microsoft 365 service health
2. OneNote for the web Help | Microsoft Support
3. Fix issues when you can't sync OneNote | Microsoft Support
4. Insert or attach files to notes | Microsoft Support