> 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/guide/quick-setup.md).

# Quick Setup

Prepare an OSDeploy workstation and create Hydra boot media with Invoke-OSDeployHydration.

Use `Invoke-OSDeployHydration` to prepare an OSDeploy workstation, download current Windows and WinPE driver content, and create OSDCloud boot media.

<figure><img src="https://3996045416-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LDKRxGiKLYjW1gana2O%2Fuploads%2FS5O0VdoILtV05bghRkpR%2Fimage.png?alt=media&amp;token=11be3b4e-d7b8-422c-8c5f-7ebf01601f5d" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
Hydration installs software, downloads Windows and driver content, and creates boot media under `C:\ProgramData\OSDeployCore`. If Hydration enables Hyper-V, restart Windows before creating a test VM.
{% endhint %}

## Run Hydration

{% stepper %}
{% step %}

### Confirm the Requirements

Use a workstation with:

* Windows 11 25H2 build 26200 or Windows 11 26H2 build 26300
* PowerShell 7.6 or later installed from the MSI package
* Current [OSDeploy module](https://www.osdeploy.com/guide/requirements/powershell-modules.md)
* OSDCloud module version `26.5.24.1` or later
* Windows ADK `10.1.26100.2454` or `10.1.26100.9457` for boot-image builds and OS image selection; Hydration offers ADK 26H2 when no ADK is installed
* A Recast Software Community License is recommended for direct use of gated update commands; the Core update commands invoked by Hydration use its immediate-caller exception
* Administrator rights
* `curl.exe` available in `PATH`

Open PowerShell 7.6 as an administrator before continuing.
{% endstep %}

{% step %}

### Run Hydration

Run the interactive workflow from the elevated PowerShell 7.6 session:

```powershell
Invoke-OSDeployHydration
```

Review the workflow and continue. Approve the Windows ADK 26H2 and 7-Zip installations when prompted; declining either required component stops Hydration. Choose whether to install the optional Git, Visual Studio Code, Visual Studio Code Insiders, and Hyper-V components.

Complete any content and wallpaper selections. Hydration detects the workstation architecture, prepares matching Windows and WinPE driver content, and creates Hydra boot media under `C:\ProgramData\OSDeployCore\boot`. On a physical workstation with Hyper-V enabled, it can also create a VM and boot the generated ISO.
{% endstep %}
{% endstepper %}

For `-Force`, `-WhatIf`, workflow details, and returned objects, see [Invoke-OSDeployHydration](https://www.osdeploy.com/guide/cmdlets/invoke-osdeployhydration.md). For compact syntax and parameter definitions, see the [Invoke-OSDeployHydration command reference](https://www.osdeploy.com/command-reference/osdeploy/invoke-osdeployhydration.md).


---

# 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/guide/quick-setup.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.
