> 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/task-sequences/task-sequence-templates/windows-bare-metal-with-ffu.md).

# Windows bare metal with FFU

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

The **Windows bare metal with FFU** template deploys Windows from a Full Flash Update (`.ffu`) image instead of a WIM. An FFU contains the complete disk layout, so the template has no **Format disk** step. The [Apply FFU](/deployr/reference/step-definitions/apply-ffu.md) step writes the image straight to disk 0.

The template contains these steps:

* **Windows PE**
  * **Set Windows settings**
  * **Detect disk sector size**: sets `DISK0SECTORSIZE` for disk 0.
  * **Apply FFU**: runs when `DISK0SectorSize` equals `512`.
  * **Apply FFU 4K**: runs when `DISK0SectorSize` equals `4096`.
  * **Inject drivers**
  * **Prepare OS**
  * **Reboot**
* **Full OS**
  * **Configure new OS**
  * **Enable BitLocker**
  * **Enable BranchCache**
  * **Enable Administrator account**

After creating a task sequence from this template, edit both **Apply FFU** steps to select the FFU content items: one captured from a disk with 512-byte sectors and one captured from a 4K native disk. An FFU can only be applied to a disk with the same sector size as the disk it was captured from. If all of your devices use the same type of disk, you can disable or delete the step you do not need.

As with the other bare metal templates, consider adding an **Offline domain join** step, or set a password for the Administrator account, so that you can sign in to the new operating system.


---

# 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/task-sequences/task-sequence-templates/windows-bare-metal-with-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.