How to check whether your operating system is still receiving security updates

Before looking up support dates, write down which device you have and what software it runs. On a computer, check the operating system name, version and, if shown, edition or update channel. On a phone, note the model and system version. The relevant information is usually in Settings, under sections such as “About,” “Device information” or “System”; names vary by manufacturer and interface. Record what the device actually displays rather than relying on a general impression or memory.

Do not stop at a broad description such as “Windows,” “Android” or “iOS.” The version, edition and model can affect which updates apply to the device. On Android, the phone manufacturer may also publish its own information about support for a particular model. It is therefore useful to copy the identifiers exactly as they appear on screen, including any edition or model suffix, instead of trying to reconstruct them later. The more precise the identification, the easier it is to compare the device with an official support notice.

Also record the date on which you checked. Support pages are updated, and an end date may apply to a specific edition rather than every variant that shares a product name. If the device belongs to a business or is managed by an organisation, note that too: internal policies can influence when updates are distributed. Keeping these details together gives you a reliable starting point if you need to check again, compare a later notice, or ask the manufacturer for help.

Compare the device details with official documentation from the operating-system provider or the device manufacturer. Look for a lifecycle page, a table of supported versions, an update notice or a security bulletin. Make sure the page concerns the same version, edition, model and region. A date mentioned in a forum or on a third-party website may be a useful clue, but it should not be the basis for a security decision. Check the source and the scope of the information before treating a date as applicable to your device.

For Apple products, the security releases page lists published updates and the systems they apply to; Apple’s iOS update documentation can also help you check changes available for that platform. On Android, security bulletins describe fixes published for parts of the ecosystem, but a general bulletin does not by itself certify that every individual phone has received them. Check the device manufacturer’s own information as well. A published correction and its delivery to a particular commercial model are related questions, but they are not the same confirmation.

The relevant authority depends on what you need to know. To find out what an operating-system update fixes, consult that system’s provider. To confirm whether a specific model is included and when it receives a patch, check the device manufacturer’s documentation or the guidance for its update channel. If the pages do not agree, do not assume that the device is covered. Look for a more specific notice or contact official support with the exact model and version in hand. That gives the support team the information needed to address your particular variant.

Support lifecycles do not always apply uniformly to everything carrying the same brand name. A version may have several editions, and some updates may be rolled out in stages or depend on a managed configuration. On phones, the model, carrier or market may affect the schedule. These differences explain why one person may see an update before another without, on their own, proving that either device has reached the end of support. A delay can have more than one explanation, so compare like with like before drawing conclusions.

On the official information page, look for the exact version name and any conditions limiting coverage: edition, channel, release date, supported model or region. Distinguish a date when an update becomes available from a date when service ends. Also check whether a notice concerns operating-system updates or another component, such as an app or service. Receiving app updates does not show that the operating system itself is still receiving security patches. Keep the component covered by the notice in view as you interpret its wording.

If the documentation uses unfamiliar terms, do not treat one label on its own as a guarantee. End of support, end of service and end of updates may have manufacturer-specific meanings. Read the definition alongside the date, and check whether it refers to new features, technical assistance, security fixes or a combination. The practical question is specific: is there a security release that applies to this version and device, and is the device still within the stated conditions? Answering that requires matching the identifiers, not just recognising a familiar product name.

Open the system update section and ask it to check for updates. If a newer version appears, record its number, date and any requirements shown. If there is no download ready, that does not prove support has ended: the update may not have rolled out yet, may be awaiting approval, or may not appear because of a connection, storage or configuration issue. Conversely, a device saying “up to date” confirms only that it is not showing a pending download at that moment; by itself, it does not certify the device’s support lifecycle. Treat the screen as one piece of evidence, not the whole answer.

Compare the result with the official source. Check the date of the latest applicable security update and look for a newer release for your version or model. For Apple, the security releases page is a reference for identifying published updates. For Android, security bulletins help identify project releases, although delivery to a device depends on its manufacturer and model. Confirm applicability through the appropriate official channel before concluding that an update is missing. A general announcement and an update visible on an individual device may not describe the same stage of distribution.

A useful check leaves a simple record: model, system and installed version; the official page consulted; the latest update that the page identifies as applicable; and the result of the check in Settings. If those details seem inconsistent, verify the edition and model again. The absence of a notification is not confirmation that support has ended. Recording what you checked and when makes it easier to separate a genuine support issue from a delay, a device-specific rollout or a setting that prevents the update from appearing.

If official documentation says your version no longer receives security fixes, consider how you use the device and which compatible alternatives are available. First find out whether the manufacturer allows a later version to be installed on that model. Check the requirements, available storage and update conditions in official documentation. Do not assume that changing a password, reinstalling the software or applying an update manually will restore support: the result must be a compatible version that is still covered. Confirm both compatibility and support status rather than relying on the installation process alone.

If there is no official update, options may include continuing to use the device with less exposure, installing another system only when the responsible manufacturer or project confirms compatibility, or replacing it. Which option makes sense depends on factors this guide cannot decide for you: required apps, peripherals, data, costs and risk tolerance. An alternative operating system is not automatically safer if it is not maintained or if it stops an essential part of your workflow from functioning. Consider the practical consequences as well as the stated support status.

While deciding, reduce exposure by keeping apps that are still supported up to date, avoiding software from doubtful sources and limiting sensitive tasks on a device whose coverage you cannot confirm. These steps do not replace operating-system patches. If you use the device for work, banking or other sensitive services, consult the recommendations of the relevant organisation or provider and consider an alternative with verifiable support. A careful decision does not require rushing, but it does require being clear about what is and is not confirmed.

Before installing a major update, make a backup and check that you can restore your files. Apple, for example, provides instructions for updating iPhone and iPad; follow the official guidance for your device and check any requirements it lists. On computers, use the instructions from the operating-system and device manufacturers, especially if the device is managed or contains specialist software. A backup is useful only if you know where it is and can access the files when needed, so verify that part rather than assuming the backup completed successfully.

Check compatibility with your apps and accessories, available storage and the device’s power supply. Read whether the update changes the major version or installs a security revision within the same version. After installation, return to Settings and record the resulting version. An interrupted installation or a download that remained pending does not show that the patch was applied. Check the version displayed after the process and, where necessary, compare it with the official release information for your device.

As a final checklist, keep four details: the full device identification, support status according to the official source, installed version and date of the latest check. If any of these has no clear answer, do not turn an assumption into certainty. Look for more specific documentation or contact the manufacturer’s support team before deciding that the device is protected or needs replacing. This record also helps make a later check quicker and more precise, because you can see exactly which model, version and support notice informed your decision.