after recovering a client to a new hardware (same client model from HP ProDesk G400 G4) the is an error after the recovery and the system doesn't start.
Its a system with an EFI-Partition.
I could fix it by converting EFI to a MBR with the following KB article from Veeam (https://www.veeam.com/kb2407)
But I think this is not the right way .
So after that I had to disable driver signature enforcement and the system starts...but I would rather keep my EFI partition
System ist a Windows 1709 and Veeam Agent for Windows is 2.2.0.589
Recovery Media can collect all drivers, operating system components and even network configuration if that's required (can be controlled by corresponding checkboxes in the Recovery Media creation wizard). I assume the conflict was caused by different device drivers injected to the OS during recovery.
You can create a generic Recovery Media per Operating System type and use 'do not collect drivers' option. In such case on generic drivers will be used and you should not see this problem. Additionally, under while Booted in Recovery Media you can go to Tools > Load Drivers and select 'Do not inject drivers' option. In such case drivers collected by recovery media wont be used during recovery.