Creating a VM is an easy enough task that can be left to defaults a lot of the time. But if you want the best performance/options under Proxmox, you will have to go through a few minor hoops as Windows Server 2022 (or prior) does not have the drivers needed for everything built in.
Click on Create VM to get the dialog box. First click on Advanced if it is not already checked.
2b4fab9a-d79d-4e30-85ad-fecfd981b31e-61d2eb12-74d6-4b3b-8344-466a09e7d095-image.png
Give the VM a name (2), ID (1), Start on boot (3), and order/delay (4) as desired. Then hit Next.
Everything below the line is hidden if you have not checked Advanced.
1fae10a8-9fae-43a8-b1ca-570122289659-1a7faaf6-d754-4397-9ef7-59035119be17-image.png
Choose your ISO and Guest OS Type, then hit next.
0ac3f9e9-34da-434c-b2fc-09d233972ff7-3396d1a1-3d71-4fda-b832-b8992b04ee10-image.png
Since you specified a modern version of Windows, Proxmox automatically uses UEFI and you will need to specify EFI and TPM storage locations.
I always keep them on the same disk that will house the boot storage.
ef3e4b4e-aa83-4b78-b1cc-1870b6aa0251-95401764-637a-492d-a37f-56b81dea16b8-image.png
By default, it will use VirtIO for storage, you want this, but will have to add a driver during the Windows install itself. Also enable the Qemu Agent, again the guest agent will have to be installed after Windows setup completes.
9c9de462-d07b-4cad-9632-75c64fcfef74-159de397-558f-46af-b212-6e43b4da721b-image.png
Change the default IDE disk to SCSI (1), set the storage location (2), and your desired disk size (3).
daf37daf-1cc8-487b-b425-49c0d79238f4-d1726fd5-4a38-428d-b433-1981c6b5ab96-image.png
Assign the number of cores you need.
c17e0574-c160-476e-858f-8ee8d1cec616-7e22d1f2-e3d1-4846-ad2c-2ec00885cd63-image.png
Set your max memory (1), minimum memory (2), and ensure Balooning device (3) remains checked.
9c3525d1-1e6c-4635-86ac-49cc12bcf9ae-475c5d4f-8166-47dc-8771-1b28b5a57f80-image.png
Change the network adapter model to VirtIO (1). You will not have a working network on boot up. The VirtIO drivers will need installed first.
3facee43-75c3-495a-8177-5dc66aaa222d-4330d73d-9ebf-48cc-8658-fd1ab4eccdef-image.png
Review and hit finish. Do not check Start after created.
aaffcfe1-d6cd-4832-be84-2abdfa7d38d9-cdf70445-8bf7-4b27-a39d-f1b551edf2ee-image.png
Select the VM and click on Hardware (1) and then Add (2)
8c5d1081-740f-4041-a84e-f461712c3b1a-169a784d-1318-4ebb-8e2d-4dcdadf3316a-image.png
Choose CD/DVD
2131b224-084d-499b-814d-9d87c71a3dd0-ef989b4e-35bf-4ae8-9936-394cfac8c475-image.png
Add the virtio-win ISO, you will need this mounted to add the storage driver during install.
Current stable ISO can be
found here
6d905010-a5c5-4874-8024-857ba0f60ab1-34b7ac3f-972c-4251-8efa-27a50c4374a1-image.png
You can verify your boot order if you want, but it should still be correct.
8f4b2090-2984-49af-a41d-dfbbfa2be7a1-77d58e8f-5a02-49b4-b7c2-dc04e0882c35-image.png
Open the Console
268648c6-32ed-4323-976f-c288514811af-9d9975e4-acea-4a37-8142-9c3d020d6757-image.png
Click Start Now
fe77ddfc-6d83-4f45-bed1-1e95ca7a225f-6d886208-c861-46f9-a991-448d7c5a183d-image.png
Click in the window and press a key, because Microsoft still thinks all of us are fucking stupid.
969635e4-4f14-438f-b100-bc9f192bb7d5-c4722198-166d-4cb7-89c7-dca86b349115-image.png
Set your options and hit Next.
60f7a2da-a348-435e-a9ff-8c31ddf4b6bf-49457952-f3d3-45e7-9fc4-8fe7f6dc3905-image.png
Hit install now.
9d7b6d9f-1af7-4232-989f-0ea434a0ce67-451c5043-2c41-428f-b03e-c3db03d21bf0-image.png
Choose your OS options and hit next.
ee927e46-28a1-4bac-8b77-b9d19a837b8a-8dc9e587-bdaf-43ca-becb-4d5f4cae3b2c-image.png
Accept the license and hit next.
4d539c3f-06a7-4bc5-9341-a82c62c37082-c2ce2d63-a256-4575-8ec6-f001524e538b-image.png
Choose Custom since Microsoft thinks a new install is an advanced task.
b6967c86-f1e9-45f8-b264-e6a4785be3c2-e7a211e8-d4d3-4d84-9477-b6722b8c5625-image.png
Finally, you can load the VirtIO driver (1)
cad4c333-f4e6-4f39-8c32-e293c1babee9-94434902-ddbc-4d31-9a2c-a6f98b61e863-image.png
Click Browse.
a120dffa-7ff6-4eeb-b34f-ba7568811f04-ee6eb413-c957-4230-a2c4-c4f48603add1-image.png
Expand the virtio CD Drive
98afb691-dccc-4ee5-829e-e7c5c80450bd-0e809cea-fbe4-4b53-8eef-88c38b96a0db-image.png
Expand amd64 folder (1), click on 2k22 (2), and click OK (3)
2392520c-411c-4ce6-ba0b-50a5375730b9-b1d5f1fc-6d96-4a90-a0a7-6168bfc14f93-image.png
Click on Next and it will rescan for the disk, no need to click on rescan yourself.
b2266acc-f661-40f1-9455-96e6d2383a08-3c18de1e-af85-46bd-b7d9-f148eb74fb4f-image.png
Now the disk is available, click next
fe68e89d-ccb5-4c44-af1f-4156e9423c23-a1500400-36c4-4465-8a70-e8cbbc5c8c54-image.png
Windows will finish the install like normal and reboot.
b3274703-4e12-4473-9f85-5b0a408c4eab-49104acc-6047-49e0-87ef-1f9562627b78-image.png
wait for it..... It will reboot again
1b5e2b9e-f209-4572-8d46-5b0dae1f14aa-17732bae-41b3-48ba-8ba6-cbbc2aeabaf4-image.png
Create a password for the account you will delete anyway and click Finish. Because you don't leave Administrator do you?
dca1ae33-a99b-4909-bb2c-0c7a1010cdc0-384f6f58-ccaf-4600-b701-a89115b4d2b4-image.png
This example uses the Desktop Experience, so login and wait for the desktop. Close Server Manager and the WAC pop up.
e2f94ae1-5713-4d82-ab1e-c7ca7e271b6b-5ed7dfca-aa08-4018-87cb-80d9bc5a55a0-image.png
Open Device Manager
d699c9d2-ed65-4fac-a974-2753d85f134b-efe871fd-2df0-417f-a661-085d160df53b-image.png
You will see three things to fix.
48f73fdc-1411-4763-ad5e-4c4cb1a7a17f-3236b489-8a10-4b5e-b05d-c93785bcbbed-image.png
Right click and choose update driver for the Ethernet Controller.
9b4612ad-805a-42f4-a19a-ff5b4f38a242-4e7d4fe8-4740-4e59-b241-12758e2933bf-image.png
Choose Browse
22090904-ad38-4eb2-9aad-edb40ccd37b1-7f195d68-769e-44bd-a3ae-7d1eebb16e69-image.png
Browse again
a9920627-df2e-4100-af3c-f8e3fad7cbb0-9e136a99-cf52-4279-9e95-175c5e73c737-image.png
Expand the virtio ISO disk (1), expand netkvm (2), and select 2k22 (2), then click OK.
f67651e3-baf9-4887-bc8b-461a8936357a-006522af-cfe4-4424-ab4a-a57405a10c09-image.png
*Hit next and it will install the driver.
7f32efda-7e62-4bd7-92ba-5e6d3f14df2e-image.png
Before you hit close, you will want to hit yes on the Network discoverability screen for most use cases.
6bc791ed-d3ce-4f97-8913-bc5d21bb7aaf-a3cd2b0c-b0c3-4e7b-a4c8-d55c23ada201-image.png
Repeat the process for the remaining two items.
PCI Device is the Baloon folder
3006c735-9b96-4541-924d-dd9e50057236-4f95e4c6-c471-4b86-a624-7c8681a52e52-image.png
0c083448-9e66-4ab4-8f2a-b11260832f43-0f18c101-68cc-4a1a-bb27-6392c5b7c48e-image.png
PCI Simple Communications Controller is the vioserial folder
f85edca9-067b-4d71-85d2-a46c5e6bf08a-93468da4-2dd2-4193-9916-527ed78fd4b2-image.png
20b68e00-581c-4b2f-b641-35e87b035371-70bc7965-c8b6-45a7-b95c-23d6a9ff9da4-image.png
Now you have all the drivers for the system devices.
cbac0112-c093-4ad4-8e49-3bbd92e13ae2-9866c039-f13f-4341-a6ae-971426179dda-image.png
Finally, browse to the CD drive in Windows Explorer and install the guest agent
c51704a7-187e-46ca-9cf5-b83daa0b52a2-9bebf0e4-4e0a-4df1-ae50-e4e8cde65c10-image.png
You will know the guest agent is properly installed is you see the IP addresses on the Proxmox Summary screen.
851a10e3-06fc-4c05-bfd4-211d4d19f5a7-3cf3f46c-57da-4c0c-b067-272881b4bad0-image.png
Shut down the VM
8b382ad5-44c6-4c39-b6c6-9c243e31be12-2ab25930-1d3b-4167-8a7e-e6493eb2605e-image.png
Remove the extra CD drive
ad38fa2c-27a1-4086-a47a-63cb639a022b-0f45e200-045f-4ec6-adeb-d171fe7fd768-image.png
Unmount the Windows ISO.
3381d050-c712-44f4-8585-9e9ce1b2afef-c9358d3d-59bc-417f-897f-853e62eaad39-image.png
1801350d-8dca-4fac-a856-2a02ecee61fd-11ecb18b-63f7-4b40-929d-fb8fc80c6e2a-image.png
Start the VM back up and setup the server for the task you installed it for