Microsoft has drawn a hard line: after October 14, 2025, OneNote for Windows 10 will become read-only, cutting off editing and cloud sync for millions of users still clinging to the legacy UWP app. This move, announced through Microsoft’s official tech community and support channels, aligns with the broader Windows 10 end-of-support date but carries its own immediate consequences — users who fail to sync their notebooks and migrate to the modern OneNote on Windows client risk permanent data loss.

It’s not a sudden shutdown. Microsoft is staging the retirement in phases designed to push users toward the newer app. In June 2025, the company completed a sync infrastructure upgrade that deliberately slows performance on older OneNote clients. Starting in July, in-app banners will nag users to switch. Come October 14, the legacy app will launch only for viewing — no editing, no saving, no cloud sync. For IT administrators overseeing fleets of devices, the clock is ticking louder than for individual consumers.

Staged Obsolescence: The Timeline Unfolds

The end of OneNote for Windows 10 isn’t a single event; it’s a series of calculated nudges that began months before the hard cutoff. Microsoft confirmed the timeline through Message Center posts and a detailed Tech Community blog, giving organizations a clear — if uncomfortable — roadmap.

  • June 2025: A sync infrastructure upgrade went live. Older OneNote clients, including the Windows 10 UWP app, now experience slower sync speeds and occasional read-only prompts with messages like “Saved offline – Refresh.” Microsoft frames this as a necessary modernization, but independent reporting by Windows Latest and How-To Geek describes it as an intentional throttle to nudge users away. The effect is the same: notebooks may temporarily become uneditable until the user refreshes or updates.
  • July 2025: In-app banners and migration prompts begin appearing inside OneNote for Windows 10, directing users to the Microsoft Store listing for OneNote on Windows. Administrators should have already seen advance notice in the Message Center; now end users will face the pop-ups directly.
  • October 14, 2025: End of support. The app enters a permanent read-only state. All editing, saving, and cloud sync from this client are disabled. Users can still open the app to view existing notebooks, but any new content must be created elsewhere.

This staged degradation is more than cosmetic. It shrinks the operational usefulness of the legacy app weeks before the final date, effectively forcing migration through inconvenience. Users who rely on real-time collaboration across devices will feel the pinch first.

Why Microsoft Is Killing the UWP OneNote

Behind the timeline lies a strategic consolidation. OneNote has long existed in multiple forms on Windows: the original desktop (Win32) app, the UWP OneNote for Windows 10, the web client, and mobile versions. Microsoft now wants a single, modernized codebase — the “OneNote on Windows” client — that can receive faster updates, stronger security, and new AI features.

In its official communications, Microsoft highlights three drivers:

  • Security and compliance: The new app supports Microsoft Information Protection (MIP) sensitivity labeling, a must for enterprise compliance. The legacy UWP app lacks these enterprise-grade controls.
  • Performance and sync reliability: The modern sync infrastructure is built for the new client. Older clients, stuck on the old backend, will only become less reliable over time.
  • AI integration: Microsoft has teased Copilot-powered note generation and other AI capabilities that require the new app’s extensibility. While no firm delivery dates are attached, the roadmap depends on a unified client.

Critics argue that the move also aligns with Microsoft’s push to retire Windows 10 itself, but the one-two punch is unmistakable. Even if a user pays for Extended Security Updates (ESU) for Windows 10, the OneNote for Windows 10 app will still go read-only. Only the Microsoft 365 apps on Windows 10 will continue receiving security patches until 2028; the UWP OneNote is explicitly excluded.

Immediate Impact on Consumers

For individual users, the practical steps are straightforward but time-sensitive. The risk is highest for anyone who has been using OneNote for Windows 10 offline or with incomplete syncs. If a notebook isn’t fully synced to OneDrive (or SharePoint) by October 14, those unsynced sections become trapped in a read-only sandbox — accessible only through the legacy app’s local cache, which could be deleted if the app is uninstalled.

Microsoft’s support article “Moving to OneNote on Windows” offers a lifeline:

  1. Sync everything now: Right-click each notebook in OneNote for Windows 10 and select “Sync This Notebook.” Confirm success before moving on.
  2. Install the new app: The simplest path is to follow the in-app banner (if visible) or search the Microsoft Store for “OneNote.” The app is free and signs in with your existing Microsoft account.
  3. Verify your notebooks: Open OneNote on Windows, sign in, and ensure all notebooks appear editable. If something is missing, use the “Open Backups” option under File to restore from the legacy app’s backup folders.

The advice is simple: do not uninstall the old app until you are certain everything is safely in the new client. For users still on Windows 10 past October 14, note that the new OneNote app runs fine on both Windows 10 and 11, so there’s no need to upgrade the OS solely for OneNote — but the OS itself is also out of support, posing additional security risks.

Enterprise and IT Administrator Challenges

Organizations face a more complex puzzle. OneNote for Windows 10 was often pre-installed on Windows 10 devices or deployed through the Microsoft Store for Business; its UWP sandbox complicates backup and uninstallation. Microsoft’s official migration guide details the twists and turns admins must navigate.

