Howto Restore ImageforWindows inside VirtualBox?

[amccombs]

Windows 10, UEFI, USB, TBWinRE, VirtualBox, ImageforWindows

My main goal is to Restore ImageforWindows inside VirtualBox. I am thinking to boot off the recovery USB inside VirtualBox then restore the Backup.

I used these directions to create a recovery USB, and the USB works fine when booting it off the laptop
https://www.terabyteunlimited.com/howto ... torial.htm

Now, has anyone successfully saved that USB to an ISO file so that I can boot it in VirtualBox and get the pretty ImageForWindows screen so that I can Restore and ImageForWindowsBackup?
All I get now is a screen that shows UEFI Interactive Shell v2.1 with a Shell> prompt
I have already tried many ways, so please do not guess on how it could be done.

Thank you.

[TeraByte Support(PP)]

I use the TBWinRE ISO quite often in VMware Workstation and it boots up fine (both BIOS and UEFI modes).

Did you create the TBWinRE ISO file directly using the MakeDisk utility?

Have you successfully booted any other UEFI ISO files in VirtualBox?

If VirtualBox allows switching BIOS modes you could try changing to Legacy (MBR-type) mode and see if it works that way. Remember to switch back to UEFI mode to boot Windows.

[TeraByte Support]

you can restore on the host system directly as a .vmdk file as well.

as far as booting, check your boot order in the vm bios.

"amccombs" wrote in message news:16641@public.image...

Windows 10, UEFI, USB, TBWinRE, VirtualBox, ImageforWindows

My main goal is to Restore ImageforWindows inside VirtualBox. I am thinking
to boot off the recovery USB inside VirtualBox then restore the Backup.

[amccombs]

Where do I get the TBWinRE ISO file?

I did not directly use the MakeDisk, I just followed the pretty screen captures in the link I posted.

This is the only UEFI disk that I have, so no I have not successfully booted any other UEFI ISO file as I don't have an ISO file.

I don't see a place in VirtualBox for MBR vs UEFI.

Can VMware and VirtualBox live on the same computer or do they both fight over Hyper-V?

Thank you,

TeraByte Support(PP) wrote:
> I use the TBWinRE ISO quite often in VMware Workstation and it boots up
> fine (both BIOS and UEFI modes).
>
> Did you create the TBWinRE ISO file directly using the MakeDisk utility?
>
> Have you successfully booted any other UEFI ISO files in VirtualBox?
>
> If VirtualBox allows switching BIOS modes you could try changing to Legacy
> (MBR-type) mode and see if it works that way. Remember to switch back to
> UEFI mode to boot Windows.

[amccombs]

I tried to boot off a .vmdk that was created from a restored file, however I only get the Window logo for 12+ hours.
Probably because the HAL is different, VirtualBox has scripts to change the HAL for Windows XP, which I found out the hard way does not work for Windows 10. I can't find any scripts for changing the HAL in Windows 10.vmdk files.

Boot order, new blank hard disk in VirtualBox, won't do anything.

-Thank you

TeraByte Support wrote:
> you can restore on the host system directly as a .vmdk file as well.
>
> as far as booting, check your boot order in the vm bios.
>
> "amccombs" wrote in message news:16641@public.image...
>
> Windows 10, UEFI, USB, TBWinRE, VirtualBox, ImageforWindows
>
> My main goal is to Restore ImageforWindows inside VirtualBox. I am thinking
>
> to boot off the recovery USB inside VirtualBox then restore the Backup.

[TeraByte Support(PP)]

amccombs wrote:
> Where do I get the TBWinRE ISO file?
>
> I did not directly use the MakeDisk, I just followed the pretty screen captures in
> the link I posted.

After you create the TBWinRE build, the last step runs the MakeDisk utility to create the boot media. You would select the option to create an ISO file in MakeDisk. Since you have already created the build you can just run MakeDisk (makedisk.exe) in the TBWinRE folder and create the ISO file (no need to recreate the build unless you've made changes).

> Can VMware and VirtualBox live on the same computer or do they both fight over
> Hyper-V?

It's not a scenario I've tried, but Hyper-V most likely would need to be completely disabled.

Note that there is also the TBOSDT copyp2v.tbs script that may work for you. It can restore the image to a .vmdk/.vhd file, but also tweaks things for a VM.

[amccombs]

That MakeDisk made the iso, Thank you.

I did the restore, however when I attempt to boot it said "FATAL: No bootable medium found! System halted."

The attached Lenovo_disk shows the disk layout from Computer Management, it shows 4 partitions, 117GB partition being Boot.
[attachment=1]Lenovo_13_disk_2.jpg[/attachment]

The attached Lenovo_13_Disk_Restore shows Image for Windows, 5 partitions to restore, however it shows the system 100MiB being **active**, shouldn't the Windows 120759MiB be *active*?
[attachment=0]Lenovo_13_Disk_Restore.jpg[/attachment]

I assume that if the HAL or drivers were wrong I would get a BSOD instead of the current error about no bootable medium found. *If I assumed correctly, how would I change the active partition within TBLauncher, is it one of the scripts in TeraByte OSD Tool?

I found that TBOSDT copyp2v.tbs script video, I want to make sure that the correct partition is active first before removing drivers/changing HAL.

-Thank you

[amccombs]

I used the OSDTOOL Script:
1. removed all drivers, however that still failed to boot
2. changed HAL to halextintclpiodma.dll, however that still failed to boot
3. changed HAL to halextpl080.dll, however that still failed to boot
4. diskpart wont let me make partition 4 active because it is not a MBR

TBLauncher > System Recovery Options > Troubleshoot > Advanced Options > Startup Repair = couldn't repair your PC

[Bob Coleman]

I haven't completely followed this from the beginning. Is what you're trying to boot from a GPT disk or emulating a GPT disk? If so, the 100 MiB partition is probably the EFI partition and probably should be the active partition.

[TeraByte Support(PP)]

You shouldn't need to change the HAL and or set any partition active since it's GPT. Also, did you try using the copyp2v.tbs script or only using the osdtool.tbs script.

The error you're getting sounds like the VM itself is not seeing the boot drive or booting settings are incorrect (you're not getting a Windows boot error, for example). Are you sure the VM is configured correctly?