The system is set to boot using UEFI with security enabled
Upon boot from the USB drive I get some encouraging progress and then a fatal error with the message (paraphrasing) that the winload.efi file has an invalid signature and the system cannot boot.
Alternate method…fails differently
If I turn off secure boot and use Legacy instead of UEFI, I can get the Full Restore Wizard, can install the drivers and the Wizard appears to find my Realtek PCIe GBE Family Controller. But when I continue, the Wizard cannot find my DX4000 on the network, by name or IP address.
Any obviously wrong things I’m doing? Thanks so much for your help.
You will have to be booted uEFI to do the restore but security disabled.
You can hold down ctrl-alt-shft and get a cmd prompt in this restore thing and do ipconfig to see if it really loaded the network drivers
make a fat bootable thumb and copy the files to it should boot
when do you get the winload error and what is it exactly?
Thanks so much, Gramps. The KB2781274 patch is applied, done in 2013.
I set the Boot to Security disabled but to use UEFI.
Your excellent tip to use ctrl-alt-shift did indeed open a cmd prompt and ipconfig /all shows no hardware, just a loop back adapter.
ipconfig /renew complains that there is no adapter that can be renewed.
So it appears that although the Wizard finds the Realtek NIC after scanning the “Drivers for Full Restore” folder, it is not really using it.
Any thoughts?
Edit: Turning off security got me past the winload.efi error. But to satisfy curiosity, it was a 0xC00000428 error with a black screen, it appears just after the progress bar ends on the initial boot.
Realtek drivers can be wonkey without the full OS. Specifically, the thread says to do this:
Go to the Realtek website, click on Downloads
Click on Realtek PCIe GBE Family Controller Series Drivers from the Quick Links section on the right.
Locate and download the WinXP/Win Server 2003 Driver to your computer. I created a folder called Realtek Drivers for this purpose.
Now I am getting an IP address, can find the server, get a list of backups, etc. etc.
I could not have done this without knowing the ctrl-alt-shift trick, I still had to run an ipconfig /renew to get an IP V4 address, weird.
So it failed with a network error during restore. I am doing some “plan B” stuff before I make other attempts to restore directly from the DX4000.
Early on when I bought this device, I did a couple of bare metal restores and it was dead simple.
Now it’s gone from “it just plain works” to days of troubleshooting and annoyance for the BMR, The individual file restore still is rock solid and super convenient though.
Is Server 2012 essentials any better with modern clients and UEFI etc?
I ended up succeeding in my restore…only because I was restoring to exactly the same hard drive. In test runs attempting o use a different sized HD in the client, I never could get the partitioning offset correct for a restore that would boot.
