Skip to main content

Native boot into VHDX

By

Native boot into VHDX

Why would you boot into VHDX instead of dual booting? Because it is easy(ier) vs adjusting partition post-Windows installation. And the partition layout may not be easy to adjust without using advanced partitioning tool. Also booting into native VHDX gives full access to the hardware without the penalty of virtualization. This allow you to run say other virtuaization on top of native boot!
I prepare VHDX using Hyper-V and once it is ready to my liking I use the VHDX to boot into it. Below are the general steps:

  • Copy a VHDX into the desired location. For example, copy C:\VMs\W21H1M2\Virtual Hard Disks\W21H1M2.vhdx to C:\VMs\NaviteBoot\NaviteBoot.vhdx
  • Mount C:\VMs\NaviteBoot\NaviteBoot.vhdx using File Explorer
  • Note of volume/drive letter for the mounted VHDX, e.g. V:
  • Change directory to V:\Windows
  • Run bcdboot V:\Windows. This should have added the VHDX into the boot options
  • Optional, change the boot description. Get the GUID entry for the just added VHDX. The GUID can be displayed by running bcdedit /v. Look for the GUID that corresponds to the folder location of the VHDX. Then run bcdedit /set like below 
    c:\>bcdedit /set {02e6ec1d-d2c3-11ea-a71f-b3a579503f4b} description “W10VHDX2”

    Where:
    {02e6ec1d-d2c3-11ea-a71f-b3a579503f4b}: was taken from step above
    W10VHDX2: is the label
  • Optional, change boot order. Using the same GUID, run bcdedit /default like below 
    c:\>bcdedit /default {02e6ec1d-d2c3-11ea-a71f-b3a579503f4b}
Now reboot and note that the first entry in the boot sequence is labled W10VHDX2. To delete the entry use msconfig.exe
Labels:

Comments

Post a Comment

Popular posts from this blog

Error! Could not locate dkms.conf file install VirtualBox 4.1.8 on Ubuntu 11.10

By
Tried to update my Ubuntu host today and it did pickup that new version of VirtualBox is available (4.1.8). All other packages installed properly except that VirtualBox installation was complaining about missing dkms.conf file, see error message below. $: sudo /etc/init.d/vboxdrv setup * Stopping VirtualBox kernel modules [ OK ] * Uninstalling old VirtualBox DKMS kernel modules Error! Could not locate dkms.conf file. File: does not exist. [ OK ] * Trying to register the VirtualBox kernel modules using DKMS [ OK ] * Starting VirtualBox kernel modules [ OK ] Though it looks like installation was fine but I am concerned about its effects to VirtualBox functionality. To fix this, do: $: cd /var/lib/dkms/vboxhost $: sudo rm -r 4.1.4 $: sudo /etc/init.d/vboxdrv setup Of course you have to re
11 comments
Read more

The following add-ins could not be started MonoDevelop.GnomePlatform

By
Installing MonoDevelop in OpenSUSE 12.2 from its repository was very easy. When running it for the first time though I got the message: The following add-ins could not be started: The root of the trace shows MonoDevelop.GnomePlatform,2.8 A quick search shows that MonoDevelop depends on libgnomeui . This should have been part of dependencies when installing the application but well.... Below is the screen shot of the error message. References: http://software.1713.n2.nabble.com/MonoDevelop-and-openSUSE-12-1-td7462957.html [2013/04/09] - Same issue observed in OpenSUSE 12.3 and also the same fix. [2014/11/02] - Same issue observed in OpenSUSE 13.3, mondevelop 3.0.6 and the same fix.
21 comments
Read more