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

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