How to Install Proxmox VE on Hyper-V (Nested Virtualization for Testing on Windows)

If you've read anything about Proxmox VE, you've probably seen the advice to just grab an old desktop or a cheap mini PC and install it directly. That's still the best way to run it long-term. But what if you just want to poke around first? Maybe you're not ready to wipe a machine, or you don't have spare hardware sitting around at all. That's where running Proxmox inside Hyper-V comes in.

This isn't a niche trick. It's a genuinely common way to test-drive Proxmox on a Windows laptop or workstation before committing real hardware to it. You get a full, working Proxmox VE web interface, you can create VMs inside it, and you can throw the whole thing away with a few clicks if you decide it's not for you.

What You Will Learn

By the end of this guide you'll know how to:

• Turn on Hyper-V on Windows 10 or 11 Pro (or Windows Server)
• Create a virtual machine configured correctly for Proxmox
• Enable nested virtualization so Proxmox can actually run VMs of its own inside your Hyper-V VM
• Fix the two problems almost everyone hits: no network access and a VM that won't boot
• Reach the Proxmox web interface from your regular browser on the host

What Is This Feature?

Hyper-V is Microsoft's built-in hypervisor. It's the same technology that powers Windows Sandbox and WSL2 under the hood, and it ships free with Windows 10/11 Pro, Enterprise, and Education, plus Windows Server. You don't need to install anything extra beyond turning on a Windows feature.

Nested virtualization is the part that makes this whole guide possible. Normally, a VM can't run its own VMs — it doesn't get access to the CPU's virtualization instructions, because the host is already using them. Nested virtualization is a setting that lets a guest VM pass those instructions through, so the guest can act as a hypervisor itself. Proxmox VE is built on KVM, which absolutely needs those instructions to create its own virtual machines. Without nesting turned on, Proxmox will install fine, but every VM you try to create inside it will fail to start.

Why Would You Use It?

A few honest reasons people do this:

You want to learn the Proxmox interface, get comfortable with terms like storage pools, bridges, and LXC containers, before you touch production hardware. You're evaluating Proxmox against ESXi or Hyper-V itself and want a like-for-like comparison without racking a second server. Or you're a student or homelab tinkerer who genuinely doesn't have a spare machine right now, and a laptop with 32 GB of RAM is what you've got.

What this setup is not good for: real workloads. Performance inside a nested VM is noticeably slower than bare metal, disk I/O especially. Treat this as a learning sandbox, not a place to run your Plex server or a database you care about.

Prerequisites

• Windows 10 or 11 Pro, Enterprise, or Education — Home edition doesn't include Hyper-V at all. Windows Server 2019/2022/2025 works too.
• A CPU with virtualization support (Intel VT-x or AMD-V) enabled in the BIOS/UEFI. Almost every CPU from the last decade has this; it's usually on by default, but check if Hyper-V refuses to install.
• At least 16 GB of RAM on the host if you want a usable experience — Proxmox itself wants 2 GB minimum, but you'll want headroom to also run a test VM or two inside it.
• Roughly 40–60 GB of free disk space for the virtual hard disk.
• The Proxmox VE ISO, downloaded from the official Proxmox downloads page. At the time of writing, the current release is Proxmox VE 9.2, built on Debian 13 "Trixie."

Step-by-Step Tutorial

Step 1: Turn on Hyper-V

Open PowerShell as Administrator and run:

Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V -All

Reboot when it asks you to. If you'd rather click through a GUI, you can also enable it from Control Panel → Programs → Turn Windows features on or off → check Hyper-V.