The UWP Sandbox Trap

The legacy app stores unsynced local sections inside a user-specific sandbox path. When the app is uninstalled, that sandbox is deleted — erasing any data not yet synced to the cloud. To avoid this, admins must run backup commands per user before removal, then move the backups out of the sandbox to a safe network location. The guide provides exact paths and a protocol (onenote-uwp://backup:) to trigger backups programmatically.

Bulk Deployment and Uninstallation

Because the UWP app installs per user, standard system-wide uninstall tools miss it. The recommended approach uses Intune discovered apps to inventory installations (search for AppId “Office.OneNote”), then script per-user backups and uninstalls. Microsoft documents a WinGet command for deploying the new OneNote on Windows silently: winget download 9wzdncrfhvjl --skip-license. After verifying backups, admins can uninstall the legacy app — but only after validating each user’s data.

Sync Interruptions and User Communication

The June 2025 sync slowdowns will likely trigger support tickets. Notebooks may open as read-only with a “Refresh” prompt, or display sync error codes like E000006C. Microsoft advises updgrading clients to resolve most issues, but admins must proactively communicate these expected hiccups to users. A well-timed email explaining the banners and sync wobbles can prevent panic.

A Practical Migration Playbook

For Consumers

  • Force-sync all notebooks immediately. Right-click each notebook, select “Sync,” and wait for “Synced” status.
  • Install OneNote on Windows from the Microsoft Store.
  • Leave the old app installed until you confirm everything is accessible in the new app.

For Small Businesses and Education

  • Send a 60–90 day notice explaining the change and providing step-by-step instructions.
  • Pilot with a small group: use WinGet to push the new app, then have users validate their notebooks.
  • Handle exceptions manually: use the UWP backup protocol for any user with unsynced content, then uninstall the legacy app per user only after confirmation.

For Large Enterprises

  • Inventory all devices running OneNote for Windows 10 via Intune or equivalent.
  • Scripted backups: run onenote-uwp://backup:, examine UWPBackUpStatus.json and UWPSyncStatus.json for integrity, and move backups to a secure share.
  • Deploy the new app through WinGet or Microsoft Store for Business, configure policies (Group Policy/Intune), and validate sensitivity labels and sync before broad rollout.
  • Wave-based uninstall: only remove the legacy app after confirmed backup success, working user by user to avoid data loss.

Benefits, Risks, and Unanswered Questions

What You Gain

  • Active development: The modern app receives regular patches, performance tweaks, and new features.
  • Enterprise controls: Sensitivity labeling, Intune policy management, and centralized update deployment are now possible.
  • AI readiness: While Copilot features are still promises, the architecture is in place to support them.

What You Risk

  • Data loss: Unsynchronized notebooks are the biggest danger. The backup process requires discipline; skipping it can mean permanent loss.
  • User frustration: UI differences — especially for pen and touch users — may require retraining. The staged slowdowns, while planned, may be perceived as heavy-handed.
  • Operational disruption: If migration is delayed until September or October, the sync throttling could hinder classrooms or teams that depend on real-time notebook collaboration.

Cautious Notes

  • Copilot for OneNote: Microsoft has mentioned AI features, but no ship date is given. Treat this as a roadmap aspiration.
  • “Intentional slowdown”: While Message Center posts describe the sync changes as an infrastructure upgrade, the practical effect — slower sync on old clients — led independent analysts to call it a deliberate throttle. Admins should focus on mitigation, not debate intent.
  • Windows 10 ESU: Paying for Windows 10 Extended Security Updates does not extend OneNote for Windows 10 support. The app goes read-only on the same date regardless.

The Hard Stop: What October 14, 2025 Means

After this date, launching OneNote for Windows 10 will present a view-only interface. Notebooks stored locally will still be visible, but you cannot type, draw, or sync. For anyone needing to edit, the options are:

  • OneNote on Windows (the modern, supported app)
  • OneNote for the web (via onenote.com)
  • OneNote mobile apps (iOS, Android)

For users stuck on Windows 10 without plan to upgrade the OS, the web app offers a temporary bridge, but the native experience on the new client is far smoother. Microsoft’s broader push toward Windows 11 — and its Copilot+ PC ambitions — makes this OneNote transition feel like just one piece of a larger platform shift.

Executive Summary for Decision Makers

Time is the enemy. Every week of delay brings you closer to the sync slowdowns and banners of summer 2025, which will disrupt users and flood help desks. The hard read-only date will not bend. To protect your data and productivity:

  1. Inventory immediately. Know how many devices still run the UWP app.
  2. Back up unsynced content now. Use the documented backup protocol and move data out of sandboxes.
  3. Deploy the new app through your standard tooling and validate for critical user groups.
  4. Communicate early — tell users what to expect, when, and how to get help.

Microsoft’s consolidation to a single OneNote client is a defensible engineering choice. But the execution — a phased obsolescence that spans months — demands proactive planning. The steps are documented, the scripts exist, and the deadline is firm. Now it’s up to you to execute before your notebooks become accidentally frozen in time.