Mark Minasi's Tech Forum
Sign up Calendar Latest Topics
 
 
 


Reply
  Author   Comment  
Protech

Avatar / Picture

New Friend (or an Old Friend who Built a New Account)
Registered:
Posts: 56
Reply with quote  #1 
Hi Guys,

Things seem to have changed on 2019. I have DSK2VHD'd a physical Servers C: and when trying to boot it attached to a new VM on a 2019 Hyper-V Server the boot fails and this new message appears (see attached). I can read the VHDX file if I mount it in disk management, but any ideas why I can't boot from the VHDX I created? That new "error screen" gives no really indication as to the issue.

( On 2016 and older booting of a VM was much as it has always been. You could watch the VM boot and start and if there were issues at least the good old black and white screen would maybe give a clue. Now that image appears in various forms depending on the issue. I have even seen it appear on new builds because the VM's boot so fast you don't get a chance to "press any key" to boot from a mounted .iso file. )

Cheers

PT

Attached Images
jpeg Capture.jpg (71.15 KB, 7 views)

0
Pieter

Avatar / Picture

Senior Member
Registered:
Posts: 274
Reply with quote  #2 
Hi, try changing the generation version and/or the VM version.
__________________
Pieter Demeulemeester
0
Protech

Avatar / Picture

New Friend (or an Old Friend who Built a New Account)
Registered:
Posts: 56
Reply with quote  #3 
Thanks, I tried that and the solution i found was:

Image the EFI and C partitions only as one VHD (not vhdx) using VSS
Mount image in a G1 VM

PT



0
Previous Topic | Next Topic
Print
Reply

Quick Navigation:

Easily create a Forum Website with Website Toolbox.