VirtualBox

Opened 5 years ago

Last modified 5 years ago

#18481 new defect

Upgraded to 6.x and now VB is broken

Reported by: brentd36 Owned by:
Component: other Version: VirtualBox 6.0.4
Keywords: Cc:
Guest type: other Host type: Windows

Description

I had as good running system with v 5.2 installed and several VMs 1) Win 10 64 bit / Win Defender off except for Fire wall / Malware bytes 2) I have downgraded and removed all "User" files and program files several times 3) I have tried in safe mode and also disabled malware bytes / same error 4) I do not have any new Windows Updates installed

System was fully functioning until I ran the 6.x update which took 15 minutes and hung / now system is dead Will attach hardening log and screenshot / I have read the forums on this and none of the "fixes" work

Result Code: E_FAIL (0x80004005) Component: MachineWrap Interface: IMachine {f30138d4-e5ea-4b3a-8858-a059de4c93fd}

Attachments (2)

VBoxHardening.log (10.7 KB ) - added by brentd36 5 years ago.
fail.jpg (29.3 KB ) - added by brentd36 5 years ago.

Download all attachments as: .zip

Change History (3)

by brentd36, 5 years ago

Attachment: VBoxHardening.log added

by brentd36, 5 years ago

Attachment: fail.jpg added

in reply to:  description comment:1 by Socratis, 5 years ago

Replying to brentd36:

I had as good running system with v 5.2 installed and several VMs

  1. Win 10 64 bit / Win Defender off except for Fire wall / Malware bytes
  2. ...
  3. I have tried in safe mode and also disabled malware bytes / same error

Disabling sometimes is not enough, you may need to either:

  1. completely uninstall MalwareBytes,
  2. update/reinstall it so that either the signatures are proper or the Windows Certificate Database gets updated, or
  3. add an exception to MalwareBytes for all things related to VirtualBox.

For more information and other culprits, read really carefully the following FAQ: Diagnosing VirtualBox Hardening Issues for some generic guidelines/ideas. Those are guidelines, you have to use your judgement as to which program might be responsible...

Speaking of forums, it's usually better and faster, if issues get first addressed in the VirtualBox forums, a lot more eyes there. More than 95% of the issues are resolved in the forums, 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 not a bug and someone from the developers has to deal with it and close it as "Invalid".

Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use