Problems Install Windows 10 Technical Preview on VB5 (German

[Peter987]

Hello,

I have got problems to install the Windows10_InsiderPreview_x64_DE-DE_10130.iso in VB5. I just get an error message, which says that I have a serious error (schwerwiegender Fehler in German).

I have choosed the Windows 64bit Profile. But also tried the Windows 8.1 64bit Profile. In my bios the vtx (Intel Virtualization Technology) is enabled and also in VB5 in the system settings.

Attached you find the log file from this setup in VB5.

If I enable the UEFI Option in the system settings of VB5 I can boot from the Iso image. But the installs hangs at the windows logo screen and doesn't go further.

Thank you for any help.

Greetings
Peter

VboxLog.zip

Vbox log with serous error

(32.64 KiB) Downloaded 4 times

[mpack]

00:00:05.318654 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
00:00:05.318654 !!
00:00:05.318655 !! Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT)
00:00:05.318808 !!
00:00:05.318866 !! Skipping ring-0 registers and stack, rcErr=VINF_EM_TRIPLE_FAULT
00:00:05.318871 !!
00:00:05.318871 !! {mappings, <NULL>}
00:00:05.318872 !!

This usually means that the guest tried to do something nasty. It's impossible to say what. You might like to check the MD5 sum on the downloaded ISO.

[Peter987]

Hello,

thank you for your reply.

I don't have a checksum for the iso. But I downloaded the newer iso: Windows10_InsiderPreview_x64_DE-DE_10162.

Now I don't get any serious error anymore. But the installation hangs at the Bootscreen windows logo. No chance to go further.

Attached you find the log File for this setup.

Greetings Peter

Vbox Log Boot Logo.zip

10162 ISO Boot Logo

(14.35 KiB) Downloaded 6 times

[mpack]

00:00:01.873549 Host RAM: 7912MB total, 2054MB available
...
00:00:02.582663 RamSize <integer> = 0x00000000c0000000 (3 221 225 472, 3 GB)

Now you are over-allocating host RAM. Find out who the RAM hogs are on your host and eliminate them before running this memory hungry VM. Or reduce the allocation to the VM to 1GB.

OTOH, your graphics RAM allocation seems a bit low to me. I'd raise it to 64MB.

[Peter987]

Hi,

I reduced the used Ram in the host by closing some applications. Also I set the Guest Ram to 1GB and the video Ram to 64 MB. But nothing has changed. The Boot process from the iso image stops at the Boot Logo Windows screen.

Any new ideas?

Greetings
Peter

[mpack]

It stops, or it spins? If the latter, how long did you let it spin? If the former then I need a new VM log.

If you are no longer getting VM crashes then I'm afraid you are now into Microsoft support territory. Provided you select the Win10-64bit profile then there is nothing else you need to do that I know of.

[Peter987]

Hi,

I'm not sure about the difference between it stops or spins. Anyway the boot process goes so fas that I see the small blue windows logo screen in the middle of the window. But then nothing happens. The Logo stays there forever (waited 30 min).

Attached you find the new Log File.

Greetings
Peter

New VBOX LOG.zip

Logo

(14.36 KiB) Downloaded 5 times

[mpack]

I'm not sure about the difference between it stops or spins

I'm referring to the "spinning dots" busy signal which Win8+ displays while booting up. If that animation keeps running then the VM is still running. If that animation stops then the VM has possibly locked up.

Another way to tell: does the VM shut down if you click the window close button? If yes then it implies that the VM process is quite happy, and your problem is in the guest OS. If you get no response to the mouse click then the VM has locked up.

There is no crash evident in the VM. However it is also incomplete: unless the VM was locked up then please make sure VMs are shut down before grabbing the log.

[Peter987]

Hi,

there are no 'spinning dots'. I have attached the screenshot. It shows the logo from the boot of the iso image. It stays there forever. Nothing else happens.

Any new ideas?

Greetings
Peter

Logo Screen from Boot of the iso image

Windows 10 64 bit.png (3.44 KiB) Viewed 2820 times

[Peter987]

Attached you find the new Log File after shutdown the VM

New VBox Log after Shutdown.zip

Log file after Shutdown VM

(20.08 KiB) Downloaded 7 times

[mpack]

There is no hang evident in the new log. In fact the total runtime from startup to terminated is 26 seconds, so certainly no evidence of a VM lockup there. You need to ask on a Windows forum about this Windows support issue.