Installing Windows 11 24H2 on Proxmox VE - Complete Guide
From ISO to fully optimized virtual machine
![]()
![]()
![]()
![]()
So you’ve got Proxmox running and you need a Windows 11 VM. Maybe it’s for testing, remote access to Windows apps, or running software that just won’t work on Linux. Whatever the reason, this guide walks you through the entire process.
Windows 11 on Proxmox works great - once you know the tricks. Let’s get it done.
Prerequisites
Before we start, make sure you have:
- Proxmox VE host or cluster - Running and accessible via web UI
- Download: Proxmox VE ISO
- Windows 11 24H2 ISO - Properly formatted, downloaded from Microsoft
-
Download: Windows 11 Disk Image (ISO)
-
Select “Download Windows 11 Disk Image (ISO)” → Choose edition → Download
-
VirtIO drivers ISO - We’ll download this (required for disk/network drivers)
-
Adequate resources available:
-
Minimum 4GB RAM (8GB+ recommended)
-
Minimum 64GB storage (128GB+ recommended)
-
2+ CPU cores (4+ recommended)
Step 1: Download VirtIO Drivers ISO
This step is critical. Windows doesn’t have built-in drivers for Proxmox’s virtualized hardware. Without VirtIO drivers, Windows won’t see your virtual disk during installation.
Download the VirtIO ISO
-
Open your Proxmox web interface
-
Navigate to your local storage (or preferred ISO storage location)
-
Click ISO Images in the content panel
-
Click Download from URL
VirtIO Stable ISO URL:
https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/stable-virtio/virtio-win.iso
-
Paste the URL and click Query URL
-
Click Download
Alternative: Download manually from Fedora VirtIO-Win and upload to Proxmox.
Verify Both ISOs Are Uploaded
In your storage → ISO Images, you should see:
-
Your Windows 11 ISO (e.g.,
Win11_24H2_English_x64.iso) -
VirtIO drivers ISO (
virtio-win.iso)
Step 2: Create the Virtual Machine
Start the VM Creation Wizard
-
Click Create VM button (top right of Proxmox web UI)
-
Or right-click a node → Create VM
General Tab
| Setting | Value |
|---------|-------|
| Node | Select your preferred node (e.g., pve-1) |
| VM ID | Auto-assigned or choose your own (e.g., 300) |
| Name | windows11 (or descriptive name like win11-workstation) |
Check “Advanced” at the bottom to see all options.
Click Next.
OS Tab
| Setting | Value |
|---------|-------|
| Use CD/DVD disc image file (iso) |
Selected |
| Storage | local (or your ISO storage) |
| ISO image | Select your Windows 11 ISO |
| Guest OS Type | Microsoft Windows |
| Version | 11/2022/2025 |
Check “Add additional drive for VirtIO drivers”
-
Storage:
local(or your ISO storage) -
ISO image: Select
virtio-win.iso
Click Next.
System Tab
This is where Windows 11 requirements come in. Windows 11 requires TPM 2.0 and UEFI.
| Setting | Value |
|---------|-------|
| Graphics card | Default |
| Machine | q35 |
| BIOS | OVMF (UEFI) |
| Add EFI Disk |
Checked |
| EFI Storage | Select your VM storage (e.g., local-lvm, ceph-pool) |
| Pre-Enroll keys |
Checked (enables Secure Boot) |
| Add TPM |
Checked |
| TPM Storage | Select your VM storage |
| TPM Version | v2.0 |
| SCSI Controller | VirtIO SCSI single |
| Qemu Agent |
Checked |
Important: TPM and UEFI with Secure Boot are required for Windows 11. Without them, installation will fail with “This PC can’t run Windows 11.”
Click Next.
Disks Tab
| Setting | Value |
|---------|-------|
| Bus/Device | SCSI (default with VirtIO SCSI controller) |
| Storage | Select your VM storage (e.g., local-lvm, ceph-pool) |
| Disk size (GiB) | 128 (minimum 64, recommended 128+) |
| Cache | Write back (best performance) |
| Discard |
Checked (if using SSD/thin provisioning) |
| IO Thread |
Checked (improves I/O performance) |
Performance tip: If using Ceph or shared storage, Write back cache gives best performance. For local SSDs, None or Write through are also fine.
Click Next.
CPU Tab
| Setting | Value |
|---------|-------|
| Sockets | 1 |
| Cores | 4 (minimum 2, adjust based on workload) |
| Type | host (best performance) or x86-64-v2-AES |
CPU Type explanation:
-
host- Passes through your actual CPU features. Best performance, but VM can’t be live-migrated to hosts with different CPUs. -
x86-64-v2-AES- Good compatibility and performance. Use this if you plan to migrate VMs between hosts with different CPU models.
Recommendation: Use host for single-node setups or clusters with identical hardware. Use x86-64-v2-AES if you need live migration between different CPU types.
Click Next.
Memory Tab
| Setting | Value |
|---------|-------|
| Memory (MiB) | 8192 (8GB - recommended minimum) |
| Minimum memory | Leave blank or set for ballooning |
| Ballooning Device |
Checked (optional - allows dynamic memory) |
Memory recommendations:
-
Light use (web, Office): 4096 MiB (4GB)
-
General use: 8192 MiB (8GB)
-
Heavy use (development, VMs): 16384 MiB (16GB+)
Click Next.
Network Tab
| Setting | Value |
|---------|-------|
| Bridge | vmbr0 (or your network bridge) |
| Model | VirtIO (paravirtualized) |
| Firewall |
or
based on your setup |
VirtIO network gives best performance but requires the VirtIO drivers we’ll install.
Click Next.
Confirm Tab
Review all settings. Should look something like:
Node: pve-1
VM ID: 300
Name: windows11
OS: Microsoft Windows 11/2022/2025
Machine: q35
BIOS: OVMF (UEFI)
TPM: v2.0
Disk: 128 GiB on local-lvm (VirtIO SCSI)
CPU: 4 cores (host)
Memory: 8192 MiB
Network: vmbr0 (VirtIO)
Check “Start after created” if you want to begin installation immediately.
Click Finish.
Step 3: Install Windows 11
Start the VM and Open Console
-
Select your new Windows VM in the left panel
-
Click Start (if not already started)
-
Click Console → noVNC (or SPICE if configured)
Boot from Windows ISO
The VM should automatically boot from the Windows ISO. If not:
-
Click Console dropdown → Send Key → Ctrl+Alt+Delete
-
Press a key quickly when you see “Press any key to boot from CD or DVD”
Windows Setup
1. Language and Region
-
Select your language, time format, and keyboard
-
Click Next
2. Install Now
- Click Install now
3. Product Key
- Enter your key, or click “I don’t have a product key” to install and activate later
4. Select Edition
-
Choose Windows 11 Pro (recommended) or your licensed edition
-
Click Next
5. License Agreement
-
Accept the terms
-
Click Next
6. Installation Type
- Click “Custom: Install Windows only (advanced)”
Load VirtIO Storage Driver
Here’s where the VirtIO drivers come in.
You’ll see: “Where do you want to install Windows?” with no drives listed.
-
Click “Load driver”
-
Click “Browse”
-
Navigate to the VirtIO CD drive (usually
D:orE:) -
Browse to:
vioscsi→w11→amd64
- Full path:
D:\vioscsi\w11\amd64
-
Click OK
-
Select “Red Hat VirtIO SCSI controller”
-
Click Next
Your virtual disk should now appear!
Continue Installation
-
Select your virtual disk (e.g.,
Drive 0 Unallocated Space: 128.0 GB) -
Click Next
-
Windows will install - this takes 10-20 minutes
-
VM will reboot automatically several times
Step 4: Windows Out of Box Experience (OOBE)
After installation, Windows 11 OOBE begins.
Region and Keyboard
-
Select your country/region
-
Select keyboard layout
-
Skip second keyboard layout (unless needed)
Network Setup
Since we haven’t installed the VirtIO network driver yet, Windows won’t detect any network adapters. This is actually fine - it lets us skip the Microsoft account requirement easily.
To skip Microsoft account and use a local account:
-
When asked to connect to network, press Shift + F10 to open Command Prompt
-
Type:
oobe\bypassnro -
Press Enter - PC will restart
-
After restart, you’ll see “I don’t have internet” option
-
Click it, then “Continue with limited setup”
Account Setup
-
Enter a username (this will be your daily driver account)
-
Set a password (can be blank for auto-login, not recommended)
-
Set security questions
Important: This first account is created as an Administrator. After setup, you should:
-
Create a second local account as your dedicated Administrator
-
Downgrade your daily driver account to Standard User
This separation adds a critical security layer - malware and accidental changes can’t modify system files without explicit admin approval.
Full guide: Why You Should Ditch the Microsoft Account and Stop Using Admin
Privacy Settings
-
Disable everything you don’t need (Location, Find my device, Diagnostic data, etc.)
-
Windows 11 is aggressive with telemetry - disable what you can
Deep dive on privacy hardening: Securing Windows 11 for Privacy - A Minimal Workstation
Complete Setup
Windows will finalize settings and boot to desktop. This may take a few minutes.
Step 5: Install VirtIO Drivers and Guest Agent
Critical step! Your VM is running but without optimized drivers.
Open VirtIO CD in Windows
-
Open File Explorer
-
Navigate to the VirtIO CD drive (D: or E:)
-
Run both of these installers:
-
virtio-win-gt-x64.msi- VirtIO drivers -
virtio-win-guest-tools.exe- Guest tools and agent
These installers will install:
-
VirtIO Balloon driver (memory management)
-
VirtIO Serial driver (communication)
-
VirtIO Network driver (if not loaded during install)
-
VirtIO SCSI driver (if not loaded during install)
-
QEMU Guest Agent
-
SPICE agent (for enhanced graphics)
Run the Installers
First: Run virtio-win-gt-x64.msi
-
Double-click
virtio-win-gt-x64.msi -
Click Next through the wizard
-
Accept license agreement
-
Choose Complete installation
-
Click Install
-
Click Finish
Second: Run virtio-win-guest-tools.exe
-
Double-click
virtio-win-guest-tools.exe -
Follow the installation prompts
-
Click Finish
-
Reboot Windows
Verify Guest Agent
After reboot, in Proxmox web UI:
-
Select your Windows VM
-
Look at the Summary tab
-
You should see the VM’s IP address and other details
-
Under Guest Agent, status should show as connected
Step 6: Post-Installation Optimization
Remove VirtIO ISO from VM
-
In Proxmox, select your Windows VM
-
Go to Hardware tab
-
Select the CD/DVD drive with
virtio-win.iso -
Click Edit → Do not use any media
-
Optionally remove the Windows ISO drive too
Enable Remote Desktop (Optional)
If you want to RDP into the VM instead of using Proxmox console:
-
Open Settings → System → Remote Desktop
-
Toggle Remote Desktop to On
-
Note the PC name or IP address
Now you can connect via RDP from any device on your network.
Install Windows Updates
-
Open Settings → Windows Update
-
Click Check for updates
-
Install all available updates
-
Reboot as needed
Performance Tweaks
Disable Unnecessary Visual Effects:
-
Right-click Start → System
-
Click Advanced system settings
-
Under Performance, click Settings
-
Select “Adjust for best performance” or customize
Power Plan:
-
Open Control Panel → Power Options
-
Select High performance (may need to show additional plans)
Disable Hibernation (saves disk space):
# Run PowerShell as Administrator
powercfg /hibernate off
Step 7: Security & Privacy Hardening (Recommended)
Windows 11 comes with a lot of telemetry, bloatware, and privacy-invasive defaults. If you want a clean, private, and optimized installation, consider using Winhance.
What is Winhance?
Winhance is a free, open-source Windows optimization tool that lets you:
-
Disable telemetry and tracking - Stop Microsoft from collecting your data
-
Remove bloatware - Get rid of pre-installed apps you don’t need
-
Disable Cortana, Copilot, and other AI features - Keep Windows minimal
-
Optimize performance - Disable unnecessary services and visual effects
-
Harden security settings - Apply privacy-focused configurations
-
Customize Windows behavior - Control updates, notifications, and more
Why Use It?
Instead of manually editing registry keys, running PowerShell scripts, and hunting through settings, Winhance provides a simple GUI to apply all these changes safely. It’s:
-
Reversible - Changes can be undone
-
Transparent - You can see exactly what each option does
-
Actively maintained - Updated for Windows 11 24H2
How to Use
-
Download from winhance.net
-
Run the application (no installation required)
-
Review and select the optimizations you want
-
Apply changes and reboot
Tip: Run Winhance immediately after a fresh Windows install for best results.
TL;DR
-
Download VirtIO ISO - Required for disk/network drivers
-
Create VM with:
-
Machine:
q35 -
BIOS:
OVMF (UEFI)with EFI disk -
TPM:
v2.0(Windows 11 requirement) -
Disk:
VirtIO SCSI -
Network:
VirtIO -
CPU Type:
hostorx86-64-v2-AES
-
During Windows install - Load VirtIO SCSI driver to see disk
-
After install - Run
virtio-win-gt-x64.msifor all drivers + guest agent -
Optimize - Remove ISOs, enable RDP, update Windows
Troubleshooting
“This PC can’t run Windows 11”
-
TPM not enabled → Edit VM → System → Add TPM v2.0
-
Secure Boot not enabled → EFI disk with Pre-Enroll keys
-
Machine type wrong → Must be
q35
No Disk Visible During Install
-
VirtIO driver not loaded
-
Load driver from:
virtio-win.iso→vioscsi→w11→amd64
No Network After Install
-
Install VirtIO network driver
-
Run the full
virtio-win-gt-x64.msiinstaller
VM Won’t Boot After Install
-
Check boot order in VM → Options → Boot Order
-
Make sure the SCSI disk is first, CD/DVD after
-
Remove ISOs if still trying to boot from them
Poor Performance
-
Ensure VirtIO drivers are installed (not default Windows drivers)
-
Check CPU type is
hostfor best performance -
Enable IO Thread on disk settings
-
Make sure ballooning isn’t starving the VM of memory
Guest Agent Not Showing
-
Install
virtio-win-gt-x64.msi(includes QEMU Guest Agent) -
Check Windows Services → QEMU Guest Agent is running
-
Reboot the VM
Your Turn
Got Windows 11 running on Proxmox?
Any issues during installation?
Share your VM specs and use case below!