Windows 10 Build 15002+ - VirtualBox fails to start

For discussions related to using VirtualBox on Windows pre-releases (e.g. Windows 10 > build 10240).
Dan Bennett
Posts: 3
Joined: 15. Feb 2017, 11:07

Re: Windows 10 Build 15002+ - VirtualBox fails to start

Post by Dan Bennett »

Wow. Didn't think I'd be jumped at for posting here... my apologies for raising, then? I thought posting here would be more helpful to yourselves and myself instead of coming here to feel small for doing such thing...

I did say:
Not on the insider preview.
Likewise, the issue occurs with all VMs, including new VMs (without any ISO attatched either). Windows *DID* do an update a week or so ago when I first started seeing the issue.

The other option here is a driver update could've caused this... but trying to work that one out is seemingly difficult due to the errors given.

Apologies if this is "not the right thread" but considering I see others being pointed to here to avoid multiple posts of the same issue, I thought it'd be best to do that. Hey ho...

Thanks for making me feel welcome :-)
socratis
Site Moderator
Posts: 27329
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 Build 15002+ - VirtualBox fails to start

Post by socratis »

Dan Bennett wrote:Not on the insider preview.
So, if you said "Not on OSX host" you think it would be wise to post on the "OSX Hosts" section? That's why there are specific forums, so that the noise to signal ratio goes down. Pointing to you that you're in the wrong place is not "not welcoming you". It's just pointing you to the right direction.

If this was a standalone topic I would have moved it and pointed out your mistake. That's how it works. You can't be expecting a congratulatory letter and a pat in the back for not doing the appropriate thing...
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.
Dan Bennett
Posts: 3
Joined: 15. Feb 2017, 11:07

Re: Windows 10 Build 15002+ - VirtualBox fails to start

Post by Dan Bennett »

Then I apologize for attempting to be useful by stating I have the exact same issue but not on the Insider Preview.

Your overall tone of your posts is what is rude. But hey... nevermind. I'll go again.
Jacob Klein
Posts: 696
Joined: 20. Nov 2013, 01:07

Re: Windows 10 Build 15002+ - VirtualBox fails to start

Post by Jacob Klein »

Hi Dan,

First of all, we've worked very hard to get this forum to be a place of sorted information for preview releases. You should have seen what was going down, when the Insider program was first starting up and this subforum didn't exist -- I'd post a problem, and get the 3rd degree since I'm running a preview prerelease OS, and my posts would even get deleted, and I couldn't open tickets either, because it was a prerelease OS. Long story short, I convinced them that we, the community, needed a place to collect info on crashes with the Windows Insider program, so they created this forum "VirtualBox on Windows pre-releases" specifically because of people like me. So again, you really need to be posting in a non-pre-release forum.

Secondly, your issue is very clearly not the same. If you read the first post very carefully, it says "Any attempt to launch "Oracle VM VirtualBox" results in a WerFault.exe instance.", and even has the build number where the error started, build 15002+. Your issue is much different - you CAN launch the program! Then, when you try to start a VM, you get an error (yes, I see it's "0xc0000005", but that's a generic NULL EXCEPTION error code I believe), and so your problem is that process hardening is interfering with your ability to start a VM. Very different from this thread's problem.

Thirdly, you necromanced an old thread. The bug in this thread has been fixed a long time ago, if you read through the thread to see. Over a month ago, I confirmed fixes for this thread's problem, in this post:
viewtopic.php?f=38&t=81351&start=15#p382743
... and most people consider it really bad form, to reopen an old thread that had been fully solved.

Finally, to get back to your problem... Look. Oracle VirtualBox process hardening can be very difficult to work with at times. If it doesn't find signed info for everything about your OS that it needs, then it won't allow the VM to be started, because it could be injected into and is thus (to Oracle) considered insecure. To SOLVE your issue, you need to carefully work backward to figure out what the problem is -- taking notes at each step. Uninstall your Antivirus (and take a note), restart the PC, retest with both old VM and new VM. If it still doesn't work, uninstall any themes/mods (like Start menu changers, UI changers, etc) ONE AT A TIME (and take a note), restart the PC, retest. If that doesn't work, keep uninstalling stuff you'd think would interfere, until you find it. If THAT doesn't work, then you could "start fresh" with a clean install of Windows, and work FORWARD, testing after every install+restart. Hopefully, eventually, you'll find out which piece of software is interfering, then you can reinstall the rest, then you can report the problem to Oracle. If it's unsigned software, they probably will NOT whitelist it. If it's signed but interfering, they may fix it, if you report it kindly.... not in this forum :-p

Welcome, friend. I wish you luck in your adventure!
Jacob Klein
michaln
Oracle Corporation
Posts: 2973
Joined: 19. Dec 2007, 15:45
Primary OS: MS Windows 7
VBox Version: PUEL
Guest OSses: Any and all
Contact:

Re: Windows 10 Build 15002+ - VirtualBox fails to start

Post by michaln »

Just to be clear: Oracle does not in practice define what is insecure and what isn't. 3rd party security researchers do. It's the same with other software products.
Post Reply