> 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/000001658.md).

# How to access Windows on the MiSeq if there is black screen at boot up

If the MiSeq Control Software (MCS) does not launch at boot and a **black screen** is displayed, but the mouse is working, follow the steps below.

a. Press CTRL+ALT+DEL and open the **Task Manager**.

b. Select **New Task**.

![](/files/PVH1bYqRcC8MadtQvtnv)

c. Enter "explorer" into the text box and select **OK**.

![](/files/chZwjcF8ZtiIEstUyYwg)

d. Windows Explorer will boot up and bring you to the Windows desktop.\
e. **Launch** MCS by double-clicking the MiSeq Control Software icon on the desktop.\
f. If MCS stalls or initialization fails:

* **Quit** MCS if you have an error by acknowledging the error and closing the software.
* **Navigate** to D:\Illumina Maintenance Logs.
* **Rename** the "WashLog.xml" file to "WashLog\_archive.xml".
* **Re-launch** the MCS from the desktop.

If the issue still persists, contact [Illumina Technical Support](https://www.illumina.com/company/contact-us.html#/united-states/technical-support) for further assistance.

**Note:** If the message appears that "there is another application open," see the steps below to terminate duplicate instances of MCS.

a. In **Task Manager**, select the **Processes** tab.

![](/files/tqn9BiHKSo3H467m3Be6)

b. If "MiSeqSoftware.exe" is listed, **highlight** and select "**End Process**"

![](/files/f4OF2UByrCTvaxDPPjuC)

c. When prompted to confirm, select **End Process**.

![](/files/TvPnmEMBaMZCpwKqntvT)

d. Re-attempt launch of MCS from the desktop by double-clicking the MCS icon.

\
\
\ <br>

|                                                                                                                                                                                                                                                                                                                                                                        |
| :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: |
| *For any feedback or questions regarding this article (Illumina Knowledge Article #1658), contact Illumina Technical Support* [*techsupport@illumina.com*](mailto:techsupport@illumina.com?subject=Question%2FFeedback%20Regarding%20Illumina%20Knowledge%20Article%20#000001658%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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://knowledge.illumina.com/instrumentation/miseq-ruo/instrumentation-miseq-ruo-troubleshooting-list/000001658.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
