Windows 10 guest OS stuck booting in Virtualbox on Ubuntu 16.04 host
Microsoft offers these downloadable virtual machine images for cross-browser testing (IE8-IE11 and Edge). My host OS is Ubuntu 16.04 (64-bit) and I'm running Virtualbox 5.0.40_Ubuntu r115130.
The problem I experience is that loading two of the images Win10 stable and also the Win10 preview (after having successfully imported the appliances) gets stuck at the start screen. My host OS shows one CPU core fully utilized, so it's likely a CPU bottleneck, right?
After about a quarter of an hour, still no progress here.
At importing the appliance I left everything as it was preconfigured (4096MB memory, 1 CPU, etc.). Is there any "trick" to overcome this?
ubuntu windows-10 virtualbox virtual-machine
asked Jul 2 '17 at 10:01
Drunken MasterDrunken Master
188116
add a comment |
Microsoft offers these downloadable virtual machine images for cross-browser testing (IE8-IE11 and Edge). My host OS is Ubuntu 16.04 (64-bit) and I'm running Virtualbox 5.0.40_Ubuntu r115130.
The problem I experience is that loading two of the images Win10 stable and also the Win10 preview (after having successfully imported the appliances) gets stuck at the start screen. My host OS shows one CPU core fully utilized, so it's likely a CPU bottleneck, right?
After about a quarter of an hour, still no progress here.
At importing the appliance I left everything as it was preconfigured (4096MB memory, 1 CPU, etc.). Is there any "trick" to overcome this?
ubuntu windows-10 virtualbox virtual-machine
asked Jul 2 '17 at 10:01
Drunken MasterDrunken Master
188116
Disable other process then run VM. What's your CPU Max cycle?
– Biswapriyo
Jul 2 '17 at 12:25
May not be exactly the same, but similar issue and a fix superuser.com/a/1263414/106974
– IsaacS
Dec 5 '17 at 0:02
add a comment |
Microsoft offers these downloadable virtual machine images for cross-browser testing (IE8-IE11 and Edge). My host OS is Ubuntu 16.04 (64-bit) and I'm running Virtualbox 5.0.40_Ubuntu r115130.
The problem I experience is that loading two of the images Win10 stable and also the Win10 preview (after having successfully imported the appliances) gets stuck at the start screen. My host OS shows one CPU core fully utilized, so it's likely a CPU bottleneck, right?
After about a quarter of an hour, still no progress here.
At importing the appliance I left everything as it was preconfigured (4096MB memory, 1 CPU, etc.). Is there any "trick" to overcome this?
ubuntu windows-10 virtualbox virtual-machine
asked Jul 2 '17 at 10:01
Drunken MasterDrunken Master
188116
Microsoft offers these downloadable virtual machine images for cross-browser testing (IE8-IE11 and Edge). My host OS is Ubuntu 16.04 (64-bit) and I'm running Virtualbox 5.0.40_Ubuntu r115130.
The problem I experience is that loading two of the images Win10 stable and also the Win10 preview (after having successfully imported the appliances) gets stuck at the start screen. My host OS shows one CPU core fully utilized, so it's likely a CPU bottleneck, right?
After about a quarter of an hour, still no progress here.
At importing the appliance I left everything as it was preconfigured (4096MB memory, 1 CPU, etc.). Is there any "trick" to overcome this?
ubuntu windows-10 virtualbox virtual-machine
ubuntu windows-10 virtualbox virtual-machine
asked Jul 2 '17 at 10:01
Drunken MasterDrunken Master
188116
asked Jul 2 '17 at 10:01
Drunken MasterDrunken Master
188116
asked Jul 2 '17 at 10:01
Drunken MasterDrunken Master
188116
asked Jul 2 '17 at 10:01
Drunken MasterDrunken Master
188116
asked Jul 2 '17 at 10:01
Drunken MasterDrunken Master
188116
188116
Disable other process then run VM. What's your CPU Max cycle?
– Biswapriyo
Jul 2 '17 at 12:25
May not be exactly the same, but similar issue and a fix superuser.com/a/1263414/106974
– IsaacS
Dec 5 '17 at 0:02
add a comment |
Disable other process then run VM. What's your CPU Max cycle?
– Biswapriyo
Jul 2 '17 at 12:25
May not be exactly the same, but similar issue and a fix superuser.com/a/1263414/106974
– IsaacS
Dec 5 '17 at 0:02
Disable other process then run VM. What's your CPU Max cycle?
– Biswapriyo
Jul 2 '17 at 12:25
Disable other process then run VM. What's your CPU Max cycle?
– Biswapriyo
Jul 2 '17 at 12:25
May not be exactly the same, but similar issue and a fix superuser.com/a/1263414/106974
– IsaacS
Dec 5 '17 at 0:02
May not be exactly the same, but similar issue and a fix superuser.com/a/1263414/106974
– IsaacS
Dec 5 '17 at 0:02
add a comment |
3 Answers
3
active
oldest
votes
I have had the same problem.
I fixed it by changing the Virtualbox Setting -> System -> Acceleration -> Paravirtualization Interface and selecting KVM instead of "default".
Now boot Window 10 again and it should boot.
You may select "none" but the performance is so much slower.
FYI: I have the same version of virtualbox 5.0.40_Ubuntu r115130 and upgraded to windows 10 1709.
edited Dec 8 '17 at 8:48
Richard Lucas
2,6461622
answered Dec 8 '17 at 6:27
MingMing
23122
I tried everything possible with no luck, then I found this comment... Never even would have though it was the hypervisor in this case... Thanks for saving me another 5 hours of struggle.
– Ethode
Dec 9 '17 at 22:40
1
Yes, thanks for taking the time to record this is has saved me a lot of hassle. Does anyone know what this setting actually does - jFTR?
– diversemix
Dec 17 '17 at 21:53
I had the same problem and it actually worked. Changed to KVM and now its booting up properly.
– Dawid Pura
Mar 22 '18 at 6:48
This did it for me too, massive help!
– Michael Mallett
Oct 21 '18 at 3:36
add a comment |
I had a similar problem. I'm running Linux Mint 18.1 x64 (based off 16.04 Xenial) and VirtualBox 5.0.32. I have a full/real version (not the IE tester version) of Windows 10 that was running fine in VB as installed from the ISO. This was version 1511 (build 10586).
I then tried to update to version 1703 (build 15063) and experienced exactly the same behaviour that you've described. The solution for me was to update the version of VirtualBox to 5.1.22, the latest at the time of writing. 5.0.32 was the latest available in the Ubuntu repository so I had to install the newer version from the VirtualBox apt repo as described at https://www.virtualbox.org/wiki/Linux_Downloads#Debian-basedLinuxdistributions:
Add the following line to your /etc/apt/sources.list:
deb http://download.virtualbox.org/virtualbox/debian yakkety contrib
According to your distribution, replace 'yakkety' by 'xenial',
'vivid', 'utopic', 'trusty', 'raring', 'quantal', 'precise', 'lucid',
'jessie', 'wheezy', or 'squeeze'. ... The Oracle public key for
apt-secure can be downloaded...and register[ed]:
wget -q https://www.virtualbox.org/download/oracle_vbox_2016.asc -O- | sudo apt-key add -
wget -q https://www.virtualbox.org/download/oracle_vbox.asc -O- | sudo apt-key add -
...snip...
To install VirtualBox, do
sudo apt-get update
sudo apt-get install virtualbox-5.1
...snip...
Note: Ubuntu/Debian users might want to install the
dkms
package...through the following command:
sudo apt-get install dkms
Once I updated VirtualBox, I performed the update in the guest and after restart I almost instantly saw the white dot spinner appear on the black screen with the cyan windows logo (that you've attached) as you'd expect.
answered Jul 4 '17 at 2:39
Tom SaleebaTom Saleeba
1314
Would it be best to remove your existing Ubuntu-distributed VirtualBox installation before performing this procedure, or will this upgrade it? Or can you run them in parallel? Will your existing configurations be maintained?
– k-den
Aug 16 '17 at 18:46
I tried these steps without removing the existing Ubuntu-distributed VirtualBox, and now when I try to open the Win 10 image previously imported it says "RTR3InitEx failed with rc=-1912 The VirtualBox kernel modules do not match this version of VirtualBox. The installation of VirtualBox was apparently not successful. Executing '/sbin/vboxconfig' may correct this. Make sure that you do not mix the OSE version and the PUEL version of VirtualBox..." Executing /sbin/vboxconfig did not fix it.
– k-den
Aug 16 '17 at 18:58
@k-den I think apt should perform an upgrade and keep all your settings, at least that's what happened to me. As you're running into trouble, it might be best to backup the virtualbox config (have to Google where that lives) theapt-get purgeall versions of virtualbox from your system, then install a fresh copy. Alternatively, you might just have to restart your system if it hasn't picked up the new kernel modules.
– Tom Saleeba
Aug 17 '17 at 0:34
add a comment |
I had this issue too. I got it working by updating Virtualbox to version 5.0.40 and changing the general settings tab to other for both type and version.
$sudo apt autoremove --purge virtualbox*
$sudo apt install virtualbox=5.0.40-dfsg-0ubuntu1.16.04.1
Name: Windows 10
Type: Other
Version: Other/Unknown(64-bit)
edited Oct 15 '17 at 23:05
Pimp Juice IT
24.7k113974
answered Oct 15 '17 at 21:25
Arnaldo GArnaldo G
1
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1224949%2fwindows-10-guest-os-stuck-booting-in-virtualbox-on-ubuntu-16-04-host%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
I have had the same problem.
I fixed it by changing the Virtualbox Setting -> System -> Acceleration -> Paravirtualization Interface and selecting KVM instead of "default".
Now boot Window 10 again and it should boot.
You may select "none" but the performance is so much slower.
FYI: I have the same version of virtualbox 5.0.40_Ubuntu r115130 and upgraded to windows 10 1709.
edited Dec 8 '17 at 8:48
Richard Lucas
2,6461622
answered Dec 8 '17 at 6:27
MingMing
23122
I tried everything possible with no luck, then I found this comment... Never even would have though it was the hypervisor in this case... Thanks for saving me another 5 hours of struggle.
– Ethode
Dec 9 '17 at 22:40
1
Yes, thanks for taking the time to record this is has saved me a lot of hassle. Does anyone know what this setting actually does - jFTR?
– diversemix
Dec 17 '17 at 21:53
I had the same problem and it actually worked. Changed to KVM and now its booting up properly.
– Dawid Pura
Mar 22 '18 at 6:48
This did it for me too, massive help!
– Michael Mallett
Oct 21 '18 at 3:36
add a comment |
I have had the same problem.
I fixed it by changing the Virtualbox Setting -> System -> Acceleration -> Paravirtualization Interface and selecting KVM instead of "default".
Now boot Window 10 again and it should boot.
You may select "none" but the performance is so much slower.
FYI: I have the same version of virtualbox 5.0.40_Ubuntu r115130 and upgraded to windows 10 1709.
edited Dec 8 '17 at 8:48
Richard Lucas
2,6461622
answered Dec 8 '17 at 6:27
MingMing
23122
I tried everything possible with no luck, then I found this comment... Never even would have though it was the hypervisor in this case... Thanks for saving me another 5 hours of struggle.
– Ethode
Dec 9 '17 at 22:40
1
Yes, thanks for taking the time to record this is has saved me a lot of hassle. Does anyone know what this setting actually does - jFTR?
– diversemix
Dec 17 '17 at 21:53
I had the same problem and it actually worked. Changed to KVM and now its booting up properly.
– Dawid Pura
Mar 22 '18 at 6:48
This did it for me too, massive help!
– Michael Mallett
Oct 21 '18 at 3:36
add a comment |
I have had the same problem.
I fixed it by changing the Virtualbox Setting -> System -> Acceleration -> Paravirtualization Interface and selecting KVM instead of "default".
Now boot Window 10 again and it should boot.
You may select "none" but the performance is so much slower.
FYI: I have the same version of virtualbox 5.0.40_Ubuntu r115130 and upgraded to windows 10 1709.
edited Dec 8 '17 at 8:48
Richard Lucas
2,6461622
answered Dec 8 '17 at 6:27
MingMing
23122
I have had the same problem.
I fixed it by changing the Virtualbox Setting -> System -> Acceleration -> Paravirtualization Interface and selecting KVM instead of "default".
Now boot Window 10 again and it should boot.
You may select "none" but the performance is so much slower.
FYI: I have the same version of virtualbox 5.0.40_Ubuntu r115130 and upgraded to windows 10 1709.
edited Dec 8 '17 at 8:48
Richard Lucas
2,6461622
answered Dec 8 '17 at 6:27
MingMing
23122
edited Dec 8 '17 at 8:48
Richard Lucas
2,6461622
edited Dec 8 '17 at 8:48
Richard Lucas
2,6461622
edited Dec 8 '17 at 8:48
Richard Lucas
2,6461622
2,6461622
answered Dec 8 '17 at 6:27
MingMing
23122
answered Dec 8 '17 at 6:27
MingMing
23122
answered Dec 8 '17 at 6:27
MingMing
23122
23122
I tried everything possible with no luck, then I found this comment... Never even would have though it was the hypervisor in this case... Thanks for saving me another 5 hours of struggle.
– Ethode
Dec 9 '17 at 22:40
1
Yes, thanks for taking the time to record this is has saved me a lot of hassle. Does anyone know what this setting actually does - jFTR?
– diversemix
Dec 17 '17 at 21:53
I had the same problem and it actually worked. Changed to KVM and now its booting up properly.
– Dawid Pura
Mar 22 '18 at 6:48
This did it for me too, massive help!
– Michael Mallett
Oct 21 '18 at 3:36
add a comment |
I tried everything possible with no luck, then I found this comment... Never even would have though it was the hypervisor in this case... Thanks for saving me another 5 hours of struggle.
– Ethode
Dec 9 '17 at 22:40
1
Yes, thanks for taking the time to record this is has saved me a lot of hassle. Does anyone know what this setting actually does - jFTR?
– diversemix
Dec 17 '17 at 21:53
I had the same problem and it actually worked. Changed to KVM and now its booting up properly.
– Dawid Pura
Mar 22 '18 at 6:48
This did it for me too, massive help!
– Michael Mallett
Oct 21 '18 at 3:36
I tried everything possible with no luck, then I found this comment... Never even would have though it was the hypervisor in this case... Thanks for saving me another 5 hours of struggle.
– Ethode
Dec 9 '17 at 22:40
I tried everything possible with no luck, then I found this comment... Never even would have though it was the hypervisor in this case... Thanks for saving me another 5 hours of struggle.
– Ethode
Dec 9 '17 at 22:40
1
1
Yes, thanks for taking the time to record this is has saved me a lot of hassle. Does anyone know what this setting actually does - jFTR?
– diversemix
Dec 17 '17 at 21:53
Yes, thanks for taking the time to record this is has saved me a lot of hassle. Does anyone know what this setting actually does - jFTR?
– diversemix
Dec 17 '17 at 21:53
I had the same problem and it actually worked. Changed to KVM and now its booting up properly.
– Dawid Pura
Mar 22 '18 at 6:48
I had the same problem and it actually worked. Changed to KVM and now its booting up properly.
– Dawid Pura
Mar 22 '18 at 6:48
This did it for me too, massive help!
– Michael Mallett
Oct 21 '18 at 3:36
This did it for me too, massive help!
– Michael Mallett
Oct 21 '18 at 3:36
add a comment |
I had a similar problem. I'm running Linux Mint 18.1 x64 (based off 16.04 Xenial) and VirtualBox 5.0.32. I have a full/real version (not the IE tester version) of Windows 10 that was running fine in VB as installed from the ISO. This was version 1511 (build 10586).
I then tried to update to version 1703 (build 15063) and experienced exactly the same behaviour that you've described. The solution for me was to update the version of VirtualBox to 5.1.22, the latest at the time of writing. 5.0.32 was the latest available in the Ubuntu repository so I had to install the newer version from the VirtualBox apt repo as described at https://www.virtualbox.org/wiki/Linux_Downloads#Debian-basedLinuxdistributions:
Add the following line to your /etc/apt/sources.list:
deb http://download.virtualbox.org/virtualbox/debian yakkety contrib
According to your distribution, replace 'yakkety' by 'xenial',
'vivid', 'utopic', 'trusty', 'raring', 'quantal', 'precise', 'lucid',
'jessie', 'wheezy', or 'squeeze'. ... The Oracle public key for
apt-secure can be downloaded...and register[ed]:
wget -q https://www.virtualbox.org/download/oracle_vbox_2016.asc -O- | sudo apt-key add -
wget -q https://www.virtualbox.org/download/oracle_vbox.asc -O- | sudo apt-key add -
...snip...
To install VirtualBox, do
sudo apt-get update
sudo apt-get install virtualbox-5.1
...snip...
Note: Ubuntu/Debian users might want to install the
dkms
package...through the following command:
sudo apt-get install dkms
Once I updated VirtualBox, I performed the update in the guest and after restart I almost instantly saw the white dot spinner appear on the black screen with the cyan windows logo (that you've attached) as you'd expect.
answered Jul 4 '17 at 2:39
Tom SaleebaTom Saleeba
1314
Would it be best to remove your existing Ubuntu-distributed VirtualBox installation before performing this procedure, or will this upgrade it? Or can you run them in parallel? Will your existing configurations be maintained?
– k-den
Aug 16 '17 at 18:46
I tried these steps without removing the existing Ubuntu-distributed VirtualBox, and now when I try to open the Win 10 image previously imported it says "RTR3InitEx failed with rc=-1912 The VirtualBox kernel modules do not match this version of VirtualBox. The installation of VirtualBox was apparently not successful. Executing '/sbin/vboxconfig' may correct this. Make sure that you do not mix the OSE version and the PUEL version of VirtualBox..." Executing /sbin/vboxconfig did not fix it.
– k-den
Aug 16 '17 at 18:58
@k-den I think apt should perform an upgrade and keep all your settings, at least that's what happened to me. As you're running into trouble, it might be best to backup the virtualbox config (have to Google where that lives) theapt-get purgeall versions of virtualbox from your system, then install a fresh copy. Alternatively, you might just have to restart your system if it hasn't picked up the new kernel modules.
– Tom Saleeba
Aug 17 '17 at 0:34
add a comment |
I had a similar problem. I'm running Linux Mint 18.1 x64 (based off 16.04 Xenial) and VirtualBox 5.0.32. I have a full/real version (not the IE tester version) of Windows 10 that was running fine in VB as installed from the ISO. This was version 1511 (build 10586).
I then tried to update to version 1703 (build 15063) and experienced exactly the same behaviour that you've described. The solution for me was to update the version of VirtualBox to 5.1.22, the latest at the time of writing. 5.0.32 was the latest available in the Ubuntu repository so I had to install the newer version from the VirtualBox apt repo as described at https://www.virtualbox.org/wiki/Linux_Downloads#Debian-basedLinuxdistributions:
Add the following line to your /etc/apt/sources.list:
deb http://download.virtualbox.org/virtualbox/debian yakkety contrib
According to your distribution, replace 'yakkety' by 'xenial',
'vivid', 'utopic', 'trusty', 'raring', 'quantal', 'precise', 'lucid',
'jessie', 'wheezy', or 'squeeze'. ... The Oracle public key for
apt-secure can be downloaded...and register[ed]:
wget -q https://www.virtualbox.org/download/oracle_vbox_2016.asc -O- | sudo apt-key add -
wget -q https://www.virtualbox.org/download/oracle_vbox.asc -O- | sudo apt-key add -
...snip...
To install VirtualBox, do
sudo apt-get update
sudo apt-get install virtualbox-5.1
...snip...
Note: Ubuntu/Debian users might want to install the
dkms
package...through the following command:
sudo apt-get install dkms
Once I updated VirtualBox, I performed the update in the guest and after restart I almost instantly saw the white dot spinner appear on the black screen with the cyan windows logo (that you've attached) as you'd expect.
answered Jul 4 '17 at 2:39
Tom SaleebaTom Saleeba
1314
Would it be best to remove your existing Ubuntu-distributed VirtualBox installation before performing this procedure, or will this upgrade it? Or can you run them in parallel? Will your existing configurations be maintained?
– k-den
Aug 16 '17 at 18:46
I tried these steps without removing the existing Ubuntu-distributed VirtualBox, and now when I try to open the Win 10 image previously imported it says "RTR3InitEx failed with rc=-1912 The VirtualBox kernel modules do not match this version of VirtualBox. The installation of VirtualBox was apparently not successful. Executing '/sbin/vboxconfig' may correct this. Make sure that you do not mix the OSE version and the PUEL version of VirtualBox..." Executing /sbin/vboxconfig did not fix it.
– k-den
Aug 16 '17 at 18:58
@k-den I think apt should perform an upgrade and keep all your settings, at least that's what happened to me. As you're running into trouble, it might be best to backup the virtualbox config (have to Google where that lives) theapt-get purgeall versions of virtualbox from your system, then install a fresh copy. Alternatively, you might just have to restart your system if it hasn't picked up the new kernel modules.
– Tom Saleeba
Aug 17 '17 at 0:34
add a comment |
I had a similar problem. I'm running Linux Mint 18.1 x64 (based off 16.04 Xenial) and VirtualBox 5.0.32. I have a full/real version (not the IE tester version) of Windows 10 that was running fine in VB as installed from the ISO. This was version 1511 (build 10586).
I then tried to update to version 1703 (build 15063) and experienced exactly the same behaviour that you've described. The solution for me was to update the version of VirtualBox to 5.1.22, the latest at the time of writing. 5.0.32 was the latest available in the Ubuntu repository so I had to install the newer version from the VirtualBox apt repo as described at https://www.virtualbox.org/wiki/Linux_Downloads#Debian-basedLinuxdistributions:
Add the following line to your /etc/apt/sources.list:
deb http://download.virtualbox.org/virtualbox/debian yakkety contrib
According to your distribution, replace 'yakkety' by 'xenial',
'vivid', 'utopic', 'trusty', 'raring', 'quantal', 'precise', 'lucid',
'jessie', 'wheezy', or 'squeeze'. ... The Oracle public key for
apt-secure can be downloaded...and register[ed]:
wget -q https://www.virtualbox.org/download/oracle_vbox_2016.asc -O- | sudo apt-key add -
wget -q https://www.virtualbox.org/download/oracle_vbox.asc -O- | sudo apt-key add -
...snip...
To install VirtualBox, do
sudo apt-get update
sudo apt-get install virtualbox-5.1
...snip...
Note: Ubuntu/Debian users might want to install the
dkms
package...through the following command:
sudo apt-get install dkms
Once I updated VirtualBox, I performed the update in the guest and after restart I almost instantly saw the white dot spinner appear on the black screen with the cyan windows logo (that you've attached) as you'd expect.
answered Jul 4 '17 at 2:39
Tom SaleebaTom Saleeba
1314
I had a similar problem. I'm running Linux Mint 18.1 x64 (based off 16.04 Xenial) and VirtualBox 5.0.32. I have a full/real version (not the IE tester version) of Windows 10 that was running fine in VB as installed from the ISO. This was version 1511 (build 10586).
I then tried to update to version 1703 (build 15063) and experienced exactly the same behaviour that you've described. The solution for me was to update the version of VirtualBox to 5.1.22, the latest at the time of writing. 5.0.32 was the latest available in the Ubuntu repository so I had to install the newer version from the VirtualBox apt repo as described at https://www.virtualbox.org/wiki/Linux_Downloads#Debian-basedLinuxdistributions:
Add the following line to your /etc/apt/sources.list:
deb http://download.virtualbox.org/virtualbox/debian yakkety contrib
According to your distribution, replace 'yakkety' by 'xenial',
'vivid', 'utopic', 'trusty', 'raring', 'quantal', 'precise', 'lucid',
'jessie', 'wheezy', or 'squeeze'. ... The Oracle public key for
apt-secure can be downloaded...and register[ed]:
wget -q https://www.virtualbox.org/download/oracle_vbox_2016.asc -O- | sudo apt-key add -
wget -q https://www.virtualbox.org/download/oracle_vbox.asc -O- | sudo apt-key add -
...snip...
To install VirtualBox, do
sudo apt-get update
sudo apt-get install virtualbox-5.1
...snip...
Note: Ubuntu/Debian users might want to install the
dkms
package...through the following command:
sudo apt-get install dkms
Once I updated VirtualBox, I performed the update in the guest and after restart I almost instantly saw the white dot spinner appear on the black screen with the cyan windows logo (that you've attached) as you'd expect.
answered Jul 4 '17 at 2:39
Tom SaleebaTom Saleeba
1314
answered Jul 4 '17 at 2:39
Tom SaleebaTom Saleeba
1314
answered Jul 4 '17 at 2:39
Tom SaleebaTom Saleeba
1314
answered Jul 4 '17 at 2:39
Tom SaleebaTom Saleeba
1314
1314
Would it be best to remove your existing Ubuntu-distributed VirtualBox installation before performing this procedure, or will this upgrade it? Or can you run them in parallel? Will your existing configurations be maintained?
– k-den
Aug 16 '17 at 18:46
I tried these steps without removing the existing Ubuntu-distributed VirtualBox, and now when I try to open the Win 10 image previously imported it says "RTR3InitEx failed with rc=-1912 The VirtualBox kernel modules do not match this version of VirtualBox. The installation of VirtualBox was apparently not successful. Executing '/sbin/vboxconfig' may correct this. Make sure that you do not mix the OSE version and the PUEL version of VirtualBox..." Executing /sbin/vboxconfig did not fix it.
– k-den
Aug 16 '17 at 18:58
@k-den I think apt should perform an upgrade and keep all your settings, at least that's what happened to me. As you're running into trouble, it might be best to backup the virtualbox config (have to Google where that lives) theapt-get purgeall versions of virtualbox from your system, then install a fresh copy. Alternatively, you might just have to restart your system if it hasn't picked up the new kernel modules.
– Tom Saleeba
Aug 17 '17 at 0:34
add a comment |
Would it be best to remove your existing Ubuntu-distributed VirtualBox installation before performing this procedure, or will this upgrade it? Or can you run them in parallel? Will your existing configurations be maintained?
– k-den
Aug 16 '17 at 18:46
I tried these steps without removing the existing Ubuntu-distributed VirtualBox, and now when I try to open the Win 10 image previously imported it says "RTR3InitEx failed with rc=-1912 The VirtualBox kernel modules do not match this version of VirtualBox. The installation of VirtualBox was apparently not successful. Executing '/sbin/vboxconfig' may correct this. Make sure that you do not mix the OSE version and the PUEL version of VirtualBox..." Executing /sbin/vboxconfig did not fix it.
– k-den
Aug 16 '17 at 18:58
@k-den I think apt should perform an upgrade and keep all your settings, at least that's what happened to me. As you're running into trouble, it might be best to backup the virtualbox config (have to Google where that lives) theapt-get purgeall versions of virtualbox from your system, then install a fresh copy. Alternatively, you might just have to restart your system if it hasn't picked up the new kernel modules.
– Tom Saleeba
Aug 17 '17 at 0:34
Would it be best to remove your existing Ubuntu-distributed VirtualBox installation before performing this procedure, or will this upgrade it? Or can you run them in parallel? Will your existing configurations be maintained?
– k-den
Aug 16 '17 at 18:46
Would it be best to remove your existing Ubuntu-distributed VirtualBox installation before performing this procedure, or will this upgrade it? Or can you run them in parallel? Will your existing configurations be maintained?
– k-den
Aug 16 '17 at 18:46
I tried these steps without removing the existing Ubuntu-distributed VirtualBox, and now when I try to open the Win 10 image previously imported it says "RTR3InitEx failed with rc=-1912 The VirtualBox kernel modules do not match this version of VirtualBox. The installation of VirtualBox was apparently not successful. Executing '/sbin/vboxconfig' may correct this. Make sure that you do not mix the OSE version and the PUEL version of VirtualBox..." Executing /sbin/vboxconfig did not fix it.
– k-den
Aug 16 '17 at 18:58
I tried these steps without removing the existing Ubuntu-distributed VirtualBox, and now when I try to open the Win 10 image previously imported it says "RTR3InitEx failed with rc=-1912 The VirtualBox kernel modules do not match this version of VirtualBox. The installation of VirtualBox was apparently not successful. Executing '/sbin/vboxconfig' may correct this. Make sure that you do not mix the OSE version and the PUEL version of VirtualBox..." Executing /sbin/vboxconfig did not fix it.
– k-den
Aug 16 '17 at 18:58
@k-den I think apt should perform an upgrade and keep all your settings, at least that's what happened to me. As you're running into trouble, it might be best to backup the virtualbox config (have to Google where that lives) the
apt-get purge all versions of virtualbox from your system, then install a fresh copy. Alternatively, you might just have to restart your system if it hasn't picked up the new kernel modules.– Tom Saleeba
Aug 17 '17 at 0:34
@k-den I think apt should perform an upgrade and keep all your settings, at least that's what happened to me. As you're running into trouble, it might be best to backup the virtualbox config (have to Google where that lives) the
apt-get purge all versions of virtualbox from your system, then install a fresh copy. Alternatively, you might just have to restart your system if it hasn't picked up the new kernel modules.– Tom Saleeba
Aug 17 '17 at 0:34
add a comment |
I had this issue too. I got it working by updating Virtualbox to version 5.0.40 and changing the general settings tab to other for both type and version.
$sudo apt autoremove --purge virtualbox*
$sudo apt install virtualbox=5.0.40-dfsg-0ubuntu1.16.04.1
Name: Windows 10
Type: Other
Version: Other/Unknown(64-bit)
edited Oct 15 '17 at 23:05
Pimp Juice IT
24.7k113974
answered Oct 15 '17 at 21:25
Arnaldo GArnaldo G
1
add a comment |
I had this issue too. I got it working by updating Virtualbox to version 5.0.40 and changing the general settings tab to other for both type and version.
$sudo apt autoremove --purge virtualbox*
$sudo apt install virtualbox=5.0.40-dfsg-0ubuntu1.16.04.1
Name: Windows 10
Type: Other
Version: Other/Unknown(64-bit)
edited Oct 15 '17 at 23:05
Pimp Juice IT
24.7k113974
answered Oct 15 '17 at 21:25
Arnaldo GArnaldo G
1
add a comment |
I had this issue too. I got it working by updating Virtualbox to version 5.0.40 and changing the general settings tab to other for both type and version.
$sudo apt autoremove --purge virtualbox*
$sudo apt install virtualbox=5.0.40-dfsg-0ubuntu1.16.04.1
Name: Windows 10
Type: Other
Version: Other/Unknown(64-bit)
edited Oct 15 '17 at 23:05
Pimp Juice IT
24.7k113974
answered Oct 15 '17 at 21:25
Arnaldo GArnaldo G
1
I had this issue too. I got it working by updating Virtualbox to version 5.0.40 and changing the general settings tab to other for both type and version.
$sudo apt autoremove --purge virtualbox*
$sudo apt install virtualbox=5.0.40-dfsg-0ubuntu1.16.04.1
Name: Windows 10
Type: Other
Version: Other/Unknown(64-bit)
edited Oct 15 '17 at 23:05
Pimp Juice IT
24.7k113974
answered Oct 15 '17 at 21:25
Arnaldo GArnaldo G
1
edited Oct 15 '17 at 23:05
Pimp Juice IT
24.7k113974
edited Oct 15 '17 at 23:05
Pimp Juice IT
24.7k113974
edited Oct 15 '17 at 23:05
Pimp Juice IT
24.7k113974
24.7k113974
answered Oct 15 '17 at 21:25
Arnaldo GArnaldo G
1
answered Oct 15 '17 at 21:25
Arnaldo GArnaldo G
1
answered Oct 15 '17 at 21:25
Arnaldo GArnaldo G
1
1
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1224949%2fwindows-10-guest-os-stuck-booting-in-virtualbox-on-ubuntu-16-04-host%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Disable other process then run VM. What's your CPU Max cycle?
– Biswapriyo
Jul 2 '17 at 12:25
May not be exactly the same, but similar issue and a fix superuser.com/a/1263414/106974
– IsaacS
Dec 5 '17 at 0:02