Windows 10: proxmox

I have recently installed Proxmox on my home server, and after that, I installed Windows 11 as my main VM.unfortunately, I'm not able to activate it with my Microsoft account.I believe the reason is that the UUID is changed for sure.so my question is, is there any way around this?Is it possible to contact Microsoft support so they can provide my UUID so I can add it to my VM settings?

:)

 

How do I move my Windows installation into a VM, in my case Proxmox?

I bought Windows 10 many years ago, installed it, and upgraded it to Windows 11. A couple of months ago got a new computer, and I could reactivate the license letting the system know I had a new computer.

I made a test installation of Proxmox on this new machine, and installed Windows as a VM. However, it didn't want to activate. Saying I have new hardware didn't help, but I do. I have better hardware now which prompted me to try out Proxmox with a lot of Linux VMs on it. It's just about one Windows VM for games, the rest is Linux for work and hobby.

So, what do I need to do to make my Windows 11 activate under Proxmox as a VM?

 

why the platform role is desktop when I run Windows 10 as a guest OS in a hypervisor (Proxmox)

HI team,

My host is running Proxmox (a hypervisor), and there is a Windows 10 VM runs inside Proxmox.

I found the platform role is Desktop in the "System Information" (run msinfo32).

I don't understand that as my Windows 10 is a VM, so the platform role should be "Virtual Machine".

How to change the platform role manually by changing some setting? e.g registry.

anyone can help please?

Thanks in advance.

BR

 

capture WIM image of KVM W10 VM for convert to physical (V2P)

Hi folks

@Hopachi one for you as well to try out !!!

I've got a great running W10 KVM virtual machine running with all the software working etc -- so I would like to capture the WIM image via DISM. Also I'd like all the software etc on a Windows ISO so I don't have to re-install again on a new machine.

The main problem of course is that the Windows ISO (whether you create it from UUPDUMP or MCT won't have the KVM VIRTIO drivers so won't recognize the disk your VM is stored on so can't capture the image.

Pre condition or step 0 . You should convert the Windows Virtual hard disk from QCOW2 to RAW format first if your HDD is in QCOW2 format and install the VIRTIO disk drivers if not already done. RAW always works better BTW. This is easily done via img-convert in QEMU and check that the W10 VM boots. Also ensure any data etc is solely on the Windows partition / virtual disk --same as for capturing a WIM image on a Real physical machine.

So step 1 is to Slipstream the VIRTIO drivers into the Windows install ISO.

That's done by following this excellent link -- just ignore all the proxmox stuff -- we only want to slipstream the drivers into the ISO so that we can capture the WIM image of the running Virtual Machine !!!!!.

GitHub - Zer0CoolX/proxmox-windows-slipstream-virtio-drivers: Step-by-step guide to slipstream VirtIO drivers into Windows ISO's for use in Proxmox VE

Now you can boot the ISO in your Virtual machine , get into command mode and capture the WIM via Kari's excellent tutorial.

Have fun folks !!!

Cheers
jimbo