Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
VirtualBox fails with "Inaccessible Boot Device" BSOD
#1
Hi,

I was unsuccessful trying to run my WinToUSB stick's image in Virtualbox so far (obviously I don't know how to correctly set it up, for example where to put the boot partition etc.).

So I though let's try the Windows To Go Upgrader because it does exactly what I need, creates a VirtualBox Image from the WinToUSB Stick. So I downloaded it and started the "check for upgrade" with a "Windows 10 Pro (x64)" GPT/UEFI WinToUSB enabled USB Stick. The process starts and creates the VM and tries to start it. At first I see the virtualbox logo and the turning dots at the bottom which everyone knows, but after about 5-10 seconds I get a BSOD saying "UNMOUNTABLE_BOOT_VOLUME". So, question is, whe isn't it able to boot? I'm using Virtualbox 5.1.20.

I would be even be willing to pay if I can boot the WinToUSB image so I can modify it. And it also seems that other people are having also big problem to boot a WinToUSB volume in Virtualbox if you look into the forum threads about WinToUSB.

Any help would be greatly appreciated.

Best regards,

Marc
Reply
#2
(05-13-2017, 12:03 AM)marcelser Wrote: Hi,

I was unsuccessful trying to run my WinToUSB stick's image in Virtualbox so far (obviously I don't know how to correctly set it up, for example where to put the boot partition etc.).

So I though let's try the Windows To Go Upgrader because it does exactly what I need, creates a VirtualBox Image from the WinToUSB Stick. So I downloaded it and started the "check for upgrade" with a "Windows 10 Pro (x64)" GPT/UEFI WinToUSB enabled USB Stick. The process starts and creates the VM and tries to start it. At first I see the virtualbox logo and the turning dots at the bottom which everyone knows, but after about 5-10 seconds I get a BSOD saying "UNMOUNTABLE_BOOT_VOLUME". So, question is, whe isn't it able to boot? I'm using Virtualbox 5.1.20.

I would be even be willing to pay if I can boot the WinToUSB image so I can modify it. And it also seems that other people are having also big problem to boot a WinToUSB volume in Virtualbox if you look into the forum threads about WinToUSB.

Any help would be greatly appreciated.

Best regards,

Marc

Unmountable boot volume error is usually caused by corruption of files on the disk or corruption of the file system, so please make sure that the Windows To Go drive is not damaged and can boot normally then try again.
Thanks.
Free Data Recovery & Windows To Go Creator & UEFI Boot Manager & Windows Deployment Tool
Hasleo Software (formerly called EasyUEFI Development Team)
Reply
#3
(05-13-2017, 04:20 PM)admin Wrote:
(05-13-2017, 12:03 AM)marcelser Wrote: Hi,

I was unsuccessful trying to run my WinToUSB stick's image in Virtualbox so far (obviously I don't know how to correctly set it up, for example where to put the boot partition etc.).

So I though let's try the Windows To Go Upgrader because it does exactly what I need, creates a VirtualBox Image from the WinToUSB Stick. So I downloaded it and started the "check for upgrade" with a "Windows 10 Pro (x64)" GPT/UEFI WinToUSB enabled USB Stick. The process starts and creates the VM and tries to start it. At first I see the virtualbox logo and the turning dots at the bottom which everyone knows, but after about 5-10 seconds I get a BSOD saying "UNMOUNTABLE_BOOT_VOLUME". So, question is, whe isn't it able to boot? I'm using Virtualbox 5.1.20.

I would be even be willing to pay if I can boot the WinToUSB image so I can modify it. And it also seems that other people are having also big problem to boot a WinToUSB volume in Virtualbox if you look into the forum threads about WinToUSB.

Any help would be greatly appreciated.

Best regards,

Marc

Unmountable boot volume error is usually caused by corruption of files on the disk or corruption of the file system, so please make sure that the Windows To Go drive is not damaged and can boot normally then try again.
Thanks.

Please boot into Windows on the USB drive, run chkdsk to scan volume C: and other partitions on the USB drive and to see if there have file system errors. If Yes, fix and try again.

