Bobcares

Hyper-v no UEFI-compatible file system was found – How to fix it?

by | Nov 28, 2019

Stuck with the error “Hyper-v no UEFI-compatible file system was found”? We can help you.

A few days ago we came across this error due to which our customer was not able to create a VM.

At Bobcares, we often receive requests to fix errors in Hyper-V errors as part of our Server Management Services.

Today, let’s analyze the cause for this error and see how our Support Engineers fix it for our customers.

 

Cause for Hyper-v no UEFI-compatible error

We’ve seen many of our customers experiencing this error. And normally, this error occurs when the configuration for the VM in Hyper-V is incorrect.

Microsoft introduced two Hyper-V Boot Architectures. One or BIOS and another for UEFI. Generation 1 supports BIOS whereas Generation 2 supports UEFI.

Selecting a Boot Architecture can be confusing for customers using Hyper-V. However, we need to select the generation correctly to load Non-UEFI OS.

Let’s discuss how our Support Engineers resolve the error.

 

How we fix the Hyper-V no UEFI-compatible error?

To resolve the error we need to select Generation 1. Let us discuss how our Support Engineers select Generation 1 during VM creation.

 

Creating a new VM without a NON-UEFI

To create a VM that supports only BIOS we use Generation 1. Only Generation 2 supports UEFI. Let’s discuss how our Support Engineers create a VM using Generation 1.

1. Open Hyper-V Manager. Click on Hyper-V host and click on Virtual Machine.

2. Now a new window appears and then click Next.

3. Select a location to store the Virtual Machine data. If left empty, it automatically selects the default location. Then, click Next.

4. In the Specify Generation, our Engineers select Generation 1 and click Next.

5. In Assign Memory we specify the memory. Now, in Configure Networking we select the Virtual Switch.

6. Then in Connect Virtual Hard disk, we select the required option and click next.

7. Now the summary displays, We verify the details and finally, we click Finish.

Finally, we created the VM and customer was able to login.

 

[Need any assistance with Hyper-V errors? – We’ll help you]

 

Conclusion

In short, we discussed the cause for the error “Hyper-v no UEFI-compatible file system was found”. Today, we discussed how our Support Engineers use the generation option to resolve the error.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

var google_conversion_label = "owonCMyG5nEQ0aD71QM";

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF