> 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/foundry-osd/customization/operating-system.md).

# OS selection

**OS selection** limits the Windows versions, languages, license channels and editions that Foundry Deploy offers the technician, and chooses which ones are selected by default. Leave the page off to offer everything the Foundry catalog contains.

<figure><img src="https://64695594-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdn0pr5zia6oG2DU1R1Pn%2Fuploads%2Fgit-blob-ec3776972a485f2584e845fda4b6efdae6c0a06f%2Ffoundry-osd-customization-operating-system-01-selection.png?alt=media" alt="OS selection page enabled with the Windows version and Windows edition groups expanded, and the Windows language and Windows license channel groups collapsed"><figcaption><p>Each group limits what the technician can choose in Foundry Deploy and sets what is preselected.</p></figcaption></figure>

## Configure the Windows choices

1. Open **Customization > OS selection**.
2. Turn the switch at the top right to **Enabled**. Until you do, every control is unavailable and the media carries no restriction. On **Start**, **OS selection** now shows **Configured**.
3. Expand a group and tick the values the technician may choose.
4. In the **Preselected ...** box of the same group, choose the value selected by default, or keep **Automatic**.
5. Create or update the deployment media.

| Group                       | Allowed values                                                                                                                               | Default value                                                            |
| --------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------ |
| **Windows version**         | **Available Windows versions**: 26H2, 25H2, 24H2                                                                                             | **Preselected Windows version** and **Preselected Windows update level** |
| **Windows language**        | **Available Windows languages**                                                                                                              | **Preselected Windows language**                                         |
| **Windows license channel** | **Available Windows license channels**: Retail, Volume                                                                                       | **Preselected Windows license channel**                                  |
| **Windows edition**         | **Available Windows editions**: Home, Home N, Home Single Language, Home China, Education, Education N, Pro, Pro N, Enterprise, Enterprise N | **Preselected Windows edition**                                          |

Three rules apply to every group:

* **An empty list means all.** A list with nothing ticked offers every supported value.
* **A single value forces the default.** When exactly one value is ticked, it becomes the preselected value and the **Preselected ...** box of that group is locked, except **Preselected Windows update level**. Foundry Deploy locks that list too.
* **Automatic** leaves the choice to Foundry: version 26H2, edition Pro, license channel Retail. For the language, Foundry Deploy chooses on the device: see [Select Windows](/foundry-deploy/operating-system.md).

### Preselected Windows update level

Each Windows version is published as several monthly builds. **Preselected Windows update level** chooses the build selected by default: **Latest available update**, **Updates behind latest: 1**, and so on up to **Updates behind latest: 11**. If the catalog holds fewer builds than you asked for, the oldest one is selected. The technician can still pick another build.

### Editions and license channels depend on each other

Home editions exist only in the Retail channel and Enterprise editions only in the Volume channel. Pro and Education exist in both. Foundry OSD keeps the two lists consistent as you tick editions:

* A channel that none of the ticked editions supports is cleared and locked.
* A channel that a ticked edition requires is locked. If you had ticked a channel yourself, Foundry OSD also ticks the required one: ticking **Enterprise** adds **Volume**.

To change a locked channel, change the ticked editions first.

## What the technician sees

On the **Operating system** step of Foundry Deploy, each list contains only the values you allowed, with your preselected value selected.

A restriction is dropped when it cannot be met. If none of the allowed values of a list exists in the catalog for the device, for example an allowed version that is no longer published or a language missing for the selected build, Foundry Deploy offers every available value for that list and records a warning in its log. This fallback applies in the same way to versions, languages, editions and license channels. See [Select Windows](/foundry-deploy/operating-system.md).

## Limits

* This page restricts the images of the Foundry catalog only. It does not filter [Custom Windows images](/foundry-osd/customization/custom-windows-images.md).
* Foundry deploys Windows 11 24H2, 25H2 and 26H2. See [Supported versions](/reference/supported-versions.md).
* The versions and editions ticked here also set the availability labels on [Optional features](/foundry-osd/customization/optional-features.md).

## Related

* [Select Windows](/foundry-deploy/operating-system.md)
* [Catalogs](/reference/catalog.md)
* [Windows deployment troubleshooting](/troubleshooting/deployment.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/foundry-osd/customization/operating-system.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.