For more infomation about chkdsk,  please visit: 
http://technet.microsoft.com/en-us/library/8f7ffab9-a5e7-4de9-907a-0f172b5a6a4e.aspx
Free Data Recovery & Windows To Go Creator & UEFI Boot Manager & Windows Deployment Tool
Hasleo Software (formerly called EasyUEFI Development Team)
Reply
#4
(05-13-2017, 04:20 PM)admin Wrote:
(05-13-2017, 12:03 AM)marcelser Wrote: Hi,

I was unsuccessful trying to run my WinToUSB stick's image in Virtualbox so far (obviously I don't know how to correctly set it up, for example where to put the boot partition etc.).

So I though let's try the Windows To Go Upgrader because it does exactly what I need, creates a VirtualBox Image from the WinToUSB Stick. So I downloaded it and started the "check for upgrade" with a "Windows 10 Pro (x64)" GPT/UEFI WinToUSB enabled USB Stick. The process starts and creates the VM and tries to start it. At first I see the virtualbox logo and the turning dots at the bottom which everyone knows, but after about 5-10 seconds I get a BSOD saying "UNMOUNTABLE_BOOT_VOLUME". So, question is, whe isn't it able to boot? I'm using Virtualbox 5.1.20.

I would be even be willing to pay if I can boot the WinToUSB image so I can modify it. And it also seems that other people are having also big problem to boot a WinToUSB volume in Virtualbox if you look into the forum threads about WinToUSB.

Any help would be greatly appreciated.

Best regards,

Marc

Unmountable boot volume error is usually caused by corruption of files on the disk or corruption of the file system, so please make sure that the Windows To Go drive is not damaged and can boot normally then try again.
Thanks.

Of course I did this already. The USB stick itself boots perfectly and has no errors, but still doesn't boot in Virtualbox when the VM is created from WinToGoUpgrader. I think it has something to do with the fact that the vhd file which the UsbToWin media is created from only contains the OS partition but no recovery nor EFI partitions because it is a copy of the system partition as a vhd disk from some backup some time ago. It seems this can be booted perfectly from the USB Stick made by WinToUSB but not with how the Virtualbox image from WinToGoUpgrader.

I think that's the case because I did a lot of testing after my forum post and I found out the following: I created a new empty vm in Virtualbox and installed Win10 Pro into it from installation DVD. Once installed I created a new WinToUSB version on my stick (so I replaced the existing one which won't boot in WinToUpgrader) from this newly created win10 pro vm disk . When I use this USB stick and run WinToGoUpgrader it creates a vm that just boots fine. But this time the originating vhd file which was used to created the WinToUSB media contained a recovery, efi & system partition in the disk. So I repeated my previous step and created a new WinToUSB installation again from the vhd disk which just contains the OS partition and it failed again when trying to use it in WinToGoUpgrader with the same error UNMOUNTABLE_BOOT_DEVICE.

It seems that WinToGoUpgrader definitly needs some improvement so also WinToUSB imgaes with vhd images without efi/recovery partitions contained in them can be booted not only disks that contain this, or maybe you must modify the supplied vhd image in WinToUSB inserting any missing partitions when creating the WinToUSB Media.

Best regards,

Marc

PS: Once I get a big enough USB stick I might try to create a USB stick from my existing windows partition and check how the created vhd disk looks like. Do you also copy the recovery/efi partition into it or not?
Reply
#5
(05-13-2017, 04:56 PM)marcelser Wrote:
(05-13-2017, 04:20 PM)admin Wrote:
(05-13-2017, 12:03 AM)marcelser Wrote: Hi,

I was unsuccessful trying to run my WinToUSB stick's image in Virtualbox so far (obviously I don't know how to correctly set it up, for example where to put the boot partition etc.).

