You don't need to undo the previous command, both are required, the first added boot files to the EFI partition of the VHD and the second added a boot entry to your current boot loader. You could try sysprepping the VHD, this may avoid the error (but this also means you need to literally start fresh as you need to boot into that VHD first to even sysprep it). Did you even see if the original VHD boots on the source PC to begin with? (bcdboot X:\Windows where X:\ is the mounted VHD in windows to add it to your boot loader). Just to clarify but i know as much as you about this, while I do vhd booting, i never used Disk2VHD, i never converted from mbr>GPT before and neither did i ever transfer my VHD to another PC.
That is why I kept asking if and how VHD's store or dont store DRIVERS and you guys said it is irrelevant question. Original OS Boots, but I did not check VHD on Original Laptop as I had no way of making VHD boot on old laptop. I had removed SSD from Old Thinkpad, connected it to Toshiba laptop via USB 3.0 and done Disk2VHD on it. And these output VHD I tested inside Hyper-V to ensure it was running without issue. ..Not sure what you mean with the last line I am wondering if I should try the "MBR > GPT VHD" in a VM? Hyper V is not taking it due to Gen 1 / Gen 2 issues and I am wondering if I should test it in VMWare. PS: That is why I kept asking whether and how Disk2VHD or generally VHD's store or dont store OLD DRIVERS, GENERALIZED drivers, NEW drivers.
How would it be possible for me to run a Repair from a Windows Installation Disc on this VHD? Would it have to be via a VM or can it be done via Native Boot (I can boot ISOs) using a Zalman VE 200.
You can mount the VHD in the setup in your command prompt via Diskpart (please use some google-fu if you don't understand) to repair etc. Code: diskpart select vdisk file=X:\w8.vhd attach vdisk assign letter=Z
Yeah but the repair should be from a Win 7 Rescue or Install Disk? I am guessing I should be doing it from Win 8?
That is what I posted above. Scroll down in the code for the BLUE sections. It starts booting and then freezes at the logo.Even when trying safeboot it gets stuck. Wondering if this is a UEFI/BootBCD issue or a Windows related issue. Code: Firmware Boot Manager--------------------- identifier {fwbootmgr} displayorder {bootmgr} {a26d1a53-1770-11e4-826a-806e6f6e6963} {a26d1a54-1770-11e4-826a-806e6f6e6963} {144053b4-1bb4-11e4-8271-806e6f6e6963} {144053b5-1bb4-11e4-8271-806e6f6e6963} {144053b6-1bb4-11e4-8271-806e6f6e6963} timeout 2 Windows Boot Manager -------------------- identifier {bootmgr} device partition=\Device\HarddiskVolume2 path \EFI\Microsoft\Boot\bootmgfw.efi description Windows Boot Manager locale en-us inherit {globalsettings} default {default} resumeobject {7f94b955-16ce-11e4-8265-7c7a91e559f1} displayorder {default} {current} toolsdisplayorder {memdiag} timeout 30 Firmware Application (101fffff) ------------------------------- identifier {144053b4-1bb4-11e4-8271-806e6f6e6963} description UEFI:CD/DVD Drive Firmware Application (101fffff) ------------------------------- identifier {144053b5-1bb4-11e4-8271-806e6f6e6963} description UEFI:Removable Device Firmware Application (101fffff) ------------------------------- identifier {144053b6-1bb4-11e4-8271-806e6f6e6963} description UEFI:Network Device Firmware Application (101fffff) ------------------------------- identifier {a26d1a53-1770-11e4-826a-806e6f6e6963} description UEFI: IP4 Realtek PCIe GBE Family Controller Firmware Application (101fffff) ------------------------------- identifier {a26d1a54-1770-11e4-826a-806e6f6e6963} description UEFI: IP6 Realtek PCIe GBE Family Controller Windows Boot Loader ------------------- identifier {current} device partition=C: path \Windows\system32\winload.efi description Windows 8.1 locale en-US inherit {bootloadersettings} recoverysequence {3c2efe44-f665-11e3-8256-6002922507b4} integrityservices Enable recoveryenabled Yes isolatedcontext Yes allowedinmemorysettings 0x15000075 osdevice partition=C: systemroot \Windows resumeobject {1fc12a3c-f66d-11e3-8657-6002922507b4} nx OptIn bootmenupolicy Standard hypervisorlaunchtype Auto Windows Boot Loader ------------------- identifier {3c2efe44-f665-11e3-8256-6002922507b4} device ramdisk=[\Device\HarddiskVolume1]\Recovery\WindowsRE\Winre.wim,{3c2efe45-f665-11e3-8256-6002922507b4} path \windows\system32\winload.efi description Windows Recovery Environment locale en-us inherit {bootloadersettings} displaymessage Recovery osdevice ramdisk=[\Device\HarddiskVolume1]\Recovery\WindowsRE\Winre.wim,{3c2efe45-f665-11e3-8256-6002922507b4} systemroot \windows nx OptIn bootmenupolicy Standard winpe Yes Windows Boot Loader ------------------- identifier {default} device vhd=[C:]\MIGRATION\D164\SSD_P1.VHD path \Windows\system32\winload.efi description Windows 7 locale en-us inherit {bootloadersettings} osdevice vhd=[C:]\MIGRATION\D164\SSD_P1.VHD systemroot \Windows resumeobject {7f94b955-16ce-11e4-8265-7c7a91e559f1} nx OptIn detecthal Yes Resume from Hibernate --------------------- identifier {1fc12a3c-f66d-11e3-8657-6002922507b4} device partition=C: path \Windows\system32\winresume.efi description Windows Resume Application locale en-US inherit {resumeloadersettings} recoverysequence {3c2efe44-f665-11e3-8256-6002922507b4} recoveryenabled Yes isolatedcontext Yes allowedinmemorysettings 0x15000075 filedevice partition=C: filepath \hiberfil.sys bootmenupolicy Standard debugoptionenabled No Resume from Hibernate --------------------- identifier {7f94b955-16ce-11e4-8265-7c7a91e559f1} device vhd=[C:]\MIGRATION\D164\SSD_P1.VHD path \Windows\system32\winresume.efi description Windows Resume Application locale en-us inherit {resumeloadersettings} filepath \hiberfil.sys Windows Memory Tester --------------------- identifier {memdiag} device partition=\Device\HarddiskVolume2 path \EFI\Microsoft\Boot\memtest.efi description Windows Memory Diagnostic locale en-us inherit {globalsettings} badmemoryaccess Yes EMS Settings ------------ identifier {emssettings} bootems Yes Debugger Settings ----------------- identifier {dbgsettings} debugtype Serial debugport 1 baudrate 115200 RAM Defects ----------- identifier {badmemory} Global Settings --------------- identifier {globalsettings} inherit {dbgsettings} {emssettings} {badmemory} Boot Loader Settings -------------------- identifier {bootloadersettings} inherit {globalsettings} {hypervisorsettings} Hypervisor Settings ------------------- identifier {hypervisorsettings} hypervisordebugtype Serial hypervisordebugport 1 hypervisorbaudrate 115200 Resume Loader Settings ---------------------- identifier {resumeloadersettings} inherit {globalsettings} Device options -------------- identifier {3c2efe45-f665-11e3-8256-6002922507b4} description Windows Recovery ramdisksdidevice partition=\Device\HarddiskVolume1 ramdisksdipath \Recovery\WindowsRE\boot.sdi
On a side note (I'd like to try this on the side). What would be the fastest way to get a guinea pig Bare naked Win 7x64 .VHD (UEFI and BIOS) to test drive and Native Boot? Download from somewhere or create it myself using some guide (do point).
You could create one using Virtualbox. Virtualbox supports VHDs natively so in theory you could create a VHD, install Windows on it and test it.
Wait a moment, shouldn't the following line be: path \Windows\system32\winload.efi path \Windows\system32\winload.exe Assuming you haven't converted your original VHD to EFI.
The source system for the VHD was MBR/BIOS machine. It worked fine under Hyper-V on Destination machine i.e. GPT/UEFI. But I am told that for it to native boot on destination machine it has to be converted to GPT and UEFI boot info added to it. I havent made any specific boot name / file changes. It is what it is.. Does it have to be winload.exe versus winload.efi ?? I don't know. It boots to the Windows Logo.. and in safe boot it goes upto classpnp.sys. So I am not sure if its a VHD/UEFI boot issue or issue with drivers of the migrated windows system. It was fine before MBR > GPT conversion (as it ran in Hyper-V). I was trying to find a way to TEST IT / make it work in Hyper-V after, but Hyper-V only accepts VHDX (not good for Win7) for Gen-2 (UEFI) and Gen-1 for VHD. I might try this one time with VMWare.