Your PC needs to restart.
Please hold down the power button.
Error Code: 0x0000005D
Parameters:
0x00000000078BFBFF
0x0000000028100800
0x0000000000000001
0x0000000000000000
I had the same problem with same settings. What worked for me was disabling floppy and changing pointing device to PS2 mouse(was multimedia tablet). Maybe it has to do with Windows 10 Preview not supporting touch input? I did change number of processor (threads) from 4 - 2 - 1 - 4 and it didn't change anything and so did memory (4 - 2 - 1 - 4GB). And yes i have Execute Disable Bit on in UEFI. Graphics setting are 128 RAM, and enabled 2/3D acceleration.
My rig:
Windows 8 (not.1) x64
Xeon e3 1230 v3 (or cheaper i7 4770)
8 GB RAM
Ok, I've changed the pointing device.
But what do you mean with floppy? In the setup, I've created a hard disk (*.vdi) and I've added the Windows ISO file. So it looks like this: .
Then i think i can't help. I've read that to prevent that error you need to have enabled in bios virtualisation and execute disable bit (or something with similar name). You could check that but to be honest i'm no expert and I just bumped into this thread searching for the same answer. Mine Windows 10 is running well now. I'll post some configuration of VM
Attachments
Zrzut ekranu 2014-10-02 20.30.36.png (19.97 KiB) Viewed 96986 times
Zrzut ekranu 2014-10-02 20.30.33.png (28.3 KiB) Viewed 96986 times
Zrzut ekranu 2014-10-02 20.30.28.png (22.34 KiB) Viewed 96986 times
Same problem. I have disabled the NX bit in the bios, and verified all settings.(i think)
I ran the Intel processor id utility, and it says I have Execute disable bit set to No. The CPU supports SSE.
After reading the correct documentation, not all of the WRONG posts, I determined that the NX bit in the bios MUJST be enabled. Now on to the next problem!
I observered the post by Gemini. The only thing which makes Windows 10 works is the OS type must be set to Windows 8.1 (64bit). If you were to select Other Windows (64bit) it gives the error code of this post.
From my setting, the pointing device is as default which is USB Tablet. Here are mine setting.
2014-10-26_183004.png (39.42 KiB) Viewed 90272 times
2014-10-26_182909.png (38.9 KiB) Viewed 90272 times
2014-10-26_182930.png (37.02 KiB) Viewed 90272 times
Same problem as discussed above, same error message, etc. The only difference in my setup is that I am trying to install Windows 10 from Windows 7 64 bit. (Yes, the Operating System is set to Windows 7 (64 bit)) Are there any differences to solving the same error message from Windows 7 rather than Windows 8 or 8.1? Any help would be appreciated.
I solved this error code problem by changing the Windows version in the "Name and operating system" box from Windows 7 (64 bit) to Windows 8.1 (64 bit). This works fine even though I am running the VirtualBox on a Windows 7 (64 bit) computer. Hope this helps someone else.
Skylark wrote:I solved this error code problem by changing the Windows version in the "Name and operating system" box from Windows 7 (64 bit) to Windows 8.1 (64 bit). This works fine even though I am running the VirtualBox on a Windows 7 (64 bit) computer. Hope this helps someone else.
In my case, I changed "Name and operating system" selection in the dropdown list from "Other Windows(64bit)" to "Windows 8.1 (64bit)", since Windows10 (64bit) as guest operating system virtual machine on my Linux host (PCLinuxOS 2014 w/ 3.26.15-1pclos kernel) wasn't listed in Virtual Box (4.3.20_r96996). That fixed my 0x000005d error. Windows 10 on first boot had a problem and suggested I reboot it - I did so, and then Windows 10 (Tech Preview) booted up fine and runs as guest OS.
HP Compaq 6730 Laptop triple-boot Win7x64, Win8.1x64, PCLinuxOSx64 with Virtual Box guests (Win7Ex86 & Win10x64 Tech Preview);
Asus Z77 Sabertooth, Intel i7-3700K, 16GB DDR3, Asus GTX680/2GB, Windows 8.1 x64;
Asus P5N32-E Sli, Intel E8400, 4GB DDR2, Asus GTX580, triple-boot Win7x64, WinXPx86 & PClinuxOSx64
I am on a 32 bit laptop running Windows 7 and was trying to install Windows 10 32bit but always getting the error 0x0000005D before the installation-proper started.
Bizarrely, what fixed this issue for me was setting the guest O/S to 'Windows 8.1 (64bit)' - even though I'm totally 32bit.