E_FAIL (0x80004005)

[barney]

Hi all,
My error is slightly different to those listed on this forum:

The VM session was aborted.

Result Code: E_FAIL (0x80004005)
Component: SessionMachine
Interface: ISession {12f4dcdb-12b2-4ec1-b7cd-ddd9f6c5bf4d}

I have installed VirtualBox Version 4.3.30 release 101610
On Windows 10 Professional 64-bit
The vbox installation went OK without any errors I configure a new virtual machine in the same way as i have done in the recent past, but now when I get prompted to select the startup disk, I want to chose something other than my optical drive. (ie I want to chose a downloaded .iso file) I would normally click on the folder icon to browse to the location of the .iso.
Thats when I get the message above

I did have vbox up and running prior to upgrading to Win10, however, i tried installing a vbox update and totally f'd up resulting in having to uninstall and totally 'flatten' the registry of any vbox entries. Also deleting any vbox folders on my host machine so that all I had left was my downloaded iso files.

I hope somebody has seen this behaviour before and can highlight something stupidly simple that I have missed.
Setting up the VM prior to installing the guest OS:
General:
Ive left everything as default
System:
Ive given the VM 2048 GB Ram to play with
Ive changed the Boot Order to Hard disk first / CD-DVD drive second and have unticked floppy
Display:
default settings
Storage:
Default settings -- 8GB HDD SPace
Audio:
Disabled
Network:
NAT - enabled
Serial Ports:
Default
USB:
Default
Shared folders:
Default -- not configured

Hoping someone can help.

Regards,
Barney

[barney]

Have just installed
5.0.4
R102546
And have tried setting up a Linux Mint VM from scratch and get the following error,
This time I dont get as far in the guest OS setup.
I get this error when I click on the Start arrow in VBox...

Failed to open a session for the virtual machine Linux Mint 17.1 Mate.

The virtual machine 'Linux Mint 17.1 Mate' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\username\VirtualBox VMs\Linux Mint 17.1 Mate\Logs\VBoxStartup.log'.

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

Ive tried attaching the vbstartup.log to this post but the file is too big -- 220KB

