Microsoft has set a hard stop for one of its longest-running note-taking apps: OneNote for Windows 10 will become read-only on October 14, 2025, locking all editing and sync capabilities. The company is urging everyone—from casual home users to enterprise IT departments—to switch to the modern OneNote on Windows app before the cutoff.

What’s Changing, and When

The retirement of OneNote for Windows 10 has been telegraphed for months through in-app banners, but the formal announcement in late August 2025 — first reported by The Register — makes the deadline explicit. After October 14, 2025, the legacy Universal Windows Platform (UWP) app will no longer accept new edits or synchronize notebooks with OneDrive or SharePoint. Users will be able to open and read existing notes, but that’s it. No further security patches, bug fixes, or feature updates will be delivered for that client.

The timing is no coincidence. October 14, 2025 also marks the end of support for Windows 10 itself and several perpetual Office versions (Office 2016 and Office 2019). Microsoft is consolidating not just its operating system lifecycle but its note-taking strategy. The sole survivor will be OneNote on Windows — the modern desktop app delivered through the Microsoft Store and the Win32 executable. That client is already fully supported and will be the launchpad for future capabilities, including Copilot-powered note generation.

Who Feels the Impact

The change touches virtually every corner of the OneNote ecosystem:

  • Home users: If you’ve been sticking with the pre-installed OneNote for Windows 10 app on a home PC or Surface, your editing privileges expire in less than two months. Your cloud notebooks will remain untouched on OneDrive, but you’ll need to access them through another client.
  • Students and educators: Class Notebooks, assignment feedback, and collaborative note-taking workflows that rely on the UWP app will freeze. Schools with shared or lab machines still running Windows 10 must plan a coordinated switch.
  • Businesses and IT admins: For organizations managing fleets of Windows 10 devices, this is another item on an already crowded migration docket. The risk is amplified because the same deadline affects the underlying OS and Office suites. Users who discover their notes have suddenly become read-only on the same day their PC reaches end of support will swamp helpdesks.

The practical sting: any notebook that hasn’t been fully synchronized to the cloud by October 14 becomes trapped in a read-only state on that device. Recovering edits made locally but not synced will be nearly impossible without manual exports or backups taken before the deadline.

Why Microsoft Is Pulling the Plug

OneNote’s identity crisis traces back more than a decade. It began as a standalone Office product, later split into two parallel apps for Windows: the traditional Win32 desktop version and a UWP version purpose-built for Windows 10. The UWP app was optimized for touch, pen input, and battery life, and it came pre-installed on millions of devices. But maintaining two codebases sapped engineering resources and confused users.

Over the past few years, Microsoft has been squeezing the UWP client toward retirement. Feature updates dried up; the sync engine diverged; and increasingly prominent migration banners nudged users toward the newer OneNote on Windows app. The message from Redmond is now unequivocal: “We’re consolidating our efforts into a single, more powerful OneNote on Windows app,” the company said in its advisory. “This streamlined direction will help us deliver new features faster, ensure long-term support, and provide a foundation for future innovation in OneNote.”

That future innovation leans heavily on AI. Copilot integrations — automatic meeting notes, content summarization, and generative page creation — are being built into the new app and will never appear in the UWP version. For Microsoft, the end of OneNote for Windows 10 is the final step in clearing the decks for a modern, cloud-connected, AI-enhanced experience.

Your 5-Step Migration Guide

If you’re an individual user, the migration is straightforward but requires attention before October 14. Here’s exactly what to do:

  1. Force‑sync every notebook. Open OneNote for Windows 10, right‑click each notebook in the list, and choose Sync This Notebook. Wait for the “Up to date” confirmation. This ensures all pages, attachments, and handwritten ink are safely stored in your OneDrive or SharePoint account.
  2. Export local-only content. For any notebook you keep exclusively on your device (visible in OneNote but not linked to a cloud account), create a backup. Go to File > Export or File > Open Backups, and save a copy — as a OneNote package (.onepkg) or PDF — to an external drive or cloud folder. These local notebooks are the most vulnerable to data loss.
  3. Follow the in‑app migration banner. Most users will see a prominent banner at the top of the OneNote for Windows 10 window. Clicking “Switch now” will open the Microsoft Store listing for the new OneNote on Windows app. Install it and sign in with the same Microsoft account.
  4. Verify your notebooks. After signing in to OneNote on Windows, check that all your cloud notebooks appear. Page content, section tabs, and formatting should carry over seamlessly. If you exported backups, test restoring them via File > Open Backups.
  5. Update your shortcuts. Replace taskbar or desktop icons for the old app with the new one. Take a few minutes to explore the refreshed interface and note where familiar tools — like the drawing ribbon or page templates — now live.

