The virtual machine 'test1' has terminated unexpectedly during startup with exit code 1 (0x1).
Result Code:
NS_ERROR_FAILURE (0x80004005)
Component:
MachineWrap
Interface:
IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}
I was tryig to paste the code, but the forum saw the apple<dot>com in the output and said
You must be a member for 1 days and have 1 posts before you can post urls.
I split your post from the thread "VirtualBox fails to run on macOS High Sierra - kernel driver not loaded", since you clearly do *NOT* have the same issue. An error message can be due to a lot of things, even if it has the same error code. You didn't even have the same error code, why would you think that it's the same problem? Yours is definitely not due to the kernel extension not being loaded, they load just fine:
I'll need to do a bit further of analysis in the afternoon to see what might be going on with your setup, but I can see that you have 3 (three) different pieces of software that are "protecting" your OSX. I would start uninstalling them one by one and see who's the culprit; Symantec, Websense and Cisco SourceFire.
PS. Kudos for studying previous threads and submitting the appropriate information!
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.
Yea my apologies for submitting to that thread, I assumed it was a similar issue since it started with high serria. I should have done some further investigation.
I'll take a look at the software for this laptop installed by my helpdesk, but it all was "protecting" before the update to 10.13. Much of this software is disabled from taking active prevention measures given the challenges this active enforcement and my own Infra and development work.
Did you re-install VirtualBox after the 10.13 upgrade? Did you install the Supplemental Update for 10.13? Can you try with the just released VirtualBox 5.2.0?
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.
remerolle wrote:no improvement. The GUI's error message looks prettier though!
Hey, that's an improvement right there!
I still think that something might be wrong with your installed software that is interfering with the proper secure operation of VirtualBox. As I mentioned, please uninstall all of them and start adding them back one at a time, while testing VirtualBox in-between.
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.
Thank you for being willful to try it, even go as far as reinstalling OSX !
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.
Had the same error code after upgrading to virtual box 5.2. (after Mac OS 10.13 upgrade)
In my case the virtual box extension pack wasn't upgraded so i did the following:
1) Start virtual box and check for updates
2) First it says everything is up to date but a few moments later the update link for the extension pack pops up
3) Installed new extension pack
4) All vm´s could be started as before
Great, thanks for the feedback. Do you feel confident enough to mark this topic as [Solved]? I've always said that VirtualBox doesn't fail in a clean installation, but that's not always the suggested method of "fixing" potential issues...
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.