but found these 3 lines in that log:
Line 1383: 1458.1f54: Error -1912 in supR3HardenedMainInitRuntime! (enmWhat=4)
Line 2078: 1458.1f54: supR3HardenedMonitor_LdrLoadDll: error opening 'C:\WINDOWS\system32\wintab32.dll': 0 (NtPath=\??\C:\WINDOWS\system32\wintab32.dll; Input=C:\WINDOWS\system32\wintab32.dll; rcNtGetDll=0x0
Line 2090: 1458.1f54: supR3HardenedMonitor_LdrLoadDll: error opening 'C:\WINDOWS\system32\wintab32.dll': 0 (NtPath=\??\C:\WINDOWS\system32\wintab32.dll; Input=C:\WINDOWS\system32\wintab32.dll; rcNtGetDll=0x0

regards,
Barney

[barney]

Ive just checked in the System32 folder and there is no .dll file called wintab32.dll

Should this .dll be installed during VBox installation?
If so, any ideas why it hasnt been installed?

regards,
Barney

[JoNoren]

Hi, I updated VB last night and I got exactly the same error, old VM does not start and I cannot build new one (it stucks right after starting it).

my host is a win7 machine.
my guest, one is another win7 and the one I tried to build was linux ubuntu.

also I gave both vm enough ram(2g) and video memory to be able to run smoothly.

Thanks.

edit: I got also andyroid, this one is working fine.

[Keith'n'TX]

I"m getting a similar error. Upgraded to Win10 from Win7, upgraded to 5.0.4 Virtualbox. Both an existing (Ubuntu) and attempted Debian ISO install fail with the same popup:
LoadLibrary failed with error 1114: a dynamic link library (DLL) initialization routine failed.

Followed by this error message box:

The VM session was aborted.

Result Code:
E_FAIL (0x80004005)
Component:
SessionMachine
Interface:
ISession {7844aa05-b02e-4cdd-a04f-ade4a762e6b7}

P.S.
Last several lines from startup log:
2254.21bc: \Device\HarddiskVolume2\Windows\System32\ig4icd64.dll: Owner is administrators group.
2254.21bc: supR3HardNtViCallWinVerifyTrustCatFile: hFile=0000000000000ebc pwszName=\Device\HarddiskVolume2\Windows\System32\ig4icd64.dll
2254.21bc: supR3HardNtViCallWinVerifyTrustCatFile: Cached context 00000000016c66f0
2254.21bc: supR3HardNtViCallWinVerifyTrustCatFile: hCatAdmin=00000000016c66f0
2254.21bc: supR3HardNtViCallWinVerifyTrustCatFile: cbHash=20 wszDigest=8C41BEA27D058E4C2BFA8952D124217A9C05BA0C
2254.21bc: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007fff02ea0000 'C:\WINDOWS\system32\rsaenh.dll'
2254.21bc: supR3HardNtViCallWinVerifyTrustCatFile: WinVerifyTrust => 0x47f; cat='C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem35.cat'; file='\Device\HarddiskVolume2\Windows\System32\ig4icd64.dll'
2254.21bc: supR3HardNtViCallWinVerifyTrustCatFile -> 0 (org 22900)
2254.21bc: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #0 'opengl32.dll'.
2254.21bc: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #2 'user32.dll'.
2254.21bc: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #3 'gdi32.dll'.
2254.21bc: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #4 'advapi32.dll'.
2254.21bc: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume2\Windows\System32\ig4icd64.dll) WinVerifyTrust
2254.21bc: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume2\Windows\System32\ig4icd64.dll
2254.21bc: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'advapi32.dll'...
2254.21bc: supR3HardenedWinVerifyCacheProcessImportTodos: 'advapi32.dll' -> '\Device\HarddiskVolume2\Windows\System32\advapi32.dll' [rcNtRedir=0xc0150008]
2254.21bc: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'gdi32.dll'...
2254.21bc: supR3HardenedWinVerifyCacheProcessImportTodos: 'gdi32.dll' -> '\Device\HarddiskVolume2\Windows\System32\gdi32.dll' [rcNtRedir=0xc0150008]
2254.21bc: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'user32.dll'...
2254.21bc: supR3HardenedWinVerifyCacheProcessImportTodos: 'user32.dll' -> '\Device\HarddiskVolume2\Windows\System32\user32.dll' [rcNtRedir=0xc0150008]
2254.21bc: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'opengl32.dll'...
2254.21bc: supR3HardenedWinVerifyCacheProcessImportTodos: 'opengl32.dll' -> '\Device\HarddiskVolume2\Windows\System32\opengl32.dll' [rcNtRedir=0xc0150008]
2254.21bc: supR3HardenedScreenImage/Imports: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume2\Windows\System32\opengl32.dll
2254.21bc: supR3HardenedMonitor_LdrLoadDll: pName=C:\WINDOWS\system32\ig4icd64.dll (Input=ig4icd64.dll, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000001:<flags> [calling]
2254.21bc: supR3HardenedScreenImage/NtCreateSection: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume2\Windows\System32\ig4icd64.dll
2254.21bc: supR3HardenedDllNotificationCallback: load 0000000180000000 LB 0x011f2000 C:\WINDOWS\system32\ig4icd64.dll [fFlags=0x0]
2254.21bc: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume2\Windows\System32\ig4icd64.dll
2254.21bc: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007fff062f0000 'C:\WINDOWS\system32\gdi32.dll'
2254.21bc: supR3HardenedDllNotificationCallback: Unload 0000000180000000 LB 0x011f2000 C:\WINDOWS\system32\ig4icd64.dll [flags=0x0]
2254.21bc: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0xc0000142 'C:\WINDOWS\system32\ig4icd64.dll'
2254.21bc: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007fff06610000 'C:\WINDOWS\system32\OLEAUT32.dll'
168c.22cc: supR3HardNtChildWaitFor[2]: Quitting: ExitCode=0x45a (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 262838 ms, the end);
20c4.f68: supR3HardNtChildWaitFor[1]: Quitting: ExitCode=0x45a (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 263572 ms, the end);

I'm suspecting the old Intel graphics driver, but not sure what can be done about it...

P.P.S. WORKAROUND/FIX: Needed to disable 3D graphics (which worked before) to stop the crashes.

[loukingjr]

Ive just checked in the System32 folder and there is no .dll file called wintab32.dll

Should this .dll be installed during VBox installation?

The wintab32.dll is associated with Wacom graphics tablets, perhaps others. Nothing to do with VirtualBox. It's not in my Windows 10 install. I don't have the error mentioned here but as a guess it could be being caused by an anti-viral program.

[barney]

Ive just checked in the System32 folder and there is no .dll file called wintab32.dll

Should this .dll be installed during VBox installation?

The wintab32.dll is associated with Wacom graphics tablets, perhaps others. Nothing to do with VirtualBox. It's not in my Windows 10 install. I don't have the error mentioned here but as a guess it could be being caused by an anti-viral program.

Thanks for that loukingjr

I have now tried disabling my AVG and tried setting up a VM from scratch again.
Now I get:
RTR3InitEx failed with rc=-1912 (rc=-1912)

where: supR3HardenedMainInitRuntime
what: 4
VERR_VM_DRIVER_VERSION_MISMATCH (-1912) - The installed support driver doesn't match the version of the user.

[loukingjr]

With your guest shutdown, can you attach a zipped "VBox.log" for your guest? It would be more useful to the Windows gurus to try and diagnose the problem.

[barney]

Heres my vboxlog zipped (attached)

[barney]

Hi all,
Update for you.
Keith'n'TX » mentioned 3D graphics and disabling them helped resolve the particular issue that he had.
Well I checked my VM settings and 3D graphics were disabled, but this gave me the idea to increase the Video Memory.
I have upped the setting to 36MB (random amount) and I now dont see any of the aforementioned error message,
however now when I click Start to run the initial setup of the guest OS it counts down to the beginning of the OS Setup with the Mint logo,
then ........ nothing.
See attached image.
even tried increasing the video memory to max. 128MB. No joy.

Barney

[JoNoren]

Barney on my side I was able to finally start my stuff on the last version (5.0.4). I rolled back to 4.2.xx and test it out (which worked). Then I reinstalled 5.0.4 and I my vms were able to start normally. Now the only glitch I have is while in fullscreen mode the screen is not centered.

[loukingjr]

Now the only glitch I have is while in fullscreen mode the screen is not centered.

I'm not sure how full screen can not be centered but you might consider posting a separate topic in case someone else has the same issue.

[barney]

Barney on my side I was able to finally start my stuff on the last version (5.0.4). I rolled back to 4.2.xx and test it out (which worked). Then I reinstalled 5.0.4 and I my vms were able to start normally. Now the only glitch I have is while in fullscreen mode the screen is not centered.

Thanks for the tip JoNoren. Im not with the computer with the problem at the moment. Probably not until tomorrow, but I will give this a try and let everyone know how i got on.

Regards,
Barney

[barney]

Hi all,
After the suggestion by JoNoren
Ive uninstalled 5.0.4
and installed 4.3.28 r100309
the install went OK, but when I tried running a guest i
got the following two error messages

[barney]

OK so Ive now uninstalled 4.3.28 and have now installed
4.2.10 r84104
Now VM starts without errors and goes into the initial setup screen
which counts down from 5 before the installation proper should start.
....
....
....
....
And ....nothing

Barney.