[WorksForMe] Windows 10 does not boot
[WorksForMe] Windows 10 does not boot
I created a new vm and downloaded the iso file for windows 10 from the official microsoft download page. Did not change the settings other than selecting which iso file to boot. VirtualBox is running and telling me that windows is executed (not sure about correct term - I use the German version - it says: Windows wird ausgeführt). So it seems to work.. but I only see the blue logo. It never proceeds with the installation. Even though I tried the whole night. It used to work with Windows 8.1
Any hints what I could try? Thanks
Any hints what I could try? Thanks
Last edited by socratis on 30. Oct 2017, 03:49, edited 1 time in total.
Reason: Marked as [WorksForMe].
Reason: Marked as [WorksForMe].
-
- Site Moderator
- Posts: 27330
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: Windows 10 does not boot
- Follow a "start the VM from cold-boot" / "observe error" / "shutdown the VM" cycle.
- With the VM shut down completely (not paused or saved), right-click on the VM in the VirtualBox Manager and select "Show Log".
- Save only the first "VBox.log", ZIP it and attach it to your response (see the "Upload attachment" tab below the reply form).
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Re: Windows 10 does not boot
thanks - I attached the log
- Attachments
-
- VBox.log.zip
- (18.25 KiB) Downloaded 14 times
-
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: Windows 10 does not boot
Code: Select all
VirtualBox VM 5.0.40_Ubuntu r115130 linux.amd64 (Apr 20 2017 06:58:05) release log
00:00:01.693996 Log opened 2017-10-29T12:37:52.685805000Z
00:00:01.694000 Build Type: release
00:00:01.694010 OS Product: Linux
00:00:01.694014 OS Release: 4.8.0-53-generic
00:00:01.694018 OS Version: #56~16.04.1-Ubuntu SMP Tue May 16 01:18:56 UTC 2017
00:00:01.694103 DMI Product Name: 20BC0000MZ
00:00:01.694137 DMI Product Version: ThinkPad Edge E145
00:00:01.694292 Host RAM: 3374MB total, 2856MB available
00:00:01.694377 Executable: /usr/lib/virtualbox/VirtualBox
00:00:01.694380 Process ID: 2006
00:00:01.694383 Package type: LINUX_64BITS_GENERIC (OSE)
00:00:01.752590 Installed Extension Packs:
00:00:01.752663 VNC (Version: 5.0.40 r115130; VRDE Module: VBoxVNC)
- version 5.0.40 is too old for Windows 10 especially with updates.
We do not support the Ubuntu fork they do. So while updating remove theirs and install the official version from virtualbox.org or ask them for assistance.
Re: Windows 10 does not boot
thank you - I work with Linux Mint 18.2 (latest version) - and used the application center to install virtualbox
I am not sure which of these versions is the right one to use:
Ubuntu 17.04 ("Zesty") i386 | AMD64
Ubuntu 16.10 ("Yakkety") i386 | AMD64
Ubuntu 16.04 ("Xenial") i386 | AMD64
Ubuntu 14.04 ("Trusty") / 14.10 ("Utopic") / 15.04 ("Vivid") i386 | AMD64
Debian 9 ("Stretch") i386 | AMD64
Debian 8 ("Jessie") i386 | AMD64
Debian 7 ("Wheezy") i386 | AMD64
I assume i386 and AMD64 stands for processors or kernel architecture. My computer runs on an Intel Pentium; the kernel is 4.8.0-53-generic x86_64.
Could you give me a hint what version to pick?
Then I would run the generic installer (VirtualBox.run) according to the manual.
Sorry - I know these are probable beginners questions - its hard to solve if you really don't know..
Thanks
I am not sure which of these versions is the right one to use:
Ubuntu 17.04 ("Zesty") i386 | AMD64
Ubuntu 16.10 ("Yakkety") i386 | AMD64
Ubuntu 16.04 ("Xenial") i386 | AMD64
Ubuntu 14.04 ("Trusty") / 14.10 ("Utopic") / 15.04 ("Vivid") i386 | AMD64
Debian 9 ("Stretch") i386 | AMD64
Debian 8 ("Jessie") i386 | AMD64
Debian 7 ("Wheezy") i386 | AMD64
I assume i386 and AMD64 stands for processors or kernel architecture. My computer runs on an Intel Pentium; the kernel is 4.8.0-53-generic x86_64.
Could you give me a hint what version to pick?
Then I would run the generic installer (VirtualBox.run) according to the manual.
Sorry - I know these are probable beginners questions - its hard to solve if you really don't know..
Thanks
-
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: Windows 10 does not boot
18 is the same a Ubuntu Xenial and you need to install the amd64 version of VirtualBox
I would use dpkg to install myself.
I would use dpkg to install myself.
-
- Site Moderator
- Posts: 27330
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: Windows 10 does not boot
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Re: Windows 10 does not boot
ok thanks
but you have to admit:
if X86_64 == AMD64 - why are there two different packages?
This remains an enigma
but you have to admit:
if X86_64 == AMD64 - why are there two different packages?
This remains an enigma
-
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: Windows 10 does not boot
Ah you forgot to read the link that was provided. That would have explained it to you.
Re: Windows 10 does not boot
I looked it up on wikipedia - still unsure - but AMD seems the right choice as on wikipedia at the bottom of page it states:
amd64
....
Some Linux distributions such as Debian, Ubuntu, and Gentoo refer to both AMD64 and Intel 64 under the architecture name "amd64".
....
x86_64
The Linux kernel[83] and the GNU Compiler Collection refers to 64-bit architecture as "x86_64".
Some Linux distributions, such as Fedora, openSUSE, and Arch Linux refer to this 64-bit architecture as "x86_64"
....
this is more trying than understanding
hey - windows 10 is starting now
but unfortunately a driver is missing and the setup of Windows within the vm stops at this point - the continue-button is not active.
amd64
....
Some Linux distributions such as Debian, Ubuntu, and Gentoo refer to both AMD64 and Intel 64 under the architecture name "amd64".
....
x86_64
The Linux kernel[83] and the GNU Compiler Collection refers to 64-bit architecture as "x86_64".
Some Linux distributions, such as Fedora, openSUSE, and Arch Linux refer to this 64-bit architecture as "x86_64"
....
this is more trying than understanding
hey - windows 10 is starting now
but unfortunately a driver is missing and the setup of Windows within the vm stops at this point - the continue-button is not active.
-
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: Windows 10 does not boot
A driver is missing almost always means the download is corrupt. See if the checksum matches what the download page says it is supposed to be and if ( as I suspect ) they don't download it again.
-
- Site Moderator
- Posts: 27330
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: Windows 10 does not boot
Or it's an OEM Win10 installation, which is "cropped" to include only the hardware supported by the OEM.
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
-
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: Windows 10 does not boot
They posted "I created a new vm and downloaded the iso file for windows 10 from the official microsoft download page." So unless there is a really weird install file ( I have no idea what they have ) it is more likely that the download is corrupt.
-
- Site Moderator
- Posts: 27330
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: Windows 10 does not boot
Oops... I missed that part.
You could have taken my comment as "Generally speaking... "
You could have taken my comment as "Generally speaking... "
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Re: Windows 10 does not boot
I tried twice - and downloaded from the us website and from the german website. Both iso files lead to the same point.
can't find the official checksum for the iso file so far - unless there is something missing from virtualbox it has to be a flaw with the iso file.
I verified the MD5 checksum of the two iso files that carry the same name and were both officially downloaded. Indeed - the checksum is not the same. Both files don't work
can't find the official checksum for the iso file so far - unless there is something missing from virtualbox it has to be a flaw with the iso file.
I verified the MD5 checksum of the two iso files that carry the same name and were both officially downloaded. Indeed - the checksum is not the same. Both files don't work