New VM won't boot

Here's the issue I'm having with trying to create a working VM on machine "B":

Machine "A" the source:
Multiboot machine with Win10 Pro, Win7 Pro, and Linux Mint. Each OS is installed on a separate drive. Its working fine with no problems. I am able to run all three systems. The multiboot menu is the Metro style.

Machine "B" the host:
Win10 Pro with Hyper-V

What I am trying to do is to create a VM ON Machine "B" of the Win7 Pro OS FROM Machine "A". Here's what I have done so far:

Created a vhdx of the Win7 OS disk on Machine 'A" using Disk2VHD, moved it to Machine "B" and created a VM. It did not run. It failed to a black screen with "A disk read error occurred. Press CTRL+ALT+DEL to restart"

Used Macrium ivBoot from a backup image file of the Win7 OS disk from Machine "A" and it failed as well saying "An operating system wasn't found. Try disconnecting any drives that don't contain an operating system -

Press CTRL+ALT+DEL to restart."

Created a vhdx's of the of the System Reserved partition and the Win7 OS disk on Machine "A" and attached both to a new VM on Machine "B". That booted to a Recovery screen that said your PC needs to be repaired. A required device isn't connected or can't be accessed Error code: 0x000000f. It had the usual options. (Enter, F8, and F9). Pressing F8 displayed a different error indicating a required file couldn't be loaded because it was missing or contained errors, File \Windows\system32\winload.exe Error code 0x0000225. Pressing F9 brought up the black Windows Recovery console.

Lastly I created a vhdx of the Win10 disk (with the System Reserved partition) and one of the Win7 OS disk and created a VM with them. When run I could select Win10 from the boot menu and it ran fine but when Win7 was selected nothing happened. I am very surprised this did not work.

I think I've reach my appropriate level if incompetency so an further assistance would be greatly appreciated.

Hi jimbo45 and thanks for your reply. I’m afraid my inital post wasn’t clear. Let me clarify what I’m trying to do. I’m trying to take a VHDX made FROM Win7 on a multboot machine and use it to create a VM on another Win 10 machine with Hyper-V. Seems that nothing I do can get the Win7 VM to successfully boot. I’ve tried using a Win7 install disk to do a repair of the boot files on the Win7 VM but that’s been unsuccessful. I’m stumped.

BTW I’ve gone back and corrected my initial post for clarity.

See this tutorial, in case you use Disk2VHD on a UEFI machine with GPT partitioning, there are some additional steps to be taken before you can use the VHD on Hyper-V: Hyper-V - Create and Use VHD of Windows 10 with Disk2VHD | Tutorials

Kari

Thanks for all of the responses. Some of the suggests I've already tried and one I'm not sure I understand so I thought I'd go back an rewrite my initial post to include some additional information and some of the things I've tried.

muchomurka said:

"File \Windows\system32\winload.exe Error code 0x0000225"

...seems that loader from Win10 System Partition has wrong path to Win7 OS.

- do not mix System and OS partition into one VHD file, create two ones
- both the VHDs must be connected in the right order as in source PC
- in VM bios should be set correct boot order

If the problem persists, boot from recovery media & fixboot and/or bcdedit /create may be needed.

thanks muchomurka, I’ll go through your suggestions later this afternoon. BTW the system partition and the os are in fact two separate vitrual disks. I assume they both should be attached to the same controller with the system one first. I’ll need to learn how to set the boot order in Hyper-V. Never done that before. I’ll report back in a few hours.

UPDATE:
No success but here's what I did:
I made sure that the two VHDs were attached in the same order as on the original machine with the system partition ahead of the OS. I made sure that were on the same IDE controller and they were set at the top of the boot order.

It booted up to the Recovery screen with the same error as before

File \Windows\system32\winload.exe Error code 0x0000225". Next a booted to the Win7 installation DVD and ran the automatic repair. After much testing it gave me this

I search for an answer and learned that a patch might be preventing the system from starting. I tried using DISM.exe /image:d:\ /cleanup-image /revertpendingactions. It completed successfully but unfortunately it did not help.
Any further thoughts?