If the recovery partition isn’t present and valid, these instructions won’t work.Ĭlick the 2nd entry, you should see (and then click): If the 2nd partition isn’t the recovery partition, look under the paths in the list to see if one of them is it. The second PCI path is probably to the recovery partition, the one you need to boot from. The first PCI path in the list is probably the boot partition that doesn’t contain bootable firmware. You should see two entries in a list (they are cryptic looking PCI bus paths). Select Boot Maintenance Manager and click.

You’ll be brought into an EFI text-mode GUI. Supuhstar Posts: 9 Joined: 23.I was able to fix the UEFI problems as follows ( credit to techrechard website): Host = Windows 8.1 圆4 (device supports hardware virtualization)ĭisabling EFI made it magically work! Somehow, it was crashing with error 0x0000005D before enabling EFI, then this error when enabling it, now it works when I disable it again! Weird. The log I posted probably says it, but here's my setup just to be clear: Upon install, I just took all the easiest options (use entire disk), and oh yeah! For setup: I used windows 8.1 64 bit type OS at start (closest thing to 10 I suppose). I immediately disabled IE, switched to Chrome, disabled Bing, switched to Google, no problems there. am using the 2d/3d options under display (but not using guest-tools since they're not up to date for W10. I've only got one setting of interest set: 'Enable PAE/Nx' Let's see: What else could be of help to know? I'm not saying it's worth running, but it does run without errors.

Windows 10 (today's TP) runs fine for me on v4.3.16 vBox. Papolytic wrote:I'm using host = Win 7 Ultimate 64.

Windows 10 virtualbox hangs