VM Upload Challenge: Windows Server 2016 Boot Issue

Hi everyone!

I want to upload a virtual machine from an on-premise system under VMware to Netcup. Since support doesn't want to help me, I hope the community can help me.

Following problem:

Windows Server 2016. I uninstalled the VMware tools, installed the Windows VirtIO Drivers via an exe file and, just to be on the safe side, added all the necessary drivers again as legacy hardware in Windows. Then uploaded the VM via Veeam Bare Metal Recovery and added the SCSI drivers in the recovery process. Unfortunately the VM doesn't boot up and always goes into Windows System Restore.

The hard drive is not visible in Diskpart at first. Only after I found out that I could load the drivers via drvload drv.inf did the hard drives appear in Diskpart. Then I leave the recovery CMD and click Continue Start, but Windows hangs again and it just doesn't work any further.

Has anyone ever had a similar task?

(Translated via Google Translator)

Best regards

Zitat von H6G

Have you unlocked the bootloader?

https://superuser.com/questions/1057…-disk-to-virtio

Thank you for your quick answer. But when I enter the bcdedit command it says that the configuration data cannot be find because the system doesnt find the file.

Do you have a fix for this?

Tried this on every letter.

pasted-from-clipboard.png

EDIT:
Nevermind, I think i crashed the hard drive completely :')
pasted-from-clipboard.png

Gonna reupload the OS and try it again

Zitat von H6G

You can omit the "{current}", maybe it works then.

Already did :')

Zitat von H6G

Was the first screenshot from VMware or the rescue system?

I think it needs to be applied on the source, when you install the drivers.

The first screenshot is on the rescue system. This rescue system where windows boots into when a boot is not possible, where you can restore an image, do startup help and so on. It doesnt matter if I boot the rescue system from the recovered hard drive or a mounted windows server iso file.

What do you mean with it needs to be applied on the source? Even before taking the initial backup on my VMware system?

Zitat von H6G

In that case it will probably take the bcd of the recovery system and you need to say which bcd you want to edit.

I've always unlocked the bootloader on the source system, before copying to the target system.

But there might be some parameter for bcdedit to edit the right one - but don't ask me how to figure that out.

I'm not sure how did I get there, but there seems that in IDE-Mode Windows is able to load something:

pasted-from-clipboard.png

Now I noticed there is a wrong device entry in windows start manager (left old machine, right the cloned vm). Not sure if this is normal. But it changed back after a reboot
pasted-from-clipboard.png

After xcopy c:\windows\system32\config\regback c:\windows\system32\config from https://www.diskpart.com/de/articles/ge…lationen-0.html windows comes to load some other (?) devices about 20 Minutes and got up then!!!
pasted-from-clipboard.png

Cleaned up the Device Manager and got a running system