Create a Windows 11 VM in Hyper-V with Packer

Some people ask if it is possible to create a Windows 11 VM in Hyper-V with Packer. The answer is YES. The Packer plugin that makes this possible is called “Hyperv”. Version 1.1.1 supports TPM. Enabling TPM in the Hyper-V VM makes it possible to install Windows 11 without any registry hacks.

So I decided to test Packer with Hyper-V and Windows 11 and create a blog post about it.

So what are the prerequisites?

  • Make sure the Hyper-V role is enabled in Windows 10/11
  • Download the Windows 11 ISO and save the ISO to the following location: c:\iso
    An example of downloading and creating a Windows 10/11 ISO can be found here:
  • Install the Windows Assessment and Deployment Kit (32-bit version).
  • Add the following location the the system path variable: C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\x86\Oscdimg

When the prerequisites are met you can go further with the rest. To make it easy I created a PowerShell script called (link) that does all the work for you.

# Enable TLS 1.2
[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12
# Speed up the invoke-webrequest command
$ProgressPreference = 'SilentlyContinue'

# Variables
$downloadfolder = "C:\temp\" # Packer location installed
$win11_downloadfolder = "C:\Temp\packer-main\hyper-v\windows11\"
$packer_config = "windows.json.pkr.hcl" #Packer config file
$packer_variable = "" # Packer variable file
$github = ""
$product = "packer"
$packer_uri = ""

# Check if the temp folder exist
If(!(test-path -PathType container $downloadfolder))
      New-Item -ItemType Directory -Path $downloadfolder

# Go to the Packer download folder
Set-Location $downloadfolder

# Download Github files
Invoke-WebRequest -Uri $github -OutFile ${downloadfolder}
Expand-Archive ${downloadfolder} -DestinationPath $downloadfolder -Force

# Remove zip file
Remove-Item -Path ${downloadfolder} 

# Download the latest version of Packer
$packurl = Invoke-WebRequest -Uri $packer_uri| Select-Object -Expand links | Where-Object href -match "//releases\.hashicorp\.com/$product/\d.*/$product_.*_windows_amd64\.zip$" | Select-Object -Expand href
$packdown = $packurl | Split-Path -Leaf
$packdownload = $downloadfolder + $packdown
Invoke-WebRequest $packurl -outfile $packdownload

# Unzip Packer 
Expand-Archive $packdownload -DestinationPath $win11_downloadfolder -Force
# Remove the Packer ZIP file
Remove-Item $packdownload

# Go to the Packer download folder
Set-Location $win11_downloadfolder

  • Line 7-13: This is the variable block. Change if needed
  • Line 13-19: Here are the variables located. Change if needed
  • Line 21-25: The script creates a c:\temp folder if it does not exist
  • Line 30-32: Downloads the GitHub files for creating a Windows 11 VM
  • Line 37-41: Downloads the latest version of Packer

After running the script it is time to change the variables:

  • Get the hash of the ISO file with the Powershell Get-Filehash command and change the variable in the windows-auto-pkvars.hcl file
  • Change the other variables in the windows-auto-pkvars.hcl such as win_iso for the exact iso name
  • Run the following _2.run_packer.ps1 script
# Show Packer Version
.\packer.exe -v

# Download Packer plugins
.\packer.exe init "${$win11_downloadfolder}${packer_config}"

# Packer Format configuration files (.pkr.hcl) and variable files (.pkrvars.hcl) are updated.
.\packer.exe fmt -var-file="${$win11_downloadfolder}{$packer_variable}" "${$win11_downloadfolder}${packer_config}"

# Packer validate
.\packer.exe validate .

# Packer build
.\packer.exe build -force -var-file="${$win11_downloadfolder}${packer_variable}" "${$win11_downloadfolder}${packer_config}"
  • Line 2: Show the Packer version
  • Line 5: Download Packer plugins such as the hyper-v and Windows update plugin
  • Line 8: Formats the config and variable HCL file syntax
  • Line 11: Performs a validation to make sure the variable and config file are ok
  • Line 15: Starts Packer to create a Windows 11 VM

The creation of a Windows 11 VM starts. When the image is created it is stored and needs to be imported in the Hyper-V manager.

  • Start the Hyper-V Manager
  • Select Import Virtual Machine
  • Browse to the created image folder C:\Temp\packer-main\hyper-v\windows11\output-windows11\
  • Select the VM
  • Register the VM in-place
  • Start the VM

On my laptop, I have in 35 minutes a fresh copy of Windows 11 running with the latest updates installed running in Hyper-V. How cool is that! The scripts can be found on my GitHub page (link). Have fun creating Windows 11 VMs.


Run VMware Workstation and Microsoft Hyper-V together in Windows 10

In 2013 I wrote a blog post that it was not possible to run VMware Workstation when the Hyper-V role was enabled (link). Since VMware Workstation 15.5 it is possible to run VMware Workstation and the Hyper-V role together.


  • Windows 10 2004 or newer
  • VMware Workstation 15.5.5 or newer
  • Supported CPU: Intel Sandy Bridge or an AMD Bulldozer or newer

I tested this with my Windows 10 laptop with the Hyper-V role enabled, the Windows Subsystem for Linux running, and VMware Workstation 16 Pro. In Hyper-V and VMware Workstation a Windows 10 VM is running. In the screenshot below you see all the components started:

This is very cool, now you can run VMware Workstation and Hyper-V role at the same time even with the WSL active.

Manage Hyper-V in a workgroup remotely

Managing  Hyper-V remotely in a workgroup can be challenging to configure. This is still the case for Windows Server 2016. For a testing environment I needed to remotely manage Windows Server 2016 core server with the Hyper-V role enabled from Windows 10 with the Hyper-V manager. I used the following manual configuration:

  • Client with Hyper-V Manager (Windows 10). This client is called win10-01
  • Server with Windows Server 2016 core version with the Hyper-V role enabled. The server is called hv-02
  • Both systems are in the same workgroup called “workgroup”
  • Both systems have the same username and password.

Configuration on the Windows Server 2016  server:

  • Enable Remote Management
Configure-SMRemoting.exe -Enable
  • Open firewall for  Remote Computer Management
Set-NetFirewallRule -DisplayGroup 'Windows Management Instrumentation (WMI)' -Enabled true -PassThru
Set-NetFirewallRule -DisplayGroup 'Remote Event Log Management' -Enabled true -PassThru
  • Open firewall for ping (ICMPv4)
Set-NetFirewallRule -DisplayName “File and Printer Sharing (Echo Request – ICMPv4-In)” -Enabled True -PassThru
  • Enable Remote Desktop and allow remote connections
cscript.exe c:\Windows\System32\SCregEdit.wsf /AR 0
  • Enable Remote disk management
Set-NetFirewallRule -DisplayGroup 'Remote Volume Management' -Enabled true -PassThru


Configuration on the Windows 10 client:

  • Create a host file with IP address and hostname of the server. Make sure you can ping the hostname


  • Make sure that the network type is part of a private network before executing the WINRM command

1 2

  • Enable Remote Management
winrm quickconfig
  • For Managing remote systems
winrm set winrm/config/client @{TrustedHosts="Name of the Server"}
  • Enable remote disk Management (add this command on both systems) firewall rule
Set-NetFirewallRule -DisplayGroup 'Remote Volume Management' -Enabled true -PassThru
  • Open c:\windows\system32\dcomcnfg.exe and allow ‘anonymous logon’ for local and remote access.


After making this settings I was able to manage the Windows Server 2016 server with the following tools remotely:

  • Hyper-V manager
  • Computer Management
  • Disk Management


3 4