> For the complete documentation index, see [llms.txt](https://docs.verge.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verge.io/knowledge-base/virtual-machines/windows--slow-to-format-a-new-disk.md).

# Windows - Slow to Format a New Disk

How to fix slow virtual disk formatting in Windows Server 2012 and later by temporarily disabling SCSI TRIM and Unmap commands using fsutil.

Windows Server 2012 (and later) hosts will, by default, issue SCSI **TRIM** and **Unmap** commands equivalent to the entire size of the virtual disk. This behavior is the same even if the "Perform a quick format" option is checked, which significantly slows down the format process.

It is possible to disable the **SCSI TRIM** and **Unmap** feature on the host for the duration of the format.

## To Disable TRIM and Unmap

Using a Windows **CMD** window on the host, issue the following command:

```doscon
fsutil behavior set DisableDeleteNotify 1
```

## To Re-enable the Feature

Use the following command to re-enable the **Trim and Unmap** feature:

```doscon
fsutil behavior set DisableDeleteNotify 0
```

## To Verify the Current Setting

You can verify the current **Trim and Unmap** setting by issuing the following command:

```doscon
fsutil behavior query DisableDeleteNotify
```

The output will show one of the following:

* **DisableDeleteNotify=0** - The 'Trim and Unmap' feature is **on** (enabled).
* **DisableDeleteNotify=1** - The 'Trim and Unmap' feature is **off** (disabled).

{% hint style="info" %}
**Affected Versions**

* Only Windows Server 2012 and later hosts are affected. All earlier versions (e.g., Windows 2008) do not exhibit the same issue.
  {% endhint %}

{% hint style="info" %}
**Non-server Versions**

* Non-server versions of Windows (e.g., Windows 8.x and 10.x) do not support the **DisableDeleteNotify** parameter.
  {% endhint %}

***

{% hint style="info" %}
**Document Information**

* Last Updated: 2024-08-29
* VergeOS Version: 4.12.6
  {% endhint %}


---

# 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://docs.verge.io/knowledge-base/virtual-machines/windows--slow-to-format-a-new-disk.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.