Stuck on UEFI interactive shell with Mac OS X High Sierra VM

I got a Mac OS X virtual machine on VirtualBox and when I started it, I got into this UEFI shell:

UEFI shell

What should I do?

edited Jul 30 '17 at 22:26

G-Man

5,566102357

asked Jul 30 '17 at 21:52

WeakMaster

51113

1

Unless you're running this on Apple hardware, this qualifies as a "Hackintosh" configuration, which is of questionable legality in many areas and so is off-topic here. That said, this Intel PDF describes the basics of the EFI shell, which is what you're seeing.
– Rod Smith
Aug 1 '17 at 14:20

Possible duplicate of Getting UEFI shell when trying to boot OS X in VirtualBox
– Scott
Aug 23 '17 at 5:25

2

@RodSmith The most recent discussion on this in Meta seems to reach the consensus that the legality is a non-issue, while the practicality may remain so: meta.superuser.com/questions/12050/…
– music2myear
Aug 25 '17 at 23:12

add a comment |

I got a Mac OS X virtual machine on VirtualBox and when I started it, I got into this UEFI shell:

UEFI shell

What should I do?

edited Jul 30 '17 at 22:26

G-Man

5,566102357

asked Jul 30 '17 at 21:52

WeakMaster

51113

1

Unless you're running this on Apple hardware, this qualifies as a "Hackintosh" configuration, which is of questionable legality in many areas and so is off-topic here. That said, this Intel PDF describes the basics of the EFI shell, which is what you're seeing.
– Rod Smith
Aug 1 '17 at 14:20

Possible duplicate of Getting UEFI shell when trying to boot OS X in VirtualBox
– Scott
Aug 23 '17 at 5:25

2

@RodSmith The most recent discussion on this in Meta seems to reach the consensus that the legality is a non-issue, while the practicality may remain so: meta.superuser.com/questions/12050/…
– music2myear
Aug 25 '17 at 23:12

add a comment |

I got a Mac OS X virtual machine on VirtualBox and when I started it, I got into this UEFI shell:

UEFI shell

What should I do?

edited Jul 30 '17 at 22:26

G-Man

5,566102357

asked Jul 30 '17 at 21:52

WeakMaster

51113

I got a Mac OS X virtual machine on VirtualBox and when I started it, I got into this UEFI shell:

UEFI shell

What should I do?

macos boot virtualbox shell uefi

edited Jul 30 '17 at 22:26

G-Man

5,566102357

asked Jul 30 '17 at 21:52

WeakMaster

51113

edited Jul 30 '17 at 22:26

G-Man

5,566102357

asked Jul 30 '17 at 21:52

WeakMaster

51113

edited Jul 30 '17 at 22:26

G-Man

5,566102357

edited Jul 30 '17 at 22:26

G-Man

5,566102357

edited Jul 30 '17 at 22:26

G-Man

5,566102357

asked Jul 30 '17 at 21:52

WeakMaster

51113

asked Jul 30 '17 at 21:52

WeakMaster

51113

asked Jul 30 '17 at 21:52

WeakMaster

51113

1

Unless you're running this on Apple hardware, this qualifies as a "Hackintosh" configuration, which is of questionable legality in many areas and so is off-topic here. That said, this Intel PDF describes the basics of the EFI shell, which is what you're seeing.
– Rod Smith
Aug 1 '17 at 14:20

Possible duplicate of Getting UEFI shell when trying to boot OS X in VirtualBox
– Scott
Aug 23 '17 at 5:25

2

@RodSmith The most recent discussion on this in Meta seems to reach the consensus that the legality is a non-issue, while the practicality may remain so: meta.superuser.com/questions/12050/…
– music2myear
Aug 25 '17 at 23:12

add a comment |

1

Unless you're running this on Apple hardware, this qualifies as a "Hackintosh" configuration, which is of questionable legality in many areas and so is off-topic here. That said, this Intel PDF describes the basics of the EFI shell, which is what you're seeing.
– Rod Smith
Aug 1 '17 at 14:20

Possible duplicate of Getting UEFI shell when trying to boot OS X in VirtualBox
– Scott
Aug 23 '17 at 5:25

2

@RodSmith The most recent discussion on this in Meta seems to reach the consensus that the legality is a non-issue, while the practicality may remain so: meta.superuser.com/questions/12050/…
– music2myear
Aug 25 '17 at 23:12

Unless you're running this on Apple hardware, this qualifies as a "Hackintosh" configuration, which is of questionable legality in many areas and so is off-topic here. That said, this Intel PDF describes the basics of the EFI shell, which is what you're seeing.
– Rod Smith
Aug 1 '17 at 14:20

