Technology & Software

Windows 11 24H2 End of Updates: What to Know About 26H2

Windows 11 24H2 Home and Pro reached end of servicing October 13, 2026. Check your edition, verify encrypted backups, and move to a supported version safely.

October 26, 2026 update: what to do if you are still on 24H2

Windows 11 24H2 Home and Pro reached end of servicing on October 13, 2026. If you still use an affected edition, make moving to a supported version a priority. This is an edition-specific deadline, not the end of Windows 11 (Microsoft, 2026b).

Start by checking your edition and version, protecting your important information, and reviewing the supported update offered in Windows Update. Do not force an upgrade past a compatibility safeguard. The checklist below is designed to help you prepare and verify the result, including access to locally stored records.

What end of servicing means

Microsoft states that affected 24H2 editions will no longer receive monthly security updates, preview updates, fixes for known issues, time-zone updates, or technical support after the deadline. Continuing to use that release is not the same as keeping a supported Windows installation current (Microsoft, 2026a).

This is not a notice to erase your computer or reinstall every application. Plan the move to a supported version around the device’s compatibility and recovery needs rather than treating the deadline as a reason to skip preparation.

First, check your edition and version

Open Settings → System → About and look under Windows specifications for the edition and version. Record both: “Windows 11” alone does not identify the servicing timeline. Microsoft documents this route in its device-information guide (Microsoft, n.d.-a).

Microsoft’s release table distinguishes these common situations (Microsoft, 2026b):

Installed edition and version End of servicing Practical next step
Windows 11 24H2 Home or Pro October 13, 2026 Prepare to move to a supported version.
Windows 11 25H2 Home or Pro October 12, 2027 Keep it updated; the 24H2 deadline is not your deadline.
Windows 11 24H2 Enterprise or Education, standard servicing October 12, 2027 Follow your organization’s update plan.

LTSC editions have separate timelines. For those editions or an employer- or school-managed PC, confirm the applicable lifecycle and update plan with your IT team rather than changing organization settings yourself (Microsoft, 2026b).

Understand what “26H2 is available” means

Microsoft now reports full 26H2 availability for 24H2 and 25H2 devices. Check Windows Update for your device’s offer; compatibility safeguards still matter (Microsoft, 2026c).

Open Settings → Windows Update to check what your PC offers. Install applicable updates, but do not mistake an installed final update for an extension of 24H2’s servicing timeline. If 26H2 is not offered, check whether a supported version such as 25H2 is offered for your device. If no supported update appears or installation fails, seek help from Microsoft, your device manufacturer, or your IT team rather than leaving the issue unresolved.

Microsoft may delay an offer because of a safeguard hold for a known compatibility issue; it advises against manually bypassing such a hold (Microsoft, 2025). Review current release health and our 26H2 compatibility checklist before deciding how to proceed. The linked Microsoft guidance, not an older checklist, is the authority for current issue status.

Prepare before the update

A feature update is a good time to confirm that important records are organized and recoverable. These are practical preparation recommendations, not a guarantee that an update will be trouble-free.

  1. Check application and device compatibility. List the applications, printers, audio devices, and other equipment you depend on. Check the vendor’s current support guidance and Microsoft’s release-health page. For managed devices, let IT evaluate configuration-specific risks.
  2. Identify locally stored records. Include files in application workspaces, not just the Documents folder. Note which information exists only on this PC, where the originals are kept, and which applications require their own backup or export procedure.
  3. Create a current encrypted backup where your application supports it. Use its documented backup function rather than assuming that copying an application folder produces a usable recovery package. Keep originals unchanged and confirm that the backup covers the records you intend to recover.
  4. Verify recovery without overwriting your only working copy. Follow the application’s documented validation or restore process in a separate, supported test location where possible. Check that the package can be opened with the required credentials and that representative records are readable. A filename, upload confirmation, or successful export alone does not prove recoverability.
  5. Protect the backup and its credentials separately. Keep a recovery copy outside the PC being updated, using storage appropriate for the sensitivity of the records. Know the package’s passphrase and recovery instructions. Do not store the only credential copy inside the same locked workspace you may need to recover.
  6. Check drive-recovery access. If BitLocker or device encryption is enabled, confirm how to obtain the correct recovery key if prompted. Microsoft says it cannot retrieve or recreate a lost BitLocker recovery key. That key is distinct from an application’s vault or backup passphrase (Microsoft, n.d.-b).
  7. Choose a practical maintenance window. Allow time for installation, restarts, application checks, and support if something goes wrong. Avoid beginning immediately before a deadline or a task that depends on the computer.

An offline or local copy is useful, but a second file on the same drive is not a complete backup strategy. Encryption protects access to a copy; it does not by itself protect against drive failure, accidental deletion, or a forgotten passphrase. For more on those distinctions, see our guide to local-first software.

Verify access after the upgrade

Do not stop at the Windows sign-in screen. Before returning to normal use:

  1. Recheck Settings → System → About to confirm the installed edition and version, then review Windows Update for any remaining applicable updates.
  2. Open each important application and check representative records, attachments, and other essential workflows. Confirm that the expected local workspace is open, rather than an empty new workspace or an older restored copy.
  3. Check the equipment you rely on, such as printers, audio devices, and external storage.
  4. Confirm that backup destinations remain accessible and your backup routine still runs. Retain the verified pre-upgrade package while you establish that the updated environment works.
  5. If information appears missing, pause changes that might overwrite it. Check the application, account, workspace, and backup location with the relevant support team before resetting the app or restoring over existing data.

Keep local-first records in the plan

For people using a local-first workspace such as Meritwright Vault Desktop or Norivault for Windows, the key question is not simply whether Windows finishes updating. Confirm that the application opens and your locally stored information is accessible afterward. Maintain a separate, current encrypted backup package according to the product’s instructions, and know where any exported copy is stored.

An exported package saved to a cloud-synced folder may be uploaded automatically under that provider’s settings, or you may upload it yourself. That separate copy is outside Meritwright’s control. Keep the passphrase used for that backup: changing a current vault passphrase does not change an earlier exported package. Review the Vault Desktop backup and recovery notice or the Norivault Desktop backup and recovery notice for the relevant product’s limitations.

This is practical update preparation, not a claim that either product manages Windows updates, replaces a complete backup strategy, or guarantees compatibility with a particular Windows feature release. Your operating-system updates, application data, and backup destination are related but distinct responsibilities.

The bottom line

If you are still on an affected 24H2 edition on or after October 13, 2026, prepare a verified backup and move to a supported version through the appropriate update path. If you are already on a supported release, keep it current. Do not force 26H2 past a compatibility safeguard simply because it is the newest version.

Microsoft’s dates and rollout status can change; use the linked release-information and release-health pages for the latest device-specific guidance.

References