Failed to open a session for the virtual machine W10ENT-Gold.
The virtual machine 'W10ENT-Gold' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\username\VirtualBox VMs\W10ENT-Gold\Logs\VBoxHardening.log'.
Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {5047460a-265d-4538-b23e-ddba5fb84976}
VBox Unable to Launch VMs on Windows 10
VBox Unable to Launch VMs on Windows 10
I am running Version 6.0.0 r127566 (Qt5.6.2) on Windows 10 Ent 1709. This is a fresh install of Vbox. I've looked for "FindAdversaries" in the hardening file but all entries show 0x0 causing me to assume there aren't any other apps causing issues. Any help is much appreciated.
Last edited by socratis on 16. Jan 2019, 01:26, edited 1 time in total.
Reason: Enclosed the information in [quote] tags for better readability.
Reason: Enclosed the information in [quote] tags for better readability.
-
- 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: VBox Unable to Launch VMs on Windows 10
You have a hardening problem. Please read really carefully the following FAQ: Diagnosing VirtualBox Hardening Issues for some guidelines/ideas.3378.3258: supR3HardNtChildWaitFor[1]: Quitting: ExitCode=0x1 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 58360 ms, the end);
Remember these are guidelines, you should use your judgement as to which problem might be causing this...
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.
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.
Re: VBox Unable to Launch VMs on Windows 10
I seem to be facing the same. Assuming I am understanding the hardening log correctly I believe the cause is McAfee. However, I have not seen it mentioned as causing the issue before and others are using it with VirtualBox and no problem.
windows 10 Enterprise version 1709 (os build 16299.785)
Virtual Box Version 5.2.24 r128163
trying to start an image I get the following error:
84.20a8: Error (rc=-5640):
84.20a8: More than one thread in process
viewing the log the offender appears to be:
84.20a8: ProductName: SYSCORE
84.20a8: ProductVersion: 15.8.0.412
84.20a8: FileVersion: SYSCORE.15.8.0.412
this is a corporate laptop and I am not able to uninstall McAfee antivirus.
There are others here running McAfee and VirtualBox with no issues and my understanding is that mainstream AV products should be ok.
have tried suggestions listed related to hardening:
run sfc /scannow - no issues found
modify the registry / and VBoxDrv.inf for on demand start (workarounds listed in vbox forum)
installing different versions of VirtualBox including most recent 6.0
my virtual box install and vms are in a McAfee exclusion directory
Is the antivirus software the culprit? Is there anything else that can be done?
Thanks
windows 10 Enterprise version 1709 (os build 16299.785)
Virtual Box Version 5.2.24 r128163
trying to start an image I get the following error:
84.20a8: Error (rc=-5640):
84.20a8: More than one thread in process
viewing the log the offender appears to be:
84.20a8: ProductName: SYSCORE
84.20a8: ProductVersion: 15.8.0.412
84.20a8: FileVersion: SYSCORE.15.8.0.412
this is a corporate laptop and I am not able to uninstall McAfee antivirus.
There are others here running McAfee and VirtualBox with no issues and my understanding is that mainstream AV products should be ok.
have tried suggestions listed related to hardening:
run sfc /scannow - no issues found
modify the registry / and VBoxDrv.inf for on demand start (workarounds listed in vbox forum)
installing different versions of VirtualBox including most recent 6.0
my virtual box install and vms are in a McAfee exclusion directory
Is the antivirus software the culprit? Is there anything else that can be done?
Thanks
- Attachments
-
- VBoxHardening.zip
- (12.82 KiB) Downloaded 11 times
Last edited by socratis on 18. Jan 2019, 08:23, edited 1 time in total.
Reason: Removed unnecessary verbatim quote of the whole previous message.
Reason: Removed unnecessary verbatim quote of the whole previous message.
-
- 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: VBox Unable to Launch VMs on Windows 10
Let me suggest a couple of Microsoft tool for checking the signatures; signtool and sigcheck. The first comes with the Windows SDK. The latter is from the former SysInternals (now Microsoft) and I haven't tried it, but looking at its documentation, I think it does the job.
Also check:
Also check:
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.
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.