> 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/1.1/reference/step-definitions/format-disk.md).
# Format disk
The Format disk step will partition and format the specified disk using the recommended Windows disk layout for UEFI devices.
{% hint style="info" %}
As of DeployR 1.1 this step also supports Legacy BIOS machines.
{% endhint %}
DeployR specifies partition sizes slightly larger than the recommended values to avoid servicing and backup issues that can occur when the partitions are too small. The default layout created by DeployR is:
* System partition. A 499MB partition formatted as FAT32, containing the UEFI files necessary to boot the operating system. (Note that larger sizes require additional free disk space to create a VSS snapshot, hence the 499MB default.)
* Microsoft Reserved partition. A 128MB reserved partition, managed by the Windows operating system.
* Windows partition. This NTFS-formatted partition holds the operating system, apps, data files, etc. for the Windows installation. The size of this partition is determined by subtracting the sizes of the other partitions from the total size on the disk specified.
* Recovery partition. This 1GB NTFS-formatted partition holds a Windows RE recovery image (winre.wim).
See the **Microsoft documentation** for more information.
---
# 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/1.1/reference/step-definitions/format-disk.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.
