# Create a Windows Virtual Machine from an ISO

## Overview

This guide outlines the process of deploying a Windows virtual machine (VM) directly from an ISO using <code class="expression">space.vars.product\_name</code>. Traditionally, Windows VMs required manual installation outside the cloud environment, followed by conversion and uploading of the disk image. This streamlined approach eliminates those steps by allowing users to install Windows directly from an ISO, configure necessary drivers, and create a reusable "golden image" for future deployments. By following this guide, you can simplify Windows VM provisioning within <code class="expression">space.vars.product\_acronym</code> while ensuring consistency and efficiency across deployments.

***

## Prerequisites

* <code class="expression">space.vars.product\_name</code> **Environment:**
  * Access to <code class="expression">space.vars.product\_acronym</code> environment with Block Storage configured.
  * Appropriate permissions to create images, volumes, and virtual machines.
* **Command Line Tools:**
  * [Pcdctl Command Line](/private-cloud-director/2025.7/reference/pcdctl-command-line.md) or [OpenStack CLI](https://docs.openstack.org/python-openstackclient/2023.1/) version 6.3.0 or greater
* **Required Files:**
  * Windows Installation ISO:
    * A valid Windows ISO (e.g., Windows Server 2012, 2016, 2019, 2022, Windows 10, etc.)
  * VirtIO Driver ISO:
    * Windows requires VirtIO drivers for better performance on a Linux (QEMU-KVM) hypervisor.
    * Download the latest stable VirtIO driver ISO from the [Fedora VirtIO repository](https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/stable-virtio/).
      * This ISO contains drivers for storage, networking, and other virtual devices required during Windows installation.

***

## Step 1: Upload Images

#### 1.1 Upload Windows Installation ISO

Use the following command to upload the Windows ISO (e.g., Windows Server 2012, 2016, 2019, 2022, Windows 10, etc.) to the <code class="expression">space.vars.product\_acronym</code> Image service:

{% tabs %}
{% tab title="Bash" %}

```bash
openstack image create "windows-installation-iso" --os-interface admin --insecure \
  --disk-format iso \
  --container-format bare \
  --file /path/to/windows-installation.iso \
  --property hw_boot_menu=True \
  --property hw_cdrom_bus=sata \
  --property hw_disk_bus=scsi \
  --property hw_firmware_type=uefi \
  --property hw_machine_type=q35 \
  --property hw_scsi_model=virtio-scsi \
  --property os_secure_boot=required \
  --property os_type=Windows
```

{% endtab %}
{% endtabs %}

#### 1.2 Upload VirtIO Driver ISO

Use the following command to upload the VirtIO driver ISO file to the <code class="expression">space.vars.product\_acronym</code> Image service:

{% tabs %}
{% tab title="Bash" %}

```bash
openstack image create "virtio-driver-iso" --os-interface admin --insecure \
  --disk-format iso \
  --container-format bare \
  --file /path/to/virtio-win.iso
```

{% endtab %}
{% endtabs %}

## Step 2: Create Volumes

Create the following volumes to proceed:

{% hint style="info" %}
**Note**

If a volume type is not specified, <code class="expression">space.vars.product\_name</code> will use the `__DEFAULT__` type. Should you want to store these volumes on block storage, add `--type <volume-type>` to the end of the `volume create` commands.
{% endhint %}

#### 2.1 Create Installation Media Volume

{% hint style="info" %}
**Purpose**

Acts as the bootable volume containing the Windows installation media.
{% endhint %}

{% tabs %}
{% tab title="Bash" %}

```bash
openstack volume create --image windows-installation-iso --size 10 --bootable windows-installation-volume --insecure
```

{% endtab %}
{% endtabs %}

#### 2.2 Create VirtIO Driver Media Volume

{% hint style="info" %}
**Purpose**

Provides VirtIO drivers during Windows installation.
{% endhint %}

{% tabs %}
{% tab title="Bash" %}

```bash
openstack volume create --image virtio-driver-iso --size 2 virtio-driver-volume --insecure
```

{% endtab %}
{% endtabs %}

#### 2.3 Create Windows OS Target Volume

{% hint style="info" %}
**Purpose**

Target disk where Windows will be installed.
{% endhint %}

{% tabs %}
{% tab title="Bash" %}

```bash
openstack volume create --size 30 --bootable windows-os-target-volume --insecure
```

{% endtab %}
{% endtabs %}

## Step 3: Create the VM

This step creates a virtual machine using the previously created volumes. The VM will:

* **Boot from the Windows installation ISO** *(device\_type=cdrom)*: Allows the VM to load the Windows installer.
* **Attach the VirtIO driver ISO** *(device\_type=cdrom)*: Provides essential drivers during the installation process.
* **Use the target volume as the Windows installation disk** *(device\_type=disk)*: Serves as the destination for the Windows OS installation.

The properties specified in the command ensure the VM boots correctly and remains compatible with the Windows installation requirements.

#### 3.1 Launch the VM Using Created Volumes

{% tabs %}
{% tab title="Bash" %}

```bash
openstack server create --insecure --flavor m1.xlarge --network <NETWORK_NAME_OR_UUID> \
  --block-device source_type=volume,uuid=$(openstack volume show windows-installation-volume -f value -c id --insecure),destination_type=volume,device_type=cdrom,boot_index=0 \
  --block-device source_type=volume,uuid=$(openstack volume show virtio-driver-volume -f value -c id --insecure),destination_type=volume,device_type=cdrom,boot_index=-1 \
  --block-device source_type=volume,uuid=$(openstack volume show windows-os-target-volume -f value -c id --insecure),destination_type=volume,device_type=disk,boot_index=1 \
  --property hw_firmware_type=uefi --property hw_machine_type=q35 --property os_secure_boot=disabled \
  --property hw_boot_menu=True --property hw_video_model=qxl <vm-name>
```

{% endtab %}
{% endtabs %}

{% hint style="info" %}
**Important**

> * Replace `<NETWORK_NAME_OR_UUID>` with the appropriate network name or UUID in your environment.
> * Replace `<vm-name>` with the desired name for your VM.
> * The `openstack volume show` commands reference the previously created volumes to ensure correct attachment.
>   {% endhint %}

## Step 4: Configure the VM

#### 4.1 Initial Boot Process

* Access the VM console from the <code class="expression">space.vars.product\_acronym</code> UI.
* Press Enter
* Select "Boot Manager" and press Enter.

<figure><img src="/files/XnH1ypPHHggaY3RPsGBQ" alt=""><figcaption></figcaption></figure>

* Select **UEFI QEMU QEMU CD-ROM** from the Boot Manager and press Enter.

<figure><img src="/files/R6AoRris1xgW3nrxomhJ" alt=""><figcaption></figcaption></figure>

* Press any key to boot from CD. The Windows installer should load. *(This is only necessary during the first boot.)*

<figure><img src="/files/LudI5fXQ8ffoUfk4m0TK" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/1FHyUrtiUf3g3pggDapY" alt=""><figcaption></figcaption></figure>

\_\_

#### 4.2 Installing VirtIO drivers

1. Follow the Windows installation wizard.
2. **Load VirtIO Drivers:**
   * Click **Browse** when prompted for storage drivers.
   * Navigate to the VirtIO driver ISO identified by the Windows version you are installing (e.g., `D:\amd64\2k19`).
   * Select and install the appropriate driver.

<figure><img src="/files/XvDktvMRuLvqKxirC5GP" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/bo3G5DOGi6dezQxaQ8We" alt=""><figcaption></figcaption></figure>

#### 4.3 Disable Secure Boot and VTPM (Mandatory step for Windows 11 onwards)

Windows 11 installer mandates the use of VirtualTPM during install. The following steps help disable these checks so that Windows 11 can be installed.

1. While on the OS selection page press Shift+F10
2. The command prompt should open. Type `regedit` and hit enter to start the registry editor.
3. In registry editor, navigate to `HKEY_LOCAL_MACHINE > SYSTEM > Setup` folder
4. Create a new key under it called `Labconfig`
5. Under the `Labconfig` key, create the following 2 entries of type REG\_DWORD with values set to 1
   1. `BypassTPMCheck`
   2. `BypassSecureBootCheck`
6. Close the regedit and command line tools and proceed with the Windows install.

<figure><img src="/files/y9sKvsc7cOp5irj1sK9E" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/F3KLzEdIzL6DcsqFjooi" alt=""><figcaption></figcaption></figure>

#### 4.4 Install Network & Other Required Drivers

After the Windows installation has completed, install necessary drivers.

1. Open **Device Manager**.
2. Right-click **Ethernet Controller** → **Update Driver Software**.
3. Select the VirtIO path (e.g., `E:\NetKVM\2k16\`).
4. Complete the driver installation.
5. Repeat as needed for remaining devices in Device Manager.

#### 4.5 Install Cloudbase-Init

1. Download and Run [Cloudbase-Init](https://cloudbase.it/cloudbase-init/) to enable automated configurations for future VMs, as <code class="expression">space.vars.product\_name</code> uses this to set the initial Administrator password during VM deployment.
2. Select the option to run Sysprep for creating a generalized golden image.
3. Allow the VM to power off automatically upon completion.

<figure><img src="/files/dAvFJwNjACVZ59GYjO81" alt=""><figcaption></figcaption></figure>

## Step 5: Convert the VM into a Golden Image

#### 5.1 Detach the Installation Volume

Detach the `windows-os-target-volume`, which contains the installed OS, to prepare it for upload as a Glance image.

{% tabs %}
{% tab title="Bash" %}

```bash
openstack server remove volume <vm-name> windows-os-target-volume
```

{% endtab %}
{% endtabs %}

*Note*: The VM can be deleted after detaching the volume, as its primary purpose was to prepare the Windows image.

5.2 Create a Glance image from the installation volume

{% tabs %}
{% tab title="Bash" %}

```bash
openstack --os-interface admin --insecure image create "<windows-image-name>" --disk-format raw  --volume windows-os-target-volume
```

{% endtab %}
{% endtabs %}

#### 5.3 Set Image properties

The following properties are required in order for the VM to boot properly.

{% tabs %}
{% tab title="Bash" %}

```bash
openstack --os-interface admin --insecure image set <windows-image-name> \
  --property hw_boot_menu=True \
  --property hw_cdrom_bus=sata \
  --property hw_disk_bus=scsi \
  --property hw_firmware_type=uefi \
  --property hw_machine_type=q35 \
  --property hw_scsi_model=virtio-scsi \
  --property os_secure_boot=required \
  --property os_type=Windows
```

{% endtab %}
{% endtabs %}

{% hint style="success" %}
**Expected Result**

A reusable golden image is created for future Windows VM deployments.

With the golden image created, new VMs can be deployed quickly without repeating the installation process.
{% endhint %}

## Step 6: Deploy a VM from the golden image

Please refer to the [Deploy Vms On Your Virtualized Cluster](/private-cloud-director/2025.7/tutorials/deploy-vms-on-your-virtualized-cluster.md) guide to deploy a VM with the new golden image.


---

# Agent Instructions: 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:

```
GET https://docs.platform9.com/private-cloud-director/2025.7/tutorials/create-windows-vm-from-iso/creating-a-windows-virtual-machine--vm--from-an-iso-image.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.