📎 AI Summary:
The original poster, Blutarsky, seeks help with boot issues after migrating a Windows Server 2012 R2 VHD to Hyper-V 2019, experiencing a failure to start due to a potential boot sector problem. A suggested fix involves using a recovery environment, like repair mode, to repair the master boot record (MBR). Another user briefly recommends starting the PC without the drive and then entering setup, while Blutarsky confirms that they successfully resolved the issue by following a referenced article. The overall tone is problem-solving and resolution-focused.

Blutarsky

Extraordinary Member
Member details
Joined
Sep 25, 2010
Messages
68
Thread Author #1
Hello there, I am aware this is the Windows 8 discussion forum, however my question relates as the issue occurs on a VHD which was created from a Windows 2012 R2 disk (which in turn, is a Windows 8 "server" version)
Basically I wanted to migrate a physical Windows 2012 R2 server as a VM, to be hosted on a Hyper-V core server.

Steps I have followed:

1) Created a VHD from existing Windows 2012 R2 machine
2) Installed Hyper-V 2019 core
3) Copied the VHD file to the the Hyper-V machine
3) Created a new VM, using the VHD created in step 1

When attempting to boot, an error is thrown:

"Windows failed to start. A recent hardware or software change might be the cause. The boot selection failed because a required device is inaccessible."
2.png


The VHD image is fine (as it can be mounted and the content shows correctly), however I guess for some reasons the boot sector is corrupted.
This is how the converted disk appears when mounted (surrounded by the red box):

An image from 'Error 0x0000225 when booting VHD'. Disk Management showing two disks: Disk 0 (50 GB) and Disk 1 (931 GB) with partitions.



What steps should I try to fix this? Of course I can add to the VM an iso containing the Windows 2012 R2 setup CD and enter repair mode, then should I try to fix and rebuild the MBR?
 

Last edited by a moderator: