> 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/requirements.md).

# PC Requirements

Prepare a Windows 11 PC with the software required to build OSDeploy boot media.

Prepare a Windows 11 workstation with PowerShell 7, Hyper-V, and the modules required to create and test OSDeploy boot media.

{% hint style="warning" %}
Do not use the default WinGet command to install PowerShell. Beginning with PowerShell 7.6.0, WinGet installs the unsupported MSIX package by default. Install PowerShell from the MSI package.
{% endhint %}

## Complete the Setup

{% stepper %}
{% step %}

### Confirm the Requirements

Use a PC with:

* Windows 11 25H2, build 26200 or later
* amd64 architecture
* Local administrative rights
* At least 50 GB of free space on the system volume
* Internet access

Windows 11 on arm64 can potentially be used, but it is not fully tested. Other Windows client versions and Windows Server are unsupported.
{% endstep %}

{% step %}

### Update Windows and Enable Hyper-V

Open Windows PowerShell as an administrator, open Windows Update, and install all available cumulative updates:

```powershell
Start-Process 'ms-settings:windowsupdate'
```

On a physical Windows 11 Pro, Enterprise, or Education PC with hardware virtualization enabled, enable Hyper-V:

```powershell
Enable-WindowsOptionalFeature -Online -FeatureName 'Microsoft-Hyper-V-All' -All -NoRestart
```

Restart Windows before continuing.
{% endstep %}

{% step %}

### Install PowerShell 7

Download the latest stable amd64 or arm64 `.msi` from [PowerShell releases](https://github.com/PowerShell/PowerShell/releases/latest). Run the MSI and enable the recommended installation options, including adding PowerShell to `PATH` and enabling Microsoft Update.

Open PowerShell 7 as an administrator by running `pwsh`. Confirm that the session uses PowerShell Core 7.6 or later and that `$PSHOME` is under `$env:ProgramFiles\PowerShell\7`:

```powershell
$PSVersionTable | Select-Object PSEdition, PSVersion
$PSHOME
```

{% endstep %}

{% step %}

### Install the Required Modules

Install `OSDeploy` and `OSDCloud` from the elevated PowerShell 7 session:

```powershell
Install-Module -Name OSDeploy -Force -SkipPublisherCheck
Install-Module -Name OSDCloud -Force -SkipPublisherCheck
```

Install `OSD` only when a workflow requires legacy OSD or OSDCloud v1 commands.
{% endstep %}

{% step %}

### Register the OSDeploy PC

Complete [Community Registration](/guide/registration.md) before directly running a gated update command. Confirm that `Show-OSDeployLicense` returns a valid Recast Software Community License.

The current shared gate applies to `Update-OSDeployBootISO`, `Update-OSDeployBootProfilePreview`, `Update-OSDeployCore`, `Update-OSDeployCoreDrivers`, `Update-OSDeployCoreESD`, and `Update-OSDeployCoreRE`. Core updates invoked immediately by `Invoke-OSDeployHydration` use its limited caller exception.
{% endstep %}
{% endstepper %}

See the detailed instructions for [Windows 11](/guide/requirements/windows-11-os.md), [PowerShell 7](/guide/requirements/powershell-7.md), and [PowerShell modules](/guide/requirements/powershell-modules.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 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/guide/requirements.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.