Possible duplicate of Getting UEFI shell when trying to boot OS X in VirtualBox
– Scott
Aug 23 '17 at 5:25

@RodSmith The most recent discussion on this in Meta seems to reach the consensus that the legality is a non-issue, while the practicality may remain so: meta.superuser.com/questions/12050/…
– music2myear
Aug 25 '17 at 23:12

add a comment |

2 Answers
2

active

oldest

votes

In VM settings General > Basic > Version set "macOS 10.13 High Sierra (64-bit)", because likely now you have setting 32-bit version.

answered Apr 23 at 0:54

Prof

19113

add a comment |

I also hit the problem of getting stuck at the UEFI shell prompt when booting from a viable disk (such as my case where MacOS had just been installed in a Virtual Machine).

I was able to fix the UEFI problems as follows
(credit to VirtualBox forum):

At UEFI prompt:
Type exit

You'll be brought into an EFI text-mode GUI.

Select Boot Maintenance Manager and click.

Select Boot From File and click

You should see two entries in a list (they are cryptic looking PCI bus paths).

The first is the PCI path to a boot partition that isn't working (corrupted or perhaps has no data or OS installed on it).

The 2nd partition is the recovery partition, the one you need to boot from to do the macOS installation or other maintenance/administrative tasks (including accessing Disk Utility to work on the System Volume partition without an OS running).

Click the 2nd entry, you should see (and then click):

macOS Install Data

Then click:

Locked Files

Then (if present), click

Boot Files

And finally click:

boot.efi

At that point he installer boot will continue and you should get to the point where you can attempt to repair the volume or [re]install macOS

edited Oct 28 at 23:28

answered Aug 22 at 19:25

clearlight

249210

1

This worked for me. Only slight difference was that under Locked Files there was another level called Boot Files, once navigating into that directory, boot.efi was within it. Thanks!
– rastating
Oct 25 at 15:24

Thanks @rastating. I added it in italics to the steps, as a potential extra layer in some configurations.
– clearlight
Oct 28 at 23:18

add a comment |

Your Answer

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});

}
});

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1235970%2fstuck-on-uefi-interactive-shell-with-mac-os-x-high-sierra-vm%23new-answer', 'question_page');
}
);

Post as a guest

Name

Required, but never shown

2 Answers
2

active

oldest

votes

2 Answers
2

active

oldest

votes

In VM settings General > Basic > Version set "macOS 10.13 High Sierra (64-bit)", because likely now you have setting 32-bit version.

answered Apr 23 at 0:54

Prof

19113

add a comment |

In VM settings General > Basic > Version set "macOS 10.13 High Sierra (64-bit)", because likely now you have setting 32-bit version.

answered Apr 23 at 0:54

Prof

19113

add a comment |

In VM settings General > Basic > Version set "macOS 10.13 High Sierra (64-bit)", because likely now you have setting 32-bit version.

answered Apr 23 at 0:54

Prof

19113

In VM settings General > Basic > Version set "macOS 10.13 High Sierra (64-bit)", because likely now you have setting 32-bit version.

answered Apr 23 at 0:54

Prof

19113

answered Apr 23 at 0:54

Prof

19113

answered Apr 23 at 0:54

Prof

19113

answered Apr 23 at 0:54

Prof

19113

add a comment |

I also hit the problem of getting stuck at the UEFI shell prompt when booting from a viable disk (such as my case where MacOS had just been installed in a Virtual Machine).

I was able to fix the UEFI problems as follows
(credit to VirtualBox forum):

At UEFI prompt:
Type exit

You'll be brought into an EFI text-mode GUI.

Select Boot Maintenance Manager and click.

Select Boot From File and click

You should see two entries in a list (they are cryptic looking PCI bus paths).

The first is the PCI path to a boot partition that isn't working (corrupted or perhaps has no data or OS installed on it).

Click the 2nd entry, you should see (and then click):

macOS Install Data

Then click:

Locked Files

Then (if present), click

Boot Files

And finally click:

boot.efi

At that point he installer boot will continue and you should get to the point where you can attempt to repair the volume or [re]install macOS

edited Oct 28 at 23:28

answered Aug 22 at 19:25

clearlight

249210

1

This worked for me. Only slight difference was that under Locked Files there was another level called Boot Files, once navigating into that directory, boot.efi was within it. Thanks!
– rastating
Oct 25 at 15:24

Thanks @rastating. I added it in italics to the steps, as a potential extra layer in some configurations.
– clearlight
Oct 28 at 23:18

add a comment |

I also hit the problem of getting stuck at the UEFI shell prompt when booting from a viable disk (such as my case where MacOS had just been installed in a Virtual Machine).

