> For the complete documentation index, see [llms.txt](https://www.osdeploy.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.osdeploy.com/core-components/windows-components.md).

# Windows Components

Windows Components are optional Windows features that enable specific OSDeploy workflows on the build machine.

| Property       | Value                                                   |
| -------------- | ------------------------------------------------------- |
| Publisher      | Microsoft                                               |
| Platform       | Windows 11                                              |
| Architecture   | amd64 / arm64                                           |
| Install method | `Install-OSDeploySoftware` or Windows Optional Features |

{% embed url="<https://learn.microsoft.com/en-us/windows/client-management/client-tools/add-remove-hide-features>" %}

## Overview

Windows 11 ships with several features that are available but not enabled by default. OSDeploy uses **Hyper-V** to create and manage virtual machines on the build machine, enabling local testing of WinPE boot images without physical hardware. Enabling Windows optional features requires Administrator rights and may require a system restart.

## Why OSDeploy Uses Windows Components

* Hyper-V enables `New-OSDeployHyperVM` to create test VMs that boot from a WinPE image built by OSDeploy
* Local VM testing allows rapid iteration on boot images before deploying to physical devices
* Hyper-V is not required for building boot images — only for running them in a local VM

## In This Section

* [Hyper-V](/core-components/windows-components/hyper-v.md) — Enable the Hyper-V optional feature for VM-based boot media testing


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://www.osdeploy.com/core-components/windows-components.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.