Opened 8 years ago
Closed 8 years ago
#16755 closed defect (worksforme)
Unable to open any virtual machines after VirtualBox Update
Reported by: | CarlosAR | Owned by: | |
---|---|---|---|
Component: | other | Version: | VirtualBox 5.1.22 |
Keywords: | E_FAIL (0x80004005) | Cc: | |
Guest type: | Linux | Host type: | Windows |
Description
Hello,
I use Virtual Box, and always update to the latest version when available. I was in VirtualBox-5.0.16-105871-Win, hence no more recent version works, I tried VirtualBox-5.1.16-113841-Win, VirtualBox-5.1.18-114002-Win, VirtualBox-5.1.20-114628 -Win and VirtualBox-5.1.22-115126-Win, all can not initialize the virtual machines.
I get the following error:
Failed to open a session for the Ubuntu virtual machine - Server - PHP.
The virtual machine 'Ubuntu - Server - PHP' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'D: \ VirtualBox \ Ubuntu - Server - PHP \ Logs \ VBoxHardening.log'.
Result Code: E_FAIL (0x80004005) Component: MachineWrap Interface: IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}
Host: Windows Server 2008 R2 Enterprise
All log files are attached.
Thank you.
Attachments (1)
Change History (5)
by , 8 years ago
comment:1 by , 8 years ago
comment:2 by , 8 years ago
Hi, thanks for the help, but it seems that Malwerbytes was not alone in charge of the problem; I made an exception rule for virtualbox on it and also uninstalled, and this did not solve the problem. I read the FAQ and I was eliminating the possibilities, I found in vbox.log an entry saying that my user32.dll was not signed, I executed a "sfc / scannow" and some files were fixed, rebooted, and everything worked again. Thanks, sorry for taking the developers time. All the tikets I've visualized with the same error message, did not say a solution.
comment:3 by , 8 years ago
Thanks for the feedback. I guess the ticket can be closed as "Worksforme" ;)
comment:4 by , 8 years ago
Resolution: | → worksforme |
---|---|
Status: | new → closed |
Please read the following FAQ: Diagnosing VirtualBox Hardening Issues.
In your case it might be Malwarebytes Anti-Malware that's causing this. Add an exception for VirtualBox, disable Malwarebyts, or uninstall it. See if it makes a difference.
May I suggest something? It's usually better and faster, if problems like this one get first addressed in the forums (https://forums.virtualbox.org/). More than 95% of the issues are resolved over there, which keeps the developers focusing on the bug fixes and enhancements, and there is no need for another ticket to keep track of. For example, yours is most probably not a bug and someone from the developers has to deal with it and close it as "Invalid".