> For the complete documentation index, see [llms.txt](https://documentation.2pintsoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.2pintsoftware.com/deployr/reference/step-definitions/apply-operating-system-from-cloud.md).

# Apply operating system from cloud

The **Apply operating system from cloud** step is similar in many ways to the **Apply operating system** step. Both steps apply a Windows image (`.wim` file), with an optional `unattend.xml` file, to the volume formatted as `S:` by the **Format disk** step. Unlike the **Apply operating system** step, this step can download the operating system directly from Windows Update.

<figure><img src="https://content.gitbook.com/content/8m0VARX9oyZ2zXWCdPgr/blobs/A4ADiODbo41UsPz6XQeE/image.png" alt=""><figcaption></figcaption></figure>

To select the image to apply, specify the operating system, version, language, edition, and architecture. The default version is **25H2**, and **26H2** is also available.

### Options

| Option                        | Description                                                                                                                                                                                                                      |
| ----------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Operating system              | **Windows 10** or **Windows 11**. Default: **Windows 11**.                                                                                                                                                                       |
| Operating system version      | 21H2, 22H2, 23H2, 24H2, 25H2, or 26H2. Default: **25H2**.                                                                                                                                                                        |
| Language code                 | Operating system language, from the list below. Default: `en-us`.                                                                                                                                                                |
| Operating system edition      | **Enterprise**, **Education**, **Professional**, or **Professional Workstation**. Default: **Enterprise**.                                                                                                                       |
| Operating system architecture | **x64** or **ARM64**. Default: **x64**.                                                                                                                                                                                          |
| Unattend.xml answer file      | Optional content item containing an `unattend.xml` file. Only used with the **Use provided unattend.xml** continuation method.                                                                                                   |
| Continuation method           | How the task sequence resumes in the new operating system. The choices are the same as for the [Apply operating system](/deployr/reference/step-definitions/apply-operating-system.md) step. Default: **Use SetupComplete.cmd**. |
| Disable Shift-F10             | Creates the `DisableCmdRequest.tag` file so that a command prompt cannot be opened with Shift-F10 during setup and OOBE. Default: `false`.                                                                                       |
| Require Internet              | Requires the device to have internet access during OOBE. Default: `false`.                                                                                                                                                       |

### OS language options available from the Cloud OS catalog

* `ar-sa`
* `bg-bg`
* `cs-cz`
* `da-dk`
* `de-de`
* `el-gr`
* `en-gb`
* `en-us`
* `es-es`
* `es-mx`
* `et-ee`
* `fi-fi`
* `fr-ca`
* `fr-fr`
* `he-il`
* `hr-hr`
* `hu-hu`
* `it-it`
* `ja-jp`
* `ko-kr`
* `lt-lt`
* `lv-lv`
* `nb-no`
* `nl-nl`
* `pl-pl`
* `pt-br`
* `pt-pt`
* `ro-ro`
* `ru-ru`
* `sk-sk`
* `sl-si`
* `sr-latn-rs`
* `sv-se`
* `th-th`
* `tr-tr`
* `uk-ua`
* `zh-cn`
* `zh-tw`


---

# 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://documentation.2pintsoftware.com/deployr/reference/step-definitions/apply-operating-system-from-cloud.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.