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

# Apply FFU

{% hint style="info" %}
This is only supported in DeployR Enterprise. Applies to: DeployR 1.4 and later.
{% endhint %}

The **Apply FFU** step writes a Full Flash Update (`.ffu`) image directly to the specified disk. An FFU image contains the entire disk layout, including the EFI, MSR, Windows, and recovery partitions, so this step replaces both the **Format disk** and **Apply operating system** steps. Applying a sector-based FFU image is typically much faster than applying a file-based WIM image.

After the image is applied, the step assigns the `S:` drive letter to the Windows partition (the same convention used by **Format disk**), moves the DeployR state onto that drive, and configures the selected continuation method so that the task sequence resumes in the new operating system.

### Options

| Option                   | Description                                                                                                                                                                                                                      |
| ------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Operating system image   | Content item containing the FFU file. To create one from an existing WIM, see [Creating FFU images](/deployr/content-management/creating-ffu-images.md).                                                                         |
| Disk index               | Number of the disk that the image is written to. Default: `0`.                                                                                                                                                                   |
| Unattend.xml answer file | Optional content item containing an `unattend.xml` file. Only used when the continuation method is **Use provided unattend.xml**.                                                                                                |
| 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 OOBE. Default: `false`.                                                                                                 |
| Require Internet         | Requires the device to have internet access during OOBE. Default: `false`.                                                                                                                                                       |

If **Use provided unattend.xml** is selected but no answer file is specified, the step uses **Use SetupComplete.cmd** instead.

### Sector size

An FFU image can only be applied to a disk with the same logical sector size as the disk it was captured from. Disks with 512-byte sectors and disks with 4096-byte (4K native) sectors need separate images. To support both types of hardware with one task sequence:

1. Add a [Detect disk sector size](/deployr/reference/step-definitions/detect-disk-sector-size.md) step before the **Apply FFU** steps. It sets the `DISK0SECTORSIZE` variable (for disk 0).
2. Add two **Apply FFU** steps, one with the 512-byte image and one with the 4K image.
3. Add a condition to each one, for example `DISK0SectorSize` equals `512` and `DISK0SectorSize` equals `4096`.

The [Windows bare metal with FFU](/deployr/task-sequences/task-sequence-templates/windows-bare-metal-with-ffu.md) template is already set up this way.

### Notes

* When running from standalone media, the image is read from the media. Otherwise it is streamed from the DeployR server straight onto the disk, so no local copy of the image is needed; BranchCache peering is not used for FFU images.
* Because the FFU defines the partition layout, do not add a **Format disk** step before this step.


---

# 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-ffu.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.