That’s it for consumer accounts. The process typically takes less than 30 minutes per device.

Enterprise Checklist: Secure Your Data Before the Deadline

For IT administrators, the migration is a project, not a quick switch. The convergence of deadlines on October 14 turns this into a high‑stakes exercise in change control. Use these steps to build your plan:

  • Inventory and prioritize. Identify every device with OneNote for Windows 10 installed, and flag users who are heavy note‑takers. Pay special attention to local‑only notebooks that never synced — these are your data‑loss time bombs.
  • Communicate early and often. Send a company‑wide notice with the firm October 14 cutoff, a link to your migration instructions, and a reminder to sync now. Provide a one‑pager or short video covering the key differences between the old and new apps.
  • Force syncs programmatically. Use scripts or Group Policy to trigger a full sync of known notebooks before the deadline. Microsoft offers a sample migration script that detects unsynced notebooks and exports them; adapt it to your environment.
  • Automate app deployment. Push the OneNote on Windows app via Microsoft Intune, SCCM, or your endpoint management tool. Pre‑install it now, so users only need to sign in. After the migration, consider blocking or uninstalling the UWP app to prevent confusion.
  • Back up local notebooks obsessively. Before any mass cutover, execute a scripted export of all local‑only notebooks. Store those backups in a secure network location and test restoration on a pilot group.
  • Test integrations. Validate that Class Notebooks, Teams assignments, SharePoint links, and any education or business workflows still function as expected in the new client. Third‑party add‑ins built for the UWP app may need replacement.
  • Review Copilot and compliance settings. Once users land in OneNote on Windows, they’ll have access to Copilot features if your tenant enables them. Verify data handling, DLP, and AI governance policies before flipping that switch. Organizations in regulated industries may need to disable certain AI features until compliance is confirmed.
  • Prepare helpdesk scripts. Arm your support team with troubleshooting flows for the most common post‑migration issues: missing notebooks, sync errors, ink‑tool changes, and local‑notebook recovery.

A phased rollout — pilot, then broad deployment — remains the safest approach. The biggest single mistake is waiting until the final week, when the helpdesk is already crushed by Windows 10 ESU decisions and Office compatibility surprises.

What Happens If You Do Nothing?

On October 15, the OneNote for Windows 10 app will still launch, but each open notebook will bear an uneditable, unsynced status. Users who rely on the app daily will immediately feel the pain: they can read meeting notes from yesterday but can’t add today’s action items. For students, the sudden freeze will disrupt class note‑taking. For businesses, it could mean lost productivity, data silos, and a torrent of frantic helpdesk tickets.

More dangerously, any unsynced local notebooks become digital ghosts. Without an export, those pages are visible but forever frozen in that client. Recovering the content later involves tedious page‑by‑page copying or forensic data extraction — tasks no one wants during an already busy October.

Beyond the Deadline: Copilot and Compliance

The new OneNote on Windows app isn’t just a replacement; it’s a platform for AI features that Microsoft is aggressively integrating into Microsoft 365. Automated meeting summaries, voice‑to‑text transcription, and Copilot‑driven page generation will appear first (or only) in the unified client. For organizations that want those tools, migration is a prerequisite.

But there’s a compliance wrinkle: migrating to a client that can invoke Copilot means revisiting data governance. Administrators should map out which Copilot features will be active, review data retention and eDiscovery settings, and ensure that content processed by AI meets internal and regulatory standards. The migration deadline, then, is also the moment to tighten up Copilot policies.

Compounding the schedule, Microsoft is separately retiring back‑end support for voice features — Dictation, Transcription, and Read Aloud — in older Office clients in early 2026, unless those clients are updated to a minimum build. Organizations that rely on these accessibility tools need to factor that deadline into their migration timeline as well. The OneNote change on October 14 isn’t happening in isolation; it’s part of a broader platform shift.

Outlook

October 14, 2025 will be a milestone: the last day the OneNote for Windows 10 app accepts a new keystroke or syncs a page. For users who act now, the transition is smooth — a few clicks, a fresh app, and continued note‑taking with no loss of data. For those who wait, the day arrives as a hard wall, with notebooks frozen mid‑thought.

The consolidation, while disruptive, is the right move for a healthier OneNote ecosystem. One codebase means faster updates, consistent cross‑platform behavior, and an app that’s ready for AI‑augmented productivity. The price is the migration effort over the next seven weeks. Start by syncing every notebook, back up the precious local ones, and install the new OneNote today. Your October self will thank you.