> 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/genomestudio/microarray-genomestudio-troubleshooting-list/000005955.md).

# Troubleshooting the "Could not find a part of the path 'C:\Folder\Data\ad.bin" error in GenomeStudio Genotyping

The error "Could not find a part of the path 'C:\Folder\Data\ad.bin'" can occur when attempting to open a standalone GenomeStudio .bsc file if the accompanying Data folder is missing.

**Note:** The “Could not find a part of the path” error can occur in other situations. This article specifically addresses instances where the error message identifies the ad.bin file as part of the missing path.

The following image shows the correct parent folder structure for a GenomeStudio genotyping project.

The parent folder, which has the same name as the GenomeStudio project, contains the `.bsc` file and the accompanying Data and CNV folders.

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

**Figure 1.** Parent folder structure of a GenomeStudio Genotyping project.

The Data folder contains the necessary .bin files to open the GenomeStudio project.

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

**Figure 2.** Content of the Data folder of a GenomeStudio project.

When sharing a GenomeStudio project, share the entire parent folder rather than the `.bsc` file alone. The parent folder is named after the project and contains the `.bsc` file and the associated Data and CNV folders.

**Reference:**

[GenomeStudio Genotyping Introduction Support Webinar Video](https://knowledge.illumina.com/microarray/general/microarray-general-reference_material-list/000008070.md)

\
\
\ <br>

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