Windows 10: Windows fails to boot natively, but can boot in a VM

I have a PC that dual boots Linux and Windows. When booted in Linux, I also boot the Windows install through VirtualBox by passing the disks in directly.


The boot process natively is mobo UEFI -> GRUB -> Windows Boot Loader -> Windows, and the boot process in the VM is vbox UEFI -> GRUB -> Windows Boot Loader -> Windows.


When I try to boot locally, the Windows Boot Loader is loaded and runs with the spinning circle bottom centre for a bit, then BSODs with the error "INACCESSIBLE BOOT DEVICE".


VirtualBox booting the same Windows install continues to boot without issue.


If I try to fix the Windows boot form the Windows recovery menu, it says it's unable to fix the boot issues and C:/Windows/System32/LogFiles/Srt/SrtTrail.txt it says "Unspecified changes to system configuration might have caused the problem." is the root cause.


Trying to reset Windows from within the recovery menu fails as well.


I had been using this native and virtual boot for about 6 months, across many Windows updates without issues.


Soon before the problem occurred, I had deleted a partition on the drive that Windows is installed on. The drive had 4 partitions. 1 was ZFS - Linux data, 2 was LUKS - Linux swap, 3 is "Microsoft Reserved Partition" and 4 is NTFS C:\ for Windows. I deleted partition 2 and didn't touch or move the two Windows partitions, and their partition numbers are unchanged, so I don't see why that would effect it.


I've uninstalled guest additions form Windows from within a virtualized boot, but Windows continues to fail to boot.


I can't really understand what's going on. Both when running in vbox and running natively it's using the same Windows boot loader to boot the same Windows, and the drives are passed through in full to vbox, so how could it not find the boot device natively, but can find it in vbox? It doesn't seem like it can be UEFI related either even though that differs between the two boots because GRUB is chainloading the Windows bootloader in both cases, and GRUB is loading fine.

:)

 

Native boot virtual machine failed to boot

Hello,

I have 2 SSDs in my laptop and each one has Windows 10 installed. I use dualboot menu to select which one to boot.

Now I am trying to use native boot of vhdx. What I did are:

1. use disk2vhd to create vhdx file, select the 2nd SSD(D: drive) and created Windows2.vhdx under folder \VM in the root of 1st SSD.

After VHDX file created, I run disk management and attach the virtual disk, I noticed there are three partition EFI/SYSTEM/Recovery in the VHD.

then I detached the drive.

2. use bcdicex64 to add an boot entry "Windows 10 VM" to boot from vhd.

3. Reboot the computer, select Windows 10 VM, Windows starts to load, after a few seconds, I got STOP error "critical_process_died".

I tried the following after boot failure:

Boot to 1st SSD, attach vhdx in disk management, delete EFI partition and recovery partition. detach vhdx, reboot the computer and choose Windows 10 VM. This time the computer keeps rebooting when the windows starts to load without giving STOP error.

Booting to safemode results same problem.

How to fix the problem? Thanks

 

Windows 10 VHD Native Boot Installation--Officially Supported?

I have done two major upgrades to my VHD boot system now. I get the failed to upgrade message so I do the upgrade in Hyper-V on another system I have. To do it Hyper-V I had to replicate my entire system so that my virtual is dual boot as well. Once this
is setup its just a case of copy the VHD, upgrade, copy it back.

Update (July 2017): I just had to build a new Hype-V VM for upgrading my Native Boot VHD (NBV) to W10 Creators Update. Here are the steps I used.

1. Copied my NBV to a USB attached external drive

2. On a spare machine built a Win10 VM, attached the NBV file to the second IDE controller on the VM, this became drive E:

3. In the VM made a copy of the boot "bcdedit /copy {current} /d "Native boot VHD"

4. Update the boot config copy from above so that device and osdevice point to E:\, good example in the bcdedit help of this.

5. Added detecthal to above boot cfg, bcdedit /set {guid} detecthal on

6. Reboot the VM, select the NBV, it boots to that, let it upgrade, copy the NBV file back to its original location.

Worked for me. Did it all on a USB3 attached external drive, slow but worked. My spare machine running Hyper-V had 4GB, gave 2GB to the VM.

-Wes

 

XP / Vista Duel Boot

http://www.lifehacker.com/software/...-boot-windows-xp-and-windows-vista-179906.php

that is a complete step by step guide.

Hope that helps