> For the complete documentation index, see [llms.txt](https://knowledge.illumina.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.illumina.com/instrumentation/general/instrumentation-general-reference_material-list/000009668.md).

# Windows 10 support and timelines for Illumina sequencing and array instrument computers

Microsoft has announced that standard retail versions of Windows 10 will reach End of Life (EoL) in October 2025. **This does not apply to Illumina instruments**.

Illumina **does not support** upgrading sequencing or array instruments to Windows 11. Illumina will provide more information in the future about the process to upgrade the operating system (OS) of instruments prior to any OS End of Life.

Windows 10 versions and timeline information:

* **Sequencing instruments** running Windows — including iSeq 100, MiSeq, MiniSeq, NextSeq 500/550, and NovaSeq 6000 — run on Microsoft Windows 10 Enterprise LTSB (build 1607) with extended support through **October 13**, **2026** or Microsoft Windows 10 Enterprise LTSC (build 1809), with extended support through **January 09**, **2029**.
* **Array instruments** — iScan and Tecan EVO — run on Windows 10 1607 LTSB (x64), with extended support through **October 13**, **2026**.

For more information on timelines, see the following Microsoft resources.

**Note**: This information is not provided or curated by Illumina.

* [Windows 10 2016 LTSB support/lifecycle](https://learn.microsoft.com/en-us/lifecycle/products/windows-10-2016-ltsb)
* [Windows 10 Enterprise LTSC 2019 support/lifecycle](https://learn.microsoft.com/en-us/lifecycle/products/windows-10-enterprise-ltsc-2019)
* [Microsoft Fixed Lifecycle Policy](https://learn.microsoft.com/en-us/lifecycle/policies/fixed)

To identify the Windows 10 version is currently installed on an instrument, see Knowledge article [Operating System (OS) versions on Illumina platforms](/instrumentation/general/instrumentation-general-faq-list/000006353.md).

\
\
\ <br>

|                                                                                                                                                                                                                                                                                                                                                                        |
| :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: |
| *For any feedback or questions regarding this article (Illumina Knowledge Article #9668), contact Illumina Technical Support* [*techsupport@illumina.com*](mailto:techsupport@illumina.com?subject=Question%2FFeedback%20Regarding%20Illumina%20Knowledge%20Article%20#000009668%20-%20Instrumentation%20\&body=Dear%20Illumina%20Technical%20Support,%0D%0A%0D%0A)*.* |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://knowledge.illumina.com/instrumentation/general/instrumentation-general-reference_material-list/000009668.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.