> 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/content-management/operating-system.md).
# Operating system
First, create an operating system content item:
Next, open the content item's details page and click **+ New Version** to create an operating system version.
Click **Choose File**, browse to your WIM file, and click **Open**.
Click **Upload All** to upload the file.
### Accepted File Types
DeployR originally supported OS WIM files, but it is now also possible to use an ISO. When an ISO is uploaded as an operating system content item, the **Apply operating system** step or script mounts the ISO in Windows PE and uses `sources\install.wim`.
### Troubleshooting during Task Sequence
The most common issues during this step are caused by setting the content type to **Folder** instead of **Single File**. During the Task Sequence, this will result in the following error:
```
Applying image s:\_2P\content\%WIMContentItemGUID%\ index 1 to path S:\
ERROR: Value does not fall within the expected range.
```
During a successful deployment, the log shows the file being applied:
```
Applying image s:\_2P\content\%WIMContentItemGUID%\ index 1 to path S:\
```
Other times, the index number does not exist in the WIM. For example, you are trying to apply index 5, which is typically Pro, but the WIM you are using has only one index because it was modified before import.
Issues can also be caused by too little memory. This happens most often on virtual machines with less than 4 GB allocated, or when Dynamic Memory is enabled.
---
# 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/content-management/operating-system.md?ask=&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.
