E_FAIL (0x80004005) MachineWrap, Please help

[NoHotLiquids]

hi all

TL;DR
- one morning, VM stopped running, and can no longer create new VM's,

Computer specs:
--CPU: i7-6700
--RAM: 32GB
--HDD: 1TB
--Graphics: GeForceGTX 1080
- the machine is natively running Windows 10(64-bit),
- have been using virtualBox to run Ubuntu-17.04(64-bit)

what has been tried
- backdating to old version of the VirtualBox
- creating new VMs
- opening backup VM
- disabling firewalls and antivirus software's (as much as possible)

Error Message:
Failed to open a session for the virtual machine Ubuntu-17.04.

The virtual machine 'Ubuntu-17.04' has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005). More details may be available in 'D:\LIAM\Ubuntu-17.04\Logs\VBoxHardening.log'.

Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {85cd948e-a71f-4289-281e-0ca7ad48cd89}

thanks, and please help

[mpack]

Please read: FAQ: Diagnosing VirtualBox Hardening Issues.

[gazroobari]

Hi,

I have what I think is exactly the same issue as you. Happy to share expereinces if it will help both of us. I'm wondering if mine started since I upgraded my Windows 10 24 hours ago ... ?

My VB version is 5.1.22 r115126 (Qt5.6.2)
My VM is Ubuntu 12.04.5 and had been working fine.

Error dialogue reads:

The virtual machine 'Ubuntu 12.04.5 VM' has terminated unexpectedly during startup with exit code 1 (0x1).
More details may be available in 'C:\Users\...my-name...\VirtualBox VMs\Ubuntu 12.04.5 VM\Logs\VBoxHardening.log'.

Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}

Last few lines of my hardening log:

Code: Select all

367c.2b88: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #1 'advapi32.dll'.
367c.2b88: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #2 'gdi32.dll'.
367c.2b88: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #4 'user32.dll'.
367c.2b88: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume3\Windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_5.82.16299.19_none_e48015d00334ec58\comctl32.dll)
367c.2b88: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume3\Windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_5.82.16299.19_none_e48015d00334ec58\comctl32.dll
367c.2b88: supR3HardenedScreenImage/NtCreateSection: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\winmmbase.dll [lacks WinVerifyTrust]
367c.2b88: supR3HardenedScreenImage/NtCreateSection: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\IPHLPAPI.DLL [lacks WinVerifyTrust]
367c.2b88: supR3HardenedScreenImage/NtCreateSection: cache hit (Unknown Status -626 (0xfffffd8e)) on \Device\HarddiskVolume3\Windows\System32\bcrypt.dll [lacks WinVerifyTrust]
367c.2b88: Error (rc=0):
367c.2b88: supR3HardenedScreenImage/NtCreateSection: cached rc=Unknown Status -626 (0xfffffd8e) fImage=1 fProtect=0x10 fAccess=0xf cHits=4 \Device\HarddiskVolume3\Windows\System32\bcrypt.dll
367c.2b88: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0xc0000190 'C:\Program Files\Oracle\VirtualBox\VirtualBox.dll'
e24.f04: supR3HardNtChildWaitFor[2]: Quitting: ExitCode=0x1 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 858 ms, the end);
3620.1afc: supR3HardNtChildWaitFor[1]: Quitting: ExitCode=0x1 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 1321 ms, the end);

[gazroobari]

@NoHotLiquids

Fixed.

My problem was slightly different than yours in that you said you couldn't create new VMs whereas I was simply interested in getting a previous VM to boot up again, one that I hadn't used for 3 months.

Anyhow, I tried:

• sfc /scannow --- Didn't show up any issues
  In-place repair of VBox 5.1.22 with the same version installer + Windows reboot, all done with Administrator UAC --- Didn't work
  Full uninstall and reinstall of VBox 5.1.22 + Windows reboot, all done with Administrator UAC --- Didn't work
  Full uninstall of 5.1.22 followed by install of VBox 5.1.30 + Windows reboot, all done with Administrator UAC --- WORKED

Hope this helps ?

Gary

[mpack]

I'm sorry to tell you that your solution doesn't sound long term to me. If you didn't identify the source of the conflict then the conflict is still there.

VirtualBox is not in conflict with itself, so I don't see how replacing VirtualBox with an older version is likely to provide a cure.

[NoHotLiquids]

hi all,

glad you got yours fixed gazoobari, right time for an update.

Update

ok, after going through the "FAQ: Diagnosing VirtualBox Hardening Issues" a few times, and only finding conflicts with modified windows backgrounds that the ICT here decide to replace.
TL;DR It turns out the ICT installed 'Cylance' overnight, however the program was hidden to normal users. had to wait for virtualBox to be added to the whitelist now all is working.

thanks for help.

[mpack]

Cylance is a well known serial offender.

[Hanerhan]

Just had the same thing happen after Microsoft applied some of its updates. Ended up downloading the latest version of Virtualbox and installing it as Administrator. Fixed all my images.

[socratis]

If you want to use the latest version for your host/guests, you should also consider doing the same for VirtualBox. Otherwise failures *will* happen.

[Robert-Nick Revnic]

On Windows 10, I installed everything as ADMINISTRATOR and only the following configuration worked for me:

Vagrant 1.9.2 and Oracle VM VirtualBox 5.1.30

For older versions of VirtualBox, the virtual machine has terminated unexpectedly.
For newer versions of VirtualBox, the host-only adapter cannot be created.

When you upgrade or downgrade, make sure that you permanently delete (Shift + Delete) the following folders from C:\Users\your-user : .vagrant, .VirtualBox and Virtual VM Machines.
When using vagrant up, these folders will be created again.

After each program install and uninstall, make sure to restart your computer. Old files from VirtualMachine and Vagrant are persistent until the OS boots up again.

[socratis]

@Robert-Nick Revnic,
Vagrant is a program that relies on VirtualBox but modifies its configuration files in unknown ways to us. It is not supported on these VirtualBox user forums, they have their own Vagrant support channels. If you are having this problem with a standalone version of VirtualBox, then we can continue this discussion.

And you definitely should NOT delete your VirtualMachines. Unless you're a masochist...

[LorentzF]

Hi,

I found that it's and Window 10 update which is the major factor that's causing this error, how I found this was by restoring to a previous build of window 10 and then running the VM which it then worked. I haven't been able to find out what it is about the updated build itself that's causing the error but by using the windows 10 settings "Go back to previous build" option should at least help you get back to where you were.