After 24H2 I can no longer install W11 Virtual Machine?!

I tried to install another W11Pro in VirtualBox and Hyper-V and they both said that the system would not support W11? Well I have windows 11 Pro as my base os and it works fine. I have also installed other Virtuals without problem. Although, I updated to 24H2 yesterday...any ideas?

In Hyper-V, vhdx file needs to be at least 64GB, TPM enabled and a minimum number of 2CPU cores set. The latter one is one that often catches people out.

Also it must be a gen 2 vm.

cereberus said:

In Hyper-V, vhdx file needs to be at least 64GB, TPM enabled and a minimum number of 2CPU cores set. The latter one is one that often catches people out.

Also it must be a gen 2 vm.

Click to expand...

Hey cereberus, but that is all correct and I just tried a Quick Create and got the same error. Any other thoughts?

Doyler said:

I tried to install another W11Pro in VirtualBox and Hyper-V and they both said that the system would not support W11? Well I have windows 11 Pro as my base os and it works fine. I have also installed other Virtuals without problem. Although, I updated to 24H2 yesterday...any ideas?

Click to expand...

Did you get any error message / event log etc of what the problem was -- I suspect two areas here that might be a problem -- secure boot not enabled on the VM in its config or on the host machine, and lack of an EFI partition on the Guest's Virtual disk.

@cereberus - have you managed to install a Windows guest on Hyper-V from a vhdx file (native) -- I just don't see how the Hypervisor can boot the VM without a bootloader - even if the hypervisor can natively read vhdx files.

I haven't been able to make it work yet -- I've done it via the old "Classical way" of creating a Guest virtual disk drive with an EFI partition on it and the vhdx windows file (easier to test with a single vhdx file) , attaching it as a vdisk, assigning a volume letter and installing the bootloader on the "virtual" efi partition -- but if you can do the whole kybosh from the vhdx file -- !!!

Cheers
jimbo

jimbo45 said:

@cereberus - have you managed to install a Windows guest on Hyper-V from a vhdx file (native) -- I just don't see how the Hypervisor can boot the VM without a bootloader - even if the hypervisor can natively read vhdx files.


Cheers
jimbo

Click to expand...

Dead easy with Macrium Reflect.

1) clone host EFI partition on windows Host on to small blank vhdx.

2) Boot vm to Macrium Reflect iso, with efi vhdx and separate native boot vhdx attached

3) Use Reflect "fix windows boot issue" option

4) Restart vm, removing Macrium Reflect iso.


Alternatively, slightly harder as you need to use mess around with partitions but you end up with only 1 vhdx drive.

1) Make image backup of EFI on host PC using Macrium Reflect

2) Mount native boot vhdx on host, shrink C drive slightly and restore host EFI to native boot vhdx. EFI can be after C drive, or you can move around with minitool to get efi in front of E Drive.

3) Boot vm to Macrium Reflect iso, with vhdx attached

4) Use Reflect "fix windows boot issues" option.

5) Restart vm, removing Macrium Reflect iso.

In either case, vhdx can be natively booted or vm booted.

cereberus said:

Dead easy with Macrium Reflect.

1) clone host EFI partition on windows Host on to small blank vhdx.

2) Boot vm to Macrium Reflect iso, with efi vhdx and separate native boot vhdx attached

3) Use Reflect "fix windows boot issue" option

4) Restart vm, removing Macrium Reflect iso.


Alternatively, slightly harder as you need to use mess around with partitions but you end up with only 1 vhdx drive.

1) Make image backup of EFI on host PC using Macrium Reflect

2) Mount native boot vhdx on host, shrink C drive slightly and restore host EFI to native boot vhdx. EFI can be after C drive, or you can move around with minitool to get efi in front of E Drive.

3) Boot vm to Macrium Reflect iso, with vhdx attached

4) Use Reflect "fix windows boot issues" option.

5) Restart vm, removing Macrium Reflect iso.

In either case, vhdx can be natively booted or vm booted.

Click to expand...

Thanks
Will give it a go.


Cheers
jimbo