> For the complete documentation index, see [llms.txt](https://docs.foundryosd.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.foundryosd.com/start-here/requirements.md).

# Requirements

Foundry needs a Windows workstation to create the deployment media, the media itself, and a target device that can start from it. This page lists what each one must provide.

## Administrator workstation

| Requirement                       | Detail                                                                                                                                                                                                      |
| --------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Windows                           | Windows 10 or Windows 11, on an x64 or ARM64 processor. See [Supported versions](/reference/supported-versions.md).                                                                                         |
| Administrator rights              | Foundry OSD always runs elevated. Windows shows a UAC prompt at every start, and an account that cannot approve it cannot open the app.                                                                     |
| Free disk space                   | At least 20 GB free on the Windows system drive, and on the drive of the ISO file when you create an ISO. Foundry OSD checks this before it builds media.                                                   |
| Windows ADK and Windows PE add-on | A supported version of both. Foundry OSD installs them for you from its [ADK](/foundry-osd/adk.md) page; the accepted versions are in [Supported versions](/reference/supported-versions.md#windows-adk).   |
| Microsoft runtimes                | .NET 10 Desktop Runtime, Microsoft Edge WebView2 Runtime and Microsoft Visual C++ Redistributable 14.4. See [Download and install](/start-here/download.md#install-foundry-osd) for how they are installed. |
| Internet access                   | To GitHub and Microsoft download sites, directly or through a proxy. See [Network endpoints](/reference/network-endpoints.md).                                                                              |

## Deployment media

Choose one output, or both:

| Output    | Requirement                                                                                                                                     |
| --------- | ----------------------------------------------------------------------------------------------------------------------------------------------- |
| USB drive | 16 GB or larger; a drive sold as 16 GB is accepted. Foundry OSD refuses a smaller drive. Creating the media erases the drive.                   |
| ISO file  | A destination with at least 20 GB free. Use it for virtual machines, remote management consoles or [PXE](/foundry-osd/media/pxe-deployment.md). |

[Start: create deployment media](/foundry-osd/media.md) explains what each output carries.

## Target device

| Requirement        | Detail                                                                                                                                                                                                                                                   |
| ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Architecture       | x64 or ARM64, the same as the media. You choose the media architecture in [General](/foundry-osd/general.md).                                                                                                                                            |
| Firmware           | UEFI. Foundry Deploy converts the disk to GPT and sets Windows up for UEFI start only. On a device that starts in legacy BIOS (CSM) mode, or a generation 1 virtual machine, the deployment stops before the disk is erased.                             |
| Windows to install | Windows 11. The releases and editions offered are in [Supported versions](/reference/supported-versions.md); to install another image, see [Custom Windows images](/foundry-osd/customization/custom-windows-images.md).                                 |
| Network            | Internet access from Windows PE to the hosts in [Network endpoints](/reference/network-endpoints.md). Ethernet is the simplest choice; Wi-Fi works when you enable it in [Network](/foundry-osd/network.md) and Windows PE has a driver for the adapter. |
| Disk               | A disk that can be erased. Foundry Deploy erases the disk the technician selects.                                                                                                                                                                        |

## Optional features

Each feature has its own prerequisites, listed on its page:

* [Windows Autopilot](/foundry-osd/autopilot.md): a Microsoft Entra tenant with Microsoft Intune, and rights that depend on the method you choose.
* [Domain Join](/foundry-osd/domain-join.md): an Active Directory domain that the device can reach after the restart, and a join account allowed to join computers.

Next: [Download and install](/start-here/download.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://docs.foundryosd.com/start-here/requirements.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.
