@Kptainflintt said in Cloning Windows 11 with vTPM:
No reply to this topic but just seen same thing.
And same "workaround" : disabling vTPM at VM creation from template to avoid crashing.
I can confirm that XOA want to add a second vTPM, any fix ?
Sharing for temporal context: This appears to still be be happening when creating a VM using my custom Windows 11 template (didn't do any cloudbase stuff, just some really basic stuff like updates, then sysprep).
Once I click "Open advanced settings" then toggle "Enable vTPM" into the disabled state, my attempt to create the VM succeeds, and the newly cloned VM has a vTPM with a different UUID. This is literally my first attempt at creating and then cloning a windows 11 template, but it seems to be working.