Hi,
as it’s my first post here: Martin thanks for great software!
And get to problem, i stuck in this situation trying to restore my home developer win2016 server, machine is untouched same disk/config(i restore it few times testing different environments in last year without any problem). All files restore to disk but boot loader fail:
Loading MBR and GTP data…
Loading MBR failed: Error reading image size from server
Error loading MBR of partition
Beside this UrBackup work fine as usually, I check on my notebook - backup restore without any problems.
Are you keeping in mind that MBR drive (total drive space, not the size of partition/volume) must be less than 2048 Gb? What kind of partitioning scheme do you have on source system: GPT or MBR?
P. S. When I trying to restore image backup on different system, I always use “physical 2 physical” arrangement. This feature you can find in Paragon Partition Manager for example. It will clean boot dependencies / HAL settings from old system and recovered system will load with default driver/system software set.
Thanks for reply.
In my case it’s much simpler, same machine without any changes. As I mention it ist my home test environment I mess in system config a lot
And restore always work smooth, this was first time when i get this error so probably ghost in machine as system boot up without problem.
But as I’m testing container management on this system now, I will restore it next week once again so I let you know how it go. But my trust in urbackup is unshaken
I’m running into the same error when trying to restore my backup. The image was created from a Windows 10 installation on a GPT-formatted disk. Could you please help me diagnose and fix this issue?
Let me know what additional information you need (e.g. specific error messages, log files, partition table details) and how to gather it. I’ll be happy to provide whatever you require.
yes, I was able to restore the system successfully. Booting from the recovery USB and manually rebuilding the BCD using bootsect and bcdboot resolved the issue — the system now boots into Windows without any problems.
It would be helpful to understand what caused the problem in the first place. I used a backup image of one system and deployed it to multiple computers, so I’ll need to check whether the same issue appears on the other machines as well.