Step 2: Create a virtual switch (if you don't have one)

Open Hyper-V Manager, then go to Virtual Switch Manager on the right-hand panel. Create a New virtual network switch, choose External, and bind it to your physical network adapter (Wi-Fi or Ethernet). This is the step people skip, and it's the reason so many nested Proxmox installs end up with no internet access. The default Hyper-V switch does NAT and doesn't play nicely with a hypervisor guest that needs its own bridged network.

Step 3: Create the VM

In Hyper-V Manager, click New → Virtual Machine, and set it up like this:

• Generation: Generation 2 (UEFI-based — Proxmox needs this)
• Memory: At least 4096 MB, and turn off Dynamic Memory. Nested hypervisors don't handle memory ballooning from the host well, so give it a fixed amount.
• Network: Connect to the External switch you created in Step 2
• Virtual hard disk: 40 GB or more, dynamically expanding is fine
• Installation media: Point it at the Proxmox VE ISO you downloaded

Step 4: Turn off Secure Boot for this VM

Before starting the VM, run:

Set-VMFirmware -VMName "Proxmox" -EnableSecureBoot Off

Proxmox's boot loader isn't signed for Windows' default Secure Boot template, so the VM will sit at a black screen or drop to a UEFI shell without this. Swap "Proxmox" for whatever you named your VM.

Step 5: Enable nested virtualization

This is the step that's easy to miss, and it has to be done while the VM is turned off:

Set-VMProcessor -VMName "Proxmox" -ExposeVirtualizationExtensions $true

Also turn on MAC address spoofing on the network adapter, since Proxmox will be creating its own virtual NICs for its VMs, and Hyper-V blocks unrecognized MAC addresses by default:

Get-VMNetworkAdapter -VMName "Proxmox" | Set-VMNetworkAdapter -MacAddressSpoofing On

Step 6: Install Proxmox VE

Start the VM and connect to it. You'll see the standard Proxmox installer. If you've never installed Proxmox before, the short version is: pick your target disk (the virtual hard disk you created), set your country and time zone for correct NTP behavior, and set a root password and email address. Filesystem-wise, ext4 is the simplest choice for a nested test VM — you don't need ZFS's redundancy features when the whole thing is one virtual disk sitting on your Windows filesystem anyway.

Set a static IP during installation if your network has a free address to spare, or leave DHCP on and check what address it grabbed afterward. The install itself takes about five to eight minutes.

Step 7: Reach the web interface

Once it reboots, the console will show you an IP address. From your Windows host (or any device on the same network, since you bridged to an External switch), open a browser and go to:

https://<proxmox-ip>:8006

You'll get a certificate warning because Proxmox uses a self-signed certificate out of the box — that's normal, click through it. Log in as root with the password you set during install.

Commands Explained

Common Errors

VM boots to a black screen or "Boot Failed": almost always Secure Boot. Turn it off with the command in Step 4.

Proxmox installs fine, but VMs inside it won't start, with an error mentioning kvm: failed to initialize KVM: nested virtualization wasn't enabled, or it was enabled while the VM was still running. Shut the VM down completely (not just save state) and re-run the Set-VMProcessor command.

Proxmox has an IP but you can't reach the web interface, or VMs inside Proxmox have no network access: almost always the Default Switch instead of an External switch, or MAC spoofing left off. Both are covered in Steps 2 and 5.

"This platform does not support the instruction NX" or similarly odd CPU errors: some older CPUs, or CPUs with virtualization disabled in the BIOS entirely, won't expose the extensions Hyper-V needs to pass through. Check your BIOS settings first.

Troubleshooting

If networking still isn't working after checking the switch type and MAC spoofing, open a shell inside the Proxmox VM (via the Hyper-V console) and run ip a to confirm it actually got an address on vmbr0. If it didn't, check that your physical adapter used for the External switch isn't also being used by something else, like a VPN client, that's grabbing traffic first.

If the VM feels painfully slow, check Task Manager on the Windows host while it's running. Nested virtualization has real overhead — expect noticeably slower disk performance than bare metal, especially for anything ZFS-related. If you're testing storage performance specifically, this setup will give you misleading numbers.

One more thing worth knowing: Windows updates occasionally reset Hyper-V VM processor settings, or at least that's been reported by enough people that it's worth a quick check. If nested VMs suddenly stop starting after a Windows update, re-run the Set-VMProcessor command before assuming something else broke.

Antivirus and endpoint security software on the host can also interfere, especially anything that hooks into low-level system calls. If you're on a corporate laptop with managed security software and nothing above explains a boot failure, that's worth checking with your IT team before you burn an afternoon on it. And if you installed Hyper-V after already having VirtualBox or VMware Workstation on the same machine, be aware they can't run at the same time as Hyper-V on older Windows builds — Hyper-V effectively takes over the hardware virtualization layer. Recent Windows versions handle this better through a shared virtualization stack, but if you see VirtualBox suddenly failing to start VMs after enabling Hyper-V, that's why.

Best Practices

Give the VM a fixed amount of memory rather than Dynamic Memory — nested hypervisors generally don't like having memory taken away while running. Use an External virtual switch, not the Default Switch, so Proxmox behaves like it's on a real network rather than behind Hyper-V's own NAT layer. Don't run more than one or two lightweight test VMs inside your nested Proxmox — you're already a layer removed from real hardware, and stacking more virtualization on top just multiplies the overhead. And treat this environment as disposable. Don't store anything in it you'd be upset to lose, since the whole point is that you can delete the VM and start over in minutes.

Frequently Asked Questions

Can I do this on Windows 10 or 11 Home?

No. Hyper-V isn't available on Home editions. You'd need to upgrade to Pro, or use a different hypervisor like VirtualBox instead.

Is performance inside nested Proxmox usable for real work?

For learning the interface and testing configuration, yes. For anything performance-sensitive, no — expect noticeably slower disk and network throughput than a bare-metal install.

Can I access this Proxmox VM from other devices on my network?

Yes, as long as you used an External virtual switch. It gets its own IP address on your LAN just like a physical machine would.

Do I need a Proxmox subscription to try this?

No. The free Community/no-subscription repository works fine for testing and covers everything you need for a nested lab.

Will my VMs and settings survive a Windows reboot?

Yes, as long as you don't delete the Hyper-V VM itself. Proxmox behaves exactly like it would on real hardware — it just happens to be running inside another VM.

Conclusion

Running Proxmox nested inside Hyper-V won't replace a dedicated box if you're planning to actually rely on it, but for kicking the tires, it's hard to beat. You get the full web interface, real VM creation, and a safe space to break things, all without touching your existing hardware setup. Once you're comfortable with how storage, networking, and VMs work inside Proxmox, moving to bare metal is mostly just repeating the same install process without the nesting steps.