So I though let's try the Windows To Go Upgrader because it does exactly what I need, creates a VirtualBox Image from the WinToUSB Stick. So I downloaded it and started the "check for upgrade" with a "Windows 10 Pro (x64)" GPT/UEFI WinToUSB enabled USB Stick. The process starts and creates the VM and tries to start it. At first I see the virtualbox logo and the turning dots at the bottom which everyone knows, but after about 5-10 seconds I get a BSOD saying "UNMOUNTABLE_BOOT_VOLUME". So, question is, whe isn't it able to boot? I'm using Virtualbox 5.1.20.

I would be even be willing to pay if I can boot the WinToUSB image so I can modify it. And it also seems that other people are having also big problem to boot a WinToUSB volume in Virtualbox if you look into the forum threads about WinToUSB.

Any help would be greatly appreciated.

Best regards,

Marc

Unmountable boot volume error is usually caused by corruption of files on the disk or corruption of the file system, so please make sure that the Windows To Go drive is not damaged and can boot normally then try again.
Thanks.

Of course I did this already. The USB stick itself boots perfectly and has no errors, but still doesn't boot in Virtualbox when the VM is created from WinToGoUpgrader. I think it has something to do with the fact that the vhd file which the UsbToWin media is created from only contains the OS partition but no recovery nor EFI partitions because it is a copy of the system partition as a vhd disk from some backup some time ago. It seems this can be booted perfectly from the USB Stick made by WinToUSB but not with how the Virtualbox image from WinToGoUpgrader.

I think that's the case because I did a lot of testing after my forum post and I found out the following: I created a new empty vm in Virtualbox and installed Win10 Pro into it from installation DVD. Once installed I created a new WinToUSB version on my stick (so I replaced the existing one which won't boot in WinToUpgrader) from this newly created win10 pro vm disk . When I use this USB stick and run WinToGoUpgrader it creates a vm that just boots fine. But this time the originating vhd file which was used to created the WinToUSB media contained a recovery, efi & system partition in the disk. So I repeated my previous step and created a new WinToUSB installation again from the vhd disk which just contains the OS partition and it failed again when trying to use it in WinToGoUpgrader with the same error UNMOUNTABLE_BOOT_DEVICE.

It seems that WinToGoUpgrader definitly needs some improvement so also WinToUSB imgaes with vhd images without efi/recovery partitions contained in them can be booted not only disks that contain this, or maybe you must modify the supplied vhd image in WinToUSB inserting any missing partitions when creating the WinToUSB Media.

Best regards,

Marc

PS: Once I get a big enough USB stick I might try to create a USB stick from my existing windows partition and check how the created vhd disk looks like. Do you also copy the recovery/efi partition into it or not?

Thank you for your information. Unfortunately, we can't reproduce the problem in our test environment, and we don't think efi/recovery partitions are not the cause of this problem, because this problem is only occurring in your environment so far.

Could you take a screenshot of the BSOD and send it to us? Maybe we can offer you some advice on how to solve it.
Free Data Recovery & Windows To Go Creator & UEFI Boot Manager & Windows Deployment Tool
Hasleo Software (formerly called EasyUEFI Development Team)
Reply
#6
I meanwhile solved the issue by making a copy of the working win10 disk test installation and by replacing the contained win10 os parition with the OS partition from the vhd which doesn't boot inside virtualbox. So I have now a vhd disk which contains proper efi/recovery/bcd setup plus the backed up OS partition from the non-working vhd disk and now it boots perfectly in virtualbox. That's why I think it surely has something to do if there's a proper efi/recovery etc. setup inside the vhd disk. An interesting test would be to expand the non-working vhd drive and do it vice versa, so copying efi/msr partitions to non-working vhd and see if it boots as well but I think I'm lazy and won't test this.
Reply
#7
I am a little confused. Could you tell us the BSOD is 'Inaccessible Boot Device' or ‘UNMOUNTABLE_BOOT_DEVICE’? And we will do more tests on it.
Thank you very much.
Free Data Recovery & Windows To Go Creator & UEFI Boot Manager & Windows Deployment Tool
Hasleo Software (formerly called EasyUEFI Development Team)
Reply
#8
it's UNMOUNTABLE BOOT DEVICE not INACCESSIBLE BOOT DEVICE
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)