Windows 8 not booting in VBox

ijack March 29, 2016 at 01:33:21

Perhaps you could tell us what the error code is? This helps to identify the problem. Could you also tell us whether you are trying to install the 32- or 64-bit version of Windows 8.

Here - http://jaysarma987.xxxpart.com/file... The message with the error code. Additionally, this error screen shows up on boot - http://jaysarma987.xxxpart.com/file... But my vt-x/amd-v is enabled in my Windows 7 VBox but doesn't show any error. message edited by jaysarma987

Razor2.3 March 29, 2016 at 21:57:41

0x5D = Unsupported CPU. Verify your emulated CPU settings. How To Ask Questions The Smart Way

Verify, like? I mean, how should I set the VBox settings to make it work?

Razor2.3 March 30, 2016 at 06:12:13

.vbox files are just XML files, so you can open them in any text or XML editor. I used VirtualBox's GUI to give me the default 64-bit Win8 settings, and this is part of that file. <Hardware version="2"> <CPU count="1" hotplug="false"> <HardwareVirtEx enabled="true"/> <HardwareVirtExNestedPaging enabled="true"/> <HardwareVirtExVPID enabled="true"/> <HardwareVirtExUX enabled="true"/> <PAE enabled="false"/> <LongMode enabled="true"/> <HardwareVirtExLargePages enabled="true"/> <HardwareVirtForce enabled="false"/> </CPU> . . . . <BIOS> <ACPI enabled="true"/> <IOAPIC enabled="true"/> <Logo fadeIn="true" fadeOut="true" displayTime="0"/> <BootMenu mode="MessageAndMenu"/> <TimeOffset value="0"/> <PXEDebug enabled="false"/> </BIOS> . . . . </Hardware> Failing these settings, make sure your virtualization extensions are enabled in your BIOS. Also, make sure your ISO is an x86 or x86-64 version of Windows. How To Ask Questions The Smart Way

The Windows 8 version is an x86 one. And yes, virtualisation extension is enabled in my BIOS (considering WinXP and Win7 runs coool) Gotta try the XML codes, I have no access to my PC now for like a week, will reply on 6th :)

Update the vbox or you can increase the number of cpu core

Hi, davistar An update solved the issue. Thanks :) but speaking in technical terms, I didn't actually get that.