> 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-windowsadkpaths.md).

# Get-WindowsAdkPaths

Retrieves the command paths of the Windows Assessment and Deployment Kit (ADK).

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

## Description

Retrieves the command paths of the Windows Assessment and Deployment Kit (ADK).

## Syntax

```powershell
Get-WindowsAdkPaths [[-Architecture] <String>] [[-WindowsAdkRoot] <Object>]
 [-ProgressAction <ActionPreference>] [<CommonParameters>]
```

## Parameters

| Parameter         | Type     | Required | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
| ----------------- | -------- | -------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `-Architecture`   | `String` | False    | Windows ADK architecture to get. Valid values are 'amd64', 'x86', and 'arm64'.                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
| `-WindowsAdkRoot` | `Object` | False    | Path to the Windows ADK root directory. Typically 'C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit' \[ValidateScript({ if (!($\_ \| Test-Path)) { throw 'Path does not exist' } if (!($\_ \| Test-Path -PathType Container)) { throw 'Path must be a directory' } if (!(Test-Path "$*\Deployment Tools")) { throw 'Path does not contain a Deployment Tools directory' } if (!(Test-Path "$*\Windows Preinstallation Environment")) { throw 'Path does not contain a Windows Preinstallation Environment directory' } return $true })] |

## Examples

No examples provided in source documentation.


---

# 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-windowsadkpaths.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.
