> 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/microarray/dragen-array/microarray-dragen-array-troubleshooting-list/000010205.md).

# Troubleshooting Windows Error: 0x80010135: Path too long when extracting DRAGEN Array Local zip file

The DRAGEN Array Windows CLI Installer is available from the [DRAGEN Array Software Downloads](https://support.illumina.com/array/array_software/dragen-array-secondary-analysis/downloads.html) page. Users may encounter the following error in Windows when attempting to extract the DRAGEN Array Local zip file.

An unexpected error is keeping you from copying the file. If you continue to receive this error, you can use the error code to search for help with this problem.

Error: 0x80010135: Path too long

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

Windows extracts files to a folder with the same name as the zip file by default.

The error occurs because the total file path is too long to extract with the default zipped folder name.

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

The recommended workaround is to extract to a folder with a shorter file path, which enables all files to be extracted successfully. See example below:

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

Once the files are extracted, the resulting subfolder will still retain the full zipped file name.

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

Shortening the zipped filename is not recommended. Retaining the full name is important for software traceability.

\
\
\ <br>

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