Virtualbox won't start on Preview Build 14332

[mfelker]

The non-starting situation has returned with Insider Preview Build 14332

[michaln]

We failed to guess the VirtualBox revision you're using.

[TheUntouchable]

Can't confirm, using test 6880 build of vb and 14332 of Win10 and I have absolutely no problem!

[mfelker]

Sorry for not posting my version of VB. It is the latest - 5.18 on a clean install of Build 14332. Tried installling/uninstalling several times. VB never started. However I'm dual booting with openSUSE Tumbleweed and no problems on the Linux side.

I can post my system specs if that matters (once I boot back to Windows) but that wouuldn't make a difference. If there is a beta build of 5.19 I can try that - haven't looked for it yet.

[TimDugan]

Preview Build 14322, for a change, doesn't break VB test build 106880, but there is even a newer test build 106900 (not yet tried).

[mfelker]

Virtualbox 106900Test Build 5.0.19r 106900 does work on my Preview Build 14332 w 5.0.18 extension pack. Since this machine is basically "blending edge" I'll stick with this version in Windows and in fact will install the Linux version of the Test Build when I boot to openSUSE again.

[mfelker]

Virtualbox 5.0.20 was just released and it works perfectly on Windows Preview 14332 & openSUSE Tumbleweed

[Davide3i]

Someone still has the "VirtualBox-5.0.19-r106900-MultiArch_amd64.msi" file?
I need it to install the new 5.0.20 version, but my Windows took a nice clean to "AppData\Local\Temp".
Thank you.

[wholroyd]

Someone still has the "VirtualBox-5.0.19-r106900-MultiArch_amd64.msi" file?
I need it to install the new 5.0.20 version, but my Windows took a nice clean to "AppData\Local\Temp".
Thank you.

https://www.virtualbox.org/download/tes ... 00-Win.exe

When you go to run it, the MSI should be extracted to C:\Users\[username]\AppData\Local\Temp\VirtualBox

[Davide3i]

https://www.virtualbox.org/download/tes ... 00-Win.exe

When you go to run it, the MSI should be extracted to C:\Users\[username]\AppData\Local\Temp\VirtualBox

Thank you very much!

[wdupree]

Hmm... something happened for me. Tried to update to .20 and had a BSOD when trying to start the VM. After that tried uninstalling and going back to .19 and forward to .21 (test build) to no avail - BSOD's on all three now :/

[abadi]

I'm getting BSOD as well running VirtualBox 5.0.21-106969 on Windows 10 Preview Build 14332. Have you figure out a way to solve this?

Hmm... something happened for me. Tried to update to .20 and had a BSOD when trying to start the VM. After that tried uninstalling and going back to .19 and forward to .21 (test build) to no avail - BSOD's on all three now :/

[abadi]

I figured out my BSOD issue. It was because the insider build upgrade messed up my windows boot loader and changed my "hypervisorlaunchtype" from "Off" to "Auto", and running virtualbox with hypervisor will cause BSOD. So I just set the value back to "Off" and it's working now.

Hmm... something happened for me. Tried to update to .20 and had a BSOD when trying to start the VM. After that tried uninstalling and going back to .19 and forward to .21 (test build) to no avail - BSOD's on all three now :/