Oracle VirtualBox won't open in Build 14942
-
Oracle VirtualBox won't open in Build 14942
I had a bit of trouble updating to build 14942 but with help from this forum, I completed the update.
Now, I find that I can no longer open Oracle VirtualBox. In the announcement for build 14926, it announced that VirtualBox would crash with this build. It did not crash but worked fine. There is nothing in the announcement for the current build about VirtualBox but I cannot make it open.
Will this be fixed in the next build?
Thank you,
Ken Gash
-
-
I had a bit of trouble updating to build 14942 but with help from this forum, I completed the update.
Now, I find that I can no longer open Oracle VirtualBox. In the announcement for build 14926, it announced that VirtualBox would crash with this build. It did not crash but worked fine. There is nothing in the announcement for the current build about VirtualBox but I cannot make it open.
Will this be fixed in the next build?
Thank you,
Ken Gash
same here it worked fine for releases they noted it shouldn't work but breaks with 14942. hopefully a fix will come from VirtualBox sooner than Microsoft cause this kills my workflow.
is it possible to downgrade to 14926?
-
I had a bit of trouble updating to build 14942 but with help from this forum, I completed the update.
Now, I find that I can no longer open Oracle VirtualBox. In the announcement for build 14926, it announced that VirtualBox would crash with this build. It did not crash but worked fine. There is nothing in the announcement for the current build about VirtualBox but I cannot make it open.
Will this be fixed in the next build?
Thank you,
Ken Gash
Hard to say as it may be vb that needs updating. Frankly, I always use vmware player rather than vb on Home as it is generally more reliable in my opinion. On pro - no contest - use hyper-v.
Have you simply tried uninstalling and reinstalling latest version of vb?
-
-
Hard to say as it may be vb that needs updating. Frankly, I always use vmware player rather than vb on Home as it is generally more reliable in my opinion. On pro - no contest - use hyper-v.
Have you simply tried uninstalling and reinstalling latest version of vb?
What are the benefits of hyper v? I am on pro and use virtualbox cause i thought it was simpler.
-
-
thanks! I'll give it a go
-
same here it worked fine for releases they noted it shouldn't work but breaks with 14942. hopefully a fix will come from VirtualBox sooner than Microsoft cause this kills my workflow.
is it possible to downgrade to 14926?
Provided you have at least one of the older Windows versions still on your computer you should be able to do so quite easily. I downgraded one of my test machines back to build 19436 yesterday due to the issue with VirtualBox not working on build 14942. This post helped me do the change How To Revert to an Earlier Build of Windows 10.
But it was a pain in that all of my saved passwords and sites were no longer saved once I reverted back. Kind of odd since they were there originally when I upgraded initially. I guess it is a security thing.
-
I considered downgrading to previous build but, since I only use the virtual machine infrequently, I decided to try Hyper-v. Activating it in Windows was fairly straightforward but actually using it with a guest OS (XPPRO) was unnecessarily complex I switched to VMWare Player and was impressed with the slickness of the installation and the creation of the guest os. I'll probably not go back to VirtualBox even after Windows fixes this bug.
What is still disturbing is that I cannot use Malwarebytes with this build because as soon as I open it I get the new Windows BSOD.
-
-
I considered downgrading to previous build but, since I only use the virtual machine infrequently, I decided to try Hyper-v. Activating it in Windows was fairly straightforward but actually using it with a guest OS (XPPRO) was unnecessarily complex I switched to VMWare Player and was impressed with the slickness of the installation and the creation of the guest os. I'll probably not go back to VirtualBox even after Windows fixes this bug.
What is still disturbing is that I cannot use Malwarebytes with this build because as soon as I open it I get the new Windows BSOD.
I gave up on vb a long time ago - vmware is just a lot more reliable in my experience. To date, I have never heard of vmware failing on w10 since its launch. Same is not true for virtualbox. Not sure about issue with xppro but in the end hyper-v generally still shines over vb or vm.