> 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/osdeploy/invoke-osdeployhydration.md).

# Invoke-OSDeployHydration

Runs the complete OSDeploy workstation hydration workflow.

| Property | Value                                                                                   |
| -------- | --------------------------------------------------------------------------------------- |
| Module   | OSDeploy                                                                                |
| Platform | Windows 11 25H2 build 26200 or later (amd64 / arm64)                                    |
| Requires | PowerShell 7.6, `curl.exe`, OSDCloud, Administrator rights                              |
| Output   | Mixed child-command output: `PSCustomObject`, `FileInfo`, `DirectoryInfo`, and `String` |

## Syntax

```powershell
Invoke-OSDeployHydration [-Force] [-WhatIf] [-Confirm]
```

## Parameters

| Parameter  | Type     | Required | Description                                                                                                                                                                                |
| ---------- | -------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| `-Force`   | `Switch` | No       | Bypass hydration-level `ShouldContinue` prompts, install offered components, and forward force behavior to ESD and driver updates. It is not passed to CoreRE, Build, or Hyper-V creation. |
| `-WhatIf`  | `Switch` | No       | Preview delegated `ShouldProcess` operations. It does not suppress `ShouldContinue` prompts unless `-Force` is also used.                                                                  |
| `-Confirm` | `Switch` | No       | Flow confirmation preference into delegated commands.                                                                                                                                      |

## Examples

```powershell
Invoke-OSDeployHydration
```

```powershell
Invoke-OSDeployHydration -Force
```

## Workflow

The command validates the workstation, displays the planned workflow, and uses console Yes/No prompts unless `-Force` is supplied. It then:

1. Tests and optionally installs ADK 25H2, 7-Zip, Git, VS Code, VS Code Insiders, and Hyper-V.
2. Runs `Update-OSDeployCoreESD -Architecture $arch`.
3. Runs `Update-OSDeployCoreRE -Architecture $arch`.
4. Runs `Update-OSDeployCoreDrivers -Architecture $arch`.
5. Runs `Build-OSDeployBoot -Auto`.
6. On a physical host, optionally creates a Hyper-V VM when Hyper-V and the new ISO are available.

Hydration is the immediate-caller exception for child OSDeploy license gates. It does not use `Out-GridView` for its own confirmation prompts, and `-Force` does not guarantee that all delegated selectors or child confirmations are suppressed.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://www.osdeploy.com/command-reference/osdeploy/invoke-osdeployhydration.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.