A computer that still opens your documents can leave three important questions unanswered: whether its security-update program covers that device, whether the latest relevant update installed, and whether you can recover the work stored on it. Treat those as separate checks before deciding that a Windows 10 PC can remain in service or is ready to replace.
Start with the current program, not an old deadline
As checked on October 5, 2026, Microsoft's Canadian consumer ESU page gives October 12, 2027 as the program end date and says existing enrollments continue automatically. It lists eligible Windows 10 22H2 editions, current updates and the KB5126256 preparation package as prerequisites. Consumer ESU supplies critical and important security updates, without new features or technical support. Check enrollment in Settings > Update & Security > Windows Update. These are Microsoft's published terms, not Inquory's confirmation that any reader's PC qualifies or is enrolled. Microsoft Canada consumer ESU
The consumer offer excludes commercial scenarios, including specified managed-device configurations. A work computer needs its organization's licensing and support process; the separate commercial ESU program must not be treated as a household entitlement. Consumer exclusions · Organizational ESU
Older guidance may contain a different consumer deadline. The current pages reviewed here do not establish when their text changed. This guide is a current verification method, not a claim that Microsoft announced an extension today.
Inquory interpretation: make a small evidence record for each device
Start with the computer in front of you. Give it a private household label such as “kitchen laptop,” then record the Windows edition and version displayed in its settings. Do not copy a serial number into a public comment. If someone else manages the computer, ask that person to confirm its program and permitted changes before enrolling, upgrading or altering accounts.
Next, record what Windows Update actually says about enrollment. A news article saying a program exists is not device evidence. Neither is a payment receipt by itself: it may concern another machine or account. If you have several PCs, verify each separately. Where the screen is unclear, record “not confirmed” and the exact question for official support instead of changing it to “covered.”
Finally, examine the most recent installed security update shown in the device's update history. Record its identifier, installation date and any error or restart request still visible. Enrollment and successful installation are different observations. This checklist does not decide which particular update your machine needs; use Microsoft's current instructions for its edition and configuration, or your administrator's process.
Keep the record private. It should contain dates and status, not passwords, recovery codes, product keys or account tokens. If a screenshot helps, crop out unrelated personal details before sharing it with a support contact you have independently verified.
A worksheet that distinguishes facts from plans
| Private field | What to record | What it does not prove |
|---|---|---|
| Device label and owner | A recognizable local name; who may authorize changes | That another family or work device is covered |
| Edition and version | The values currently displayed on that PC | Eligibility based only on its age or appearance |
| Program route | Consumer or organization-managed, with the source checked | That the rules for the other route apply |
| Enrollment observation | Exact visible status and date checked | That an update successfully installed |
| Update observation | Installed update identifier, date and unresolved messages | That every application is current or every risk removed |
| Recovery exercise | One representative file reopened from its recovery copy | That all files and applications have been restored |
| Next review | A date and the person who will recheck or migrate | A permanent promise of support |
This is an Inquory planning worksheet, not a Microsoft diagnostic tool. A blank field identifies a question to resolve; it does not automatically mean the PC has failed.
Check recovery before making a large change
Microsoft's Windows Backup documentation describes separate folder and preference controls tied to a personal Microsoft account. Its consumer app does not support work or school accounts, and remembered applications may still need reinstalling. Review what is selected and what its status actually confirms. Windows Backup documentation
Inquory's practical next step is a small recovery exercise: choose an ordinary, non-sensitive sample file, make a recovery copy using your approved method, and reopen that copy without overwriting the original. Record which location was tested. Then identify important work that the sample does not represent, such as an application's own database or licensed software. Ask how those items would be restored before wiping, trading in or replacing the computer.
Do not enable new cloud synchronization merely because a checkbox looks convenient. Decide which information may be copied and who controls the destination. A successful sample-file test is useful evidence with limited scope; it is not certification of a full backup.
A fictional household example
Maya is a fictional reader with a personal laptop and a separately managed work PC. Her personal laptop displays an ESU enrollment confirmation, but its update history also shows an unresolved installation problem. She records both facts and seeks the applicable official troubleshooting guidance. She does not mark the installation successful because enrollment is confirmed.
For the work PC, she asks its administrator to confirm the organizational route instead of applying the household procedure. Before deciding what to replace, she restores a sample personal document and discovers that her budgeting application's data needs a separate recovery check. This is an invented example of decisions to record, not a tested result or a claim that a specific device is safe.
Decide what the extra time is for
A time-limited update program can be part of a transition plan. Choose a concrete next task: confirm upgrade eligibility through the official Windows route, test an essential application on a proposed replacement, or resolve an unverified recovery method. Give that task a date and an owner. Avoid unsupported upgrade workarounds based on this guide.
For the information stored inside an app, use Inquory's export and exit-plan guide. For account recovery before a device change, see the passkeys and password-manager recovery plan. Each addresses a different part of leaving an old PC without losing access or useful work.
Editorial method and limits
Sources checked October 5, 2026. Microsoft's Canadian consumer page, consumer page reached through the older support URL, organizational documentation and Windows Backup documentation were opened. The consumer pages are substantially the same vendor material, not independent corroboration. No current announcement date, device eligibility, payment, installation, enrollment or restore outcome was tested. No affiliate recommendation or sponsorship is involved. Refresh the program terms before acting on a particular device.