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

# How to troubleshoot The process cannot access the file error on MiSeq

"The process cannot access..." errors can occur when a file is being scanned by anti-virus software during the run, or when a communication issue occurs between the hardware and software.

* The run will often stop at the start of the next read. For example, if a virus scan is performed during Read 1, the run will stop at the start of Index Read 1.

**Error message:**

"The process cannot access the file 'D:\Illumina\MiSeqTemp\[RUNFOLDER]\Recipe\RunState.xml' because it is being used by another process."

![](https://761066130-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGM9W2DuBTgEXv1ClCm8H%2Fuploads%2Fgit-blob-90d0c22b9760ea2227aad88b6702bbba1e0fc70b%2Fimage1.png?alt=media\&token=61e87ab6-5686-4d95-9f68-9d9ae1862f5a)

**Troubleshooting steps:**

1. Determine if the run stopped or is paused.
   * For MiSeq Control Software (MCS) v4.0.0 and above this notification can show up during cluster generation steps and will not stop the run. Acknowledge the notification and the run will proceed.
2. If the run stopped:
   * Perform a Post-run wash.
   * Power cycle MiSeq (**Note**: if a run is in progress, it will not be able to be resumed). See instructions for [How to Power Cycle the MiSeq](https://knowledge.illumina.com/instrumentation/miseq-ruo/instrumentation-miseq-ruo-reference_material-list/000001894.md).
   * If the instrument initializes without error and no virus scan or Group Policy Objects (GPO) activity is enabled then proceed to setup the next run.
   * If a virus scan or GPO activity occurred, update the settings before the next run following the guidance provided below, or request that the settings be updated by the institutional internal IT department before setting up the next run.
     * [Illumina Control Computer Security Guide.](https://support.illumina.com/product-security-portal.html)
     * [MiSeq System Site Prep Guide](https://support.illumina.com/downloads/miseq_site_prep_guide_15027615.html) (see Networking).
   * If the error persists during the next run, contact [Illumina Technical Support](https://www.illumina.com/company/contact-us.html#/) for further assistance.

\
\
\ <br>

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