> 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/deployment-methods/generate-windows-pe-boot-images/generating-usb-flash-media.md).

# Generating USB Flash Media

Create bootable DeployR USB media from the generated WinPE ISO.

### Before you begin

You need:

* A USB flash drive.
* Access to the DeployR Content `Boot` folder.
* The `DeployR_x64_noprompt.iso` file from that folder.

{% hint style="danger" %}
This process permanently erases the selected USB drive. Confirm the disk number and size before running `clean`.
{% endhint %}

### Prepare the flash drive

1. Insert the USB flash drive.
2. Open PowerShell or Command Prompt as an administrator.
3. Start DiskPart:

```
diskpart
```

4. List the available disks:

```
list disk
```

5. Select the USB drive. Replace `1` with the correct disk number.

```
select disk 1
```

6. Clean, partition, format, and assign the drive:

```
clean
create partition primary
select partition 1
format fs=fat32 quick LABEL="DeployR"
assign
exit
```

The flash drive is now ready for the WinPE media.

### Copy the DeployR WinPE media

1. Open the DeployR Content `Boot` folder.
2. Locate `DeployR_x64_noprompt.iso`.
3. Mount or extract the ISO file.
4. Copy its contents to the root of the prepared flash drive.

In this example, the ISO is mounted as `D:`. Its contents are copied to USB drive `E:`.

Keep the ISO folder structure intact. Do not copy the ISO file itself. The flash drive must contain the extracted boot files.


---

# 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/deployment-methods/generate-windows-pe-boot-images/generating-usb-flash-media.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.