> 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-ruo/instrumentation-miseq-ruo-troubleshooting-list/000003753.md).

# Troubleshooting Free Disk Space errors during Pre-run Checks on MiSeq

If available disk space is low, a message appears and will prevent run setup from proceeding. A total of 100 Gigabytes (GB) available is required on the D:\ drive to start a sequencing run. The warning message will indicate how much space is required to meet the minimum threshold.

**Troubleshooting steps:**

1. Minimize the MiSeq Control Software (MCS).
   1. For MCS v3.1 and below, select the **Minimize** in the top right corner of the control software window.
   2. For MCS 4.0 and above, select the dropdown menu in the top left corner, then select **Minimize Application**.
2. In the Windows Operating System (OS), open the **File Explorer** application and navigate to the `D:\Illumina` folder.
3. Run folders can be deleted from the following sub-folders:
   1. `D:\Illumina\MiSeqAnalysis`
   2. `D:\Illumina\MiSeqOutput`
   3. `D:\Illumina\MiSeqTemp`
4. The Windows **Recycle Bin** must be emptied before the Pre-Run checks can be performed again.

**Note:** Deleted files and folders **cannot be recovered** once they are deleted from the instrument. Make sure that all needed files are backed up off-instrument.

For persisting disk space warnings on MiSeq instruments running MCS v4.0 on Windows 10 only, see the following additional actions.

**Troubleshooting Persisting Disk Space warnings on MCS v4.0**

Illumina software will leverage three applications that run as Services to handle data analysis and copy to the output folder. If the instrument is configured to output data to the local D:\ drive, then these Services must be configured to login as Local System.

If these Services are not configured properly, MCS will often present one or both of the following warnings after updating the local user passwords.

![](https://761066130-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGM9W2DuBTgEXv1ClCm8H%2Fuploads%2Fgit-blob-b825f23504e6ec1cc45c404218ca287835e505f6%2Fimage1.jpg?alt=media\&token=7f66b42c-bdb0-4b61-b277-d8bf084737aa)

![](https://761066130-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGM9W2DuBTgEXv1ClCm8H%2Fuploads%2Fgit-blob-2d708dc906b48d25d437fc04446dc6d9653adc1f%2Fimage2.jpg?alt=media\&token=3ae98d3f-4851-43fb-a1e2-d2ab8181ca38)

If the warnings persist after following the steps above and sufficient space on the local D:\ drive is confirmed, use the following steps to continue troubleshooting this issue.

**Troubleshooting steps:**

1. Exit the MiSeq Control Software by selecting the dropdown menu in the top left corner and select **Exit Application**.
2. Open **Local Run Manager**.
3. Select **Tools**, then **System Settings**, then the **Service Accounts** tab.
4. Select the **Local System** radio button, and then select **Save.**
5. In the Update Service Account Confirmation popup, select **Continue.**
6. Restart the MiSeq Control Software and attempt run setup again.

\
\
\ <br>

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