https://login.veeam.com/en/oauth?client_id=nXojRrypJ8&redirect_uri=https%3A%2F%2Fwww.veeam.com%2Fservices%2Fauthentication%2Fredirect_url&response_type=code&scope=profile&state=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IyODQ4IiwiaGFzaCI6ImFmZGEwYTdlLWVlMjEtNDM0Yy04MTQ2LWE0NWM5MjQxYzQyMCJ9
1-800-691-1991 | 9am - 8pm ET
EN

Restored UEFI-based Windows 2008 R2 SP1 cannot be booted in Hyper-V environment

Challenge

Restored UEFI-based Windows 2008 R2 SP1 cannot be booted in the Hyper-V environment, while the restore operation is performed without errors, the data is accessible

User-added image

Cause

The boot failure is caused by the general incompatibility of such setup with Hyper-V.

Solution

  1. As a workaround, it is possible to convert the bootloader from incompatible GPT to MBR. It could be achieved via any liveCD, e.g. via Veeam Recovery Medea. The detailed procedure is outlined here. Thus, the idea is to restore the machine to Generation 1 first and then convert the bootloader to MBR – in this case, both requirements will be fit (G1 + MBR loader on BIOS).
  2. Change of the environment from Hyper-V to physical machine or any other hypervisor that does not have such limitations if the scenario allows that.
KB ID:
2848
Product:
Veeam Agent for Microsoft Windows
Version:
2.x
Published:
2018-12-24
Last Modified:
2020-08-13
Please rate how helpful this article was to you:
5 out of 5 based on 1 ratings
Thank you for helping us improve!
An error occurred during voting. Please try again later.

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text

Knowledge base content request
By submitting, you agree that your personal data will be managed by Veeam in accordance with the Privacy Policy.
Your report was sent to the responsible team. Our representative will contact you by email you provided.
We're working on it please try again later