> For the complete documentation index, see [llms.txt](https://www.osdeploy.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.osdeploy.com/command-reference/osd/get-osdcorecacheusbpath.md).

# Get-OSDCoreCacheUSBPath

Returns OSDCloud cache paths located on USB drives.

| Property | Value                 |
| -------- | --------------------- |
| Module   | OSD                   |
| Platform | WinPE (amd64 / arm64) |

## Description

Uses Get-OSDCoreCacheDrive to enumerate OSDCloud cache drives and returns the OSDCloud directory path for each discovered cache drive where USB is true, the file system is NTFS or exFAT, and more than the specified free space is available.

## Syntax

```powershell
Get-OSDCoreCacheUSBPath [[-Include] <String[]>] [[-Exclude] <String[]>] [[-SizeRemaining] <Int32>]
 [-ProgressAction <ActionPreference>] [<CommonParameters>]
```

## Parameters

| Parameter        | Type       | Required | Description                                                                                                                                                                                            |
| ---------------- | ---------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| `-Include`       | `String[]` | False    | Optional list of drive letters to include when searching for OSDCloud cache drives. Accepts values such as 'C', 'D:', or 'E:'. When omitted, all mounted file system drive letters are considered.     |
| `-Exclude`       | `String[]` | False    | Optional list of drive letters to exclude when searching for OSDCloud cache drives. Accepts values such as 'C', 'D:', or 'E:'. Excluded drives are skipped even when they are also present in Include. |
| `-SizeRemaining` | `Int32`    | False    | Optional minimum free space required on the USB cache drive, in GB. The default is 10 GB.                                                                                                              |

## Examples

### Example

```powershell
Get-OSDCoreCacheUSBPath
```

Returns OSDCloud directory paths for all discovered USB cache drives with more than 10 GB free and an NTFS or exFAT file system.

### Example

```powershell
Get-OSDCoreCacheUSBPath -Include D
```

Returns the OSDCloud directory path when drive D contains an OSDCloud cache path, is a USB drive, has more than 10 GB free, and is formatted NTFS or exFAT.

### Example

```powershell
Get-OSDCoreCacheUSBPath -SizeRemaining 20
```

Returns OSDCloud directory paths for discovered USB cache drives with more than 20 GB free and an NTFS or exFAT file system.

## Related

* <https://github.com/OSDeploy/OSD/tree/master/docs>


---

# 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://www.osdeploy.com/command-reference/osd/get-osdcorecacheusbpath.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.
