> 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/capture-image.md).
# Capture image
After preparing a Windows operating system for capture by running `sysprep.exe /generalize /oobe`, boot the device into Windows PE. The **Capture image** step captures the Windows image (`.wim` file) and automatically uploads it to the specified operating system content item.
The **Create a new version** checkbox creates a new content item version each time the **Capture image** step runs. If the checkbox is not selected, the captured OS image overwrites the selected content item version.
### Options
| Option | Description |
| ---------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- |
| WIM file name | Name of the captured image file. Default: `Windows.wim`. |
| Upload to content item | Operating system content item (and version) to upload the image to. If not specified, the image is only saved on the device. |
| Create a new version | Creates a new version of the content item, with a status of **In development**, instead of replacing the files in the selected version. Default: `false`. |
| Capture image to a custom location | Folder to save the image to before it is uploaded. Default: the `Capture` folder under the DeployR root folder (`_2P\Capture` on the Windows drive). |
Each NTFS volume with a drive letter is captured as a separate image in the WIM file. To upload the image, the content item must allow writes (the **Write** flag).
---
# 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/capture-image.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.
