> 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/guide/basic/new-osdeployhypervm.md).

# Test a Boot ISO

Create a Hyper-V virtual machine for testing OSDeploy boot media.

Use `New-OSDeployHyperVM` to create and start a Hyper-V virtual machine for testing OSDeploy boot media. The function creates the virtual disk, attaches the newest OSDeploy boot ISO, configures the VM, creates an initial checkpoint, and opens the Hyper-V console when VMConnect is available.

## Create the Virtual Machine

{% stepper %}
{% step %}

### Confirm the Requirements

Run the function on a physical computer that meets these requirements:

* Windows 11 25H2 build 26200 or later
* PowerShell 7.6 or later installed from the MSI package
* Current [OSDeploy module](/guide/requirements/powershell-modules.md)
* [Microsoft Hyper-V](/guide/cmdlets/install-osdeploysoftware/microsoft-hyper-v.md) and the Hyper-V PowerShell tools
* Administrator rights
* `curl.exe` available in `PATH`
* Enough processor, memory, and storage capacity for the VM

{% hint style="warning" %}
Restart Windows after enabling Hyper-V. `New-OSDeployHyperVM` stops when Hyper-V is pending a restart, and it cannot run inside another virtual machine.
{% endhint %}
{% endstep %}

{% step %}

### Create the VM

Open an elevated PowerShell 7.6 session and run the function without parameters:

```powershell
New-OSDeployHyperVM
```

The default command creates a timestamp-named Generation 2 VM similar to `260829-143000 OSDeploy` with this configuration:

| Setting              | Default            |
| -------------------- | ------------------ |
| Virtual processors   | 2                  |
| Startup memory       | 8 GB, fixed        |
| Virtual disk         | 64 GB VHDX         |
| Display resolution   | `1600x900`         |
| Secure Boot template | `MicrosoftWindows` |
| Initial checkpoint   | Enabled            |
| Start VM             | Enabled            |

{% hint style="info" %}
OSDeploy recommends at least 2 virtual processors and 12 GB of startup memory for smoother deployment work. Use 12 GB only when the physical host has enough memory for both Windows and the VM. The function default remains 8 GB.
{% endhint %}

The function selects the newest `bootmedia.iso` under `C:\ProgramData\OSDeployCore\boot`. It prefers `Default Switch`, then the first available Hyper-V switch, and finally creates the VM without networking when no switch exists. It creates the VHDX in the Hyper-V host's default location, mounts the ISO, configures firmware and available TPM security, creates the checkpoint, opens VMConnect, and starts the VM.

{% hint style="warning" %}
A VM created with an empty DVD drive does not have OSDeploy boot media to start. Attach an ISO before starting or restarting the VM.
{% endhint %}
{% endstep %}
{% endstepper %}

For sizing, media, networking, firmware, checkpoint, and startup examples, see [New-OSDeployHyperVM](/guide/cmdlets/new-osdeployhypervm.md). For compact syntax and parameter definitions, see the [command reference](/command-reference/osdeploy/new-osdeployhypervm.md).


---

# 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/guide/basic/new-osdeployhypervm.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.