Machinewrap error using windows 10

[MD89]

Failed to open a session for the virtual machine ubuntu64.

The virtual machine 'ubuntu64' has terminated unexpectedly during startup with exit code 1 (0x1).

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

VboxHardeninglog is attached

[socratis]

Please read really carefully the following FAQ: Diagnosing VirtualBox Hardening Issues for some guidelines/ideas. I'd start with Malwarebytes...

PS. For future reference you should ZIP your logs. It helps save a (virtual) tree or two...

[MD89]

I whitelisted Oracle folder on Malwarebytes

[socratis]

OK, that's interesting to hear. But, the question is: did that fix your problem?

[MD89]

Sadly, it did not. I checked the log file and looked at the last line as stated in the guide.

Here is where the error starts

14bc.1ab4: Error (rc=0):
14bc.1ab4: supR3HardenedScreenImage/NtCreateSection: cached rc=Unknown Status -626 (0xfffffd8e) fImage=1 fProtect=0x10 fAccess=0xf cHits=4 \Device\HarddiskVolume4\Windows\System32\bcrypt.dll
14bc.1ab4: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0xc0000190 'C:\Program Files\Oracle\VirtualBox\VirtualBox.dll'
21ac.1698: supR3HardNtChildWaitFor[2]: Quitting: ExitCode=0x1 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 2077 ms, the end);
be0.186c: supR3HardNtChildWaitFor[1]: Quitting: ExitCode=0x1 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 3077 ms, the end);

So, I found that one solution was to go to the program files folder then to oracle and then to virtual box then to drivers and then to vboxdrv and right click the .inf file and click install and that did not resolve the issue. Current error is


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

[Martin]

VirtualBox 5.0.40 from last April is way too old for a current Windows 10 host. Please update to the current VirtualBox version 5.2.4 from https://www.virtualbox.org/wiki/Downloads and try again.

[sosul]

I had the same problem with VirtualBox 5.1.x but updating to 5.2.6 resolved the problem. Thank you.

[Ferdinando]

Greetings

I was able to correct the error that appears in MachineWrap when uploading a virtual machine by making some changes in Windows Defender Firewall. This was done on a PC where the operating system is Windows 10.

What they have to do is run the windows defender firewall program, then click on a link that says "allow an app or feature through Windows Defender Firewall".
Then press the button called "Change Settings"
Then locate one called "Virtual Machine Monitoring" in the list of applications.
Proceed to mark or check it, in the Domain, Private, Public boxes.

Reboot your PC and post the results.

[scottgus1]

Ferdinando, thanks for relating your experience. Just to let you know, "MachineWrap" is in just about every Virtualbox error and isn't actually the error. Also, Windows Defender, in its typical Windows configuration, does not interfere with Virtualbox. If you have a problem you solved with your stated solution, you might want to relate what the problem was in a new topic, so we can know what it was.

Going to lock this topic, since it's rather old.