I was able to fix the UEFI problems as follows
(credit to VirtualBox forum):

At UEFI prompt:
Type exit

You'll be brought into an EFI text-mode GUI.

Select Boot Maintenance Manager and click.

Select Boot From File and click

You should see two entries in a list (they are cryptic looking PCI bus paths).

The first is the PCI path to a boot partition that isn't working (corrupted or perhaps has no data or OS installed on it).

Click the 2nd entry, you should see (and then click):

macOS Install Data

Then click:

Locked Files

Then (if present), click

Boot Files

And finally click:

boot.efi

At that point he installer boot will continue and you should get to the point where you can attempt to repair the volume or [re]install macOS

edited Oct 28 at 23:28

answered Aug 22 at 19:25

clearlight

249210

1

This worked for me. Only slight difference was that under Locked Files there was another level called Boot Files, once navigating into that directory, boot.efi was within it. Thanks!
– rastating
Oct 25 at 15:24

Thanks @rastating. I added it in italics to the steps, as a potential extra layer in some configurations.
– clearlight
Oct 28 at 23:18

add a comment |

I also hit the problem of getting stuck at the UEFI shell prompt when booting from a viable disk (such as my case where MacOS had just been installed in a Virtual Machine).

I was able to fix the UEFI problems as follows
(credit to VirtualBox forum):

At UEFI prompt:
Type exit

You'll be brought into an EFI text-mode GUI.

Select Boot Maintenance Manager and click.

Select Boot From File and click

You should see two entries in a list (they are cryptic looking PCI bus paths).

The first is the PCI path to a boot partition that isn't working (corrupted or perhaps has no data or OS installed on it).

Click the 2nd entry, you should see (and then click):

macOS Install Data

Then click:

Locked Files

Then (if present), click

Boot Files

And finally click:

boot.efi

At that point he installer boot will continue and you should get to the point where you can attempt to repair the volume or [re]install macOS

edited Oct 28 at 23:28

answered Aug 22 at 19:25

clearlight

249210

I also hit the problem of getting stuck at the UEFI shell prompt when booting from a viable disk (such as my case where MacOS had just been installed in a Virtual Machine).

I was able to fix the UEFI problems as follows
(credit to VirtualBox forum):

At UEFI prompt:
Type exit

You'll be brought into an EFI text-mode GUI.

Select Boot Maintenance Manager and click.

Select Boot From File and click

You should see two entries in a list (they are cryptic looking PCI bus paths).

The first is the PCI path to a boot partition that isn't working (corrupted or perhaps has no data or OS installed on it).

Click the 2nd entry, you should see (and then click):

macOS Install Data

Then click:

Locked Files

Then (if present), click

Boot Files

And finally click:

boot.efi

At that point he installer boot will continue and you should get to the point where you can attempt to repair the volume or [re]install macOS

edited Oct 28 at 23:28

answered Aug 22 at 19:25

clearlight

249210

edited Oct 28 at 23:28

answered Aug 22 at 19:25

clearlight

249210

answered Aug 22 at 19:25

clearlight

249210

answered Aug 22 at 19:25

clearlight

249210

1

This worked for me. Only slight difference was that under Locked Files there was another level called Boot Files, once navigating into that directory, boot.efi was within it. Thanks!
– rastating
Oct 25 at 15:24

Thanks @rastating. I added it in italics to the steps, as a potential extra layer in some configurations.
– clearlight
Oct 28 at 23:18

add a comment |

1

This worked for me. Only slight difference was that under Locked Files there was another level called Boot Files, once navigating into that directory, boot.efi was within it. Thanks!
– rastating
Oct 25 at 15:24

Thanks @rastating. I added it in italics to the steps, as a potential extra layer in some configurations.
– clearlight
Oct 28 at 23:18

This worked for me. Only slight difference was that under Locked Files there was another level called Boot Files, once navigating into that directory, boot.efi was within it. Thanks!
– rastating
Oct 25 at 15:24

Thanks @rastating. I added it in italics to the steps, as a potential extra layer in some configurations.
– clearlight
Oct 28 at 23:18

add a comment |

draft saved

draft discarded

Thanks for contributing an answer to Super User!

Please be sure to answer the question. Provide details and share your research!

But avoid …

Asking for help, clarification, or responding to other answers.

Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.

Some of your past answers have not been well-received, and you're in danger of being blocked from answering.

Please pay close attention to the following guidance:

Please be sure to answer the question. Provide details and share your research!

But avoid …

Asking for help, clarification, or responding to other answers.

Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Name

Required, but never shown

Name

Required, but never shown

This page is only for reference, If you need detailed information, please check here

搜尋此網誌

Argthtjtr