> 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/creating-ffu-images.md).

# Creating FFU images

{% hint style="info" %}
Applies to: DeployR 1.4 and later. FFU deployment requires DeployR Enterprise.
{% endhint %}

The [Apply FFU](/deployr/reference/step-definitions/apply-ffu.md) step deploys Windows from a Full Flash Update (`.ffu`) image. You can create the FFU from an existing operating system content item (a WIM) with the `ConvertTo-DeployRFFU` command in the `DeployR.Utility` module. The command creates a new content item for the FFU and leaves the original content item unchanged.

### Requirements

* Run the command on the DeployR server, in an elevated PowerShell 7 session, after importing the module and running `Connect-DeployR`.
* The Hyper-V role and its PowerShell module must be installed on the server, because the image is built in a temporary VHDX: `Install-WindowsFeature Hyper-V -IncludeManagementTools -Restart`.
* Free disk space of roughly 8 times the size of the WIM, on the volume that holds the DeployR content `TEMP` folder (and `%TEMP%`, which DISM uses for scratch space).

### Creating the FFU

```powershell
Import-Module 'C:\Program Files\2Pint Software\DeployR\Client\PSModules\DeployR.Utility'
Connect-DeployR

# Create an FFU for disks with 512-byte sectors from the latest version of the content item, image index 3
ConvertTo-DeployRFFU -Id 6d2f8a43-0c7e-4b8e-9d61-2f0f3c5a7e11 -Index 3

# Create a second FFU for 4K native disks
ConvertTo-DeployRFFU -Id 6d2f8a43-0c7e-4b8e-9d61-2f0f3c5a7e11 -Index 3 -LogicalSectorSize 4096
```

You can also pipe content items to the command, for example `Get-DeployROperatingSystem | Where-Object name -like "*25H2*" | ConvertTo-DeployRFFU -Index 3`.

| Parameter            | Description                                                                                                                                                                                  |
| -------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `-Id`                | ID of the operating system content item containing the WIM. You can also pipe content items to the command.                                                                                  |
| `-Version`           | Content item version to convert. Default: the latest version.                                                                                                                                |
| `-Index`             | Index of the image in the WIM. Default: `1`. Use `Get-WindowsImage` on the WIM to list the editions and their indexes.                                                                       |
| `-SizeBytes`         | Size of the virtual disk the image is built on. Default: 64 GB. When deployed, the partitions are extended to fill the target disk, so this only needs to be large enough to hold the image. |
| `-LogicalSectorSize` | `512` (default) or `4096`. An FFU can only be applied to a disk with the same sector size, so create one of each if you have both kinds of disks.                                            |

### What the command does

1. Downloads the WIM from the content item to the DeployR content `TEMP` folder.
2. Creates a VHDX with the requested sector size and partitions it the way Microsoft recommends for FFUs: EFI system partition, MSR, Windows, and recovery.
3. Applies the image and makes it bootable with `bcdboot`.
4. Captures the VHDX with `DISM /Capture-FFU`, then shrinks it with `DISM /Optimize-FFU`.
5. Uploads the result as a new, active content item named after the original, for example **Windows 11 Enterprise (FFU)** or **Windows 11 Enterprise (FFU 4Kn)** for 4K images, and returns it.

Temporary files are deleted as the command goes, and when it finishes or fails. The process can take a long time for large images.

Select the new content items in the **Apply FFU** steps of your task sequence. The [Windows bare metal with FFU](/deployr/task-sequences/task-sequence-templates/windows-bare-metal-with-ffu.md) template has a step for each sector size.


---

# 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/creating-ffu-images.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.