When the same VHD is used on a virtual machine instead of native boot, all hardware Windows sees is virtual, but the VM sees the VHD as a physical hard disk. Trying to upgrade, user will get this message: This is somewhat illogical booted to VHD, Windows acts as on any physical installation, for instance using real hardware devices, but system still sees the VHD as virtual disk.
However, Windows cannot be upgraded when booted to VHD.
If the on VHD installed Windows 10 edition is the same than Windows edition on host machine, Windows 10 on VHD will be automatically activated. The VHD can then be used as native boot VHD, or on a VM. This takes care of the partitioning, doing it correctly. If you for any reason want to use a GPT partitioned VHD in native boot (can't think any valid reason!), it is better and recommended that you first create a Generation 2 VM in Hyper-V, installing Windows 10 on it. An MBR partitioned VHD is easy to attach to VM, it only needs Windows partition to be marked active, whereas a GPT partitioned VHD with only a single partition for Windows requires manually creating system partitions before it can be used on VM. When creating VHD file to be used in native boot, always use MBR partitioning! To upgrade Windows on native boot VHD, it must be temporarily attached to a virtual machine.
0 kommentar(er)
