> 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/miseq-i100-series/instrumentation-miseq-i100-series-troubleshooting-list/000010125.md).

# Troubleshooting “The loaded dry cartridge is not supported for sequencing” error on the MiSeq i100 Series

**Background**

MiSeq i100 Series instruments require Control Software v1.1 to run MiSeq i100 25M Reagent Kit (1000 cycles), as well as all MiSeq i100 Plus 50M and 100M Reagent Kits. The error “The loaded dry cartridge is not supported for sequencing. Load a compatible consumable for sequencing.” displays to users attempting to load one of these kits on a MiSeq i100 Series instrument with v1.0 control software installed.

![](https://761066130-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGM9W2DuBTgEXv1ClCm8H%2Fuploads%2Fgit-blob-9ce3aa40e36c7cf416e44dc965dab1dce35d0144%2Fimage1.png?alt=media)

**Troubleshooting Actions**

* Navigate to the **About** section of the MiSeq i100 Control Software to determine the control software version installed on the instrument.
* Upgrade the Control Software to version ≥1.1.x and restart the run setup.

MiSeq i100 Series Upgrade Software and release notes can be found in the [MiSeq i100 Series Support Page](https://support.illumina.com/sequencing/sequencing_instruments/miseq-i100-plus/downloads.html)

\
\
\ <br>

|                                                                                                                                                                                                                                                                                                                                                                         |
| :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: |
| *For any feedback or questions regarding this article (Illumina Knowledge Article #10125), contact Illumina Technical Support* [*techsupport@illumina.com*](mailto:techsupport@illumina.com?subject=Question%2FFeedback%20Regarding%20Illumina%20Knowledge%20Article%20#000010125%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/miseq-i100-series/instrumentation-miseq-i100-series-troubleshooting-list/000010125.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.
