Code d'erreur : E_FAIL (0x80004005)

Discussions related to using VirtualBox on Windows hosts.

Code d'erreur : E_FAIL (0x80004005)

Postby Sebiohazard » 21. Aug 2019, 10:47

Hello everyone :)

I have this error code when launching my VMs: Code d'erreur : E_FAIL (0x80004005)

Here is a screenshot & log file: [ModEdit: replaced 3rd party link to a screenshot of the error, with the actual error text]
Échec de l'ouverture de session pour la machine virtuelle Linux Mint 19.

The configuration constructor in main failed due to a COM error. Check the release log of the VM for further details. (VERR_MAIN_CONFIG_CONSTRUCTOR_COM_ERROR).

Code: Select all   Expand viewCollapse view
00:00:02.747044 VirtualBox VM 6.0.10 r132072 win.amd64 (Jul 12 2019 09:34:54) release log
00:00:02.747061 Log opened 2019-08-21T07:58:28.214231300Z
00:00:02.747061 Build Type: release
00:00:02.747064 OS Product: Windows 10
00:00:02.747065 OS Release: 10.0.17763
00:00:02.747065 OS Service Pack:
00:00:02.786316 DMI Product Name: MS-7A67
00:00:02.789901 DMI Product Version: 1.0
00:00:02.789915 Host RAM: 7893MB (7.7GB) total, 2916MB (2.8GB) available
00:00:02.789917 Executable: C:\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
00:00:02.789918 Process ID: 7324
00:00:02.789918 Package type: WINDOWS_64BITS_GENERIC
00:00:02.790719 Installed Extension Packs:
00:00:02.790756   Oracle VM VirtualBox Extension Pack (Version: 6.0.10 r132072; VRDE Module: VBoxVRDP)
00:00:02.792698 Console: Machine state changed to 'Starting'
00:00:02.793847 Qt version: 5.6.2
00:00:02.796014 GUI: UIMediumEnumerator: Medium-enumeration finished!
00:00:02.915929 SUP: Loaded VMMR0.r0 (C:\Program Files\Oracle\VirtualBox\VMMR0.r0) at 0xXXXXXXXXXXXXXXXX - ModuleInit at XXXXXXXXXXXXXXXX and ModuleTerm at XXXXXXXXXXXXXXXX using the native ring-0 loader
00:00:02.915948 SUP: VMMR0EntryEx located at XXXXXXXXXXXXXXXX and VMMR0EntryFast at XXXXXXXXXXXXXXXX
00:00:02.915952 SUP: windbg> .reload /f C:\Program Files\Oracle\VirtualBox\VMMR0.r0=0xXXXXXXXXXXXXXXXX
00:00:02.917663 AssertLogRel F:\tinderbox\win-6.0\src\VBox\Main\src-client\ConsoleImpl2.cpp(748) int __cdecl Console::i_configConstructorInner(struct UVM *,struct VM *,class util::AutoWriteLock *): !FAILED(hrc)
00:00:02.917678 hrc=ERROR_MOD_NOT_FOUND 0x8007007E
00:00:02.918070 Constructor failed with rc=VERR_MAIN_CONFIG_CONSTRUCTOR_COM_ERROR pfnCFGMConstructor=00007ffadcd550d0
00:00:02.918450 VMSetError: F:\tinderbox\win-6.0\src\VBox\VMM\VMMR3\VM.cpp(328) int __cdecl VMR3Create(unsigned int,const struct VMM2USERMETHODS *,void (__cdecl *)(struct UVM *,void *,int,const char *,unsigned int,const char *,const char *,char *),void *,int (__cdecl *)(struct UVM *,struct VM *,void *),void *,struct VM **,struct UVM **); rc=VERR_MAIN_CONFIG_CONSTRUCTOR_COM_ERROR
00:00:02.918471 VMSetError: The configuration constructor in main failed due to a COM error. Check the release log of the VM for further details.
00:00:02.918893 ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} aText={The configuration constructor in main failed due to a COM error. Check the release log of the VM for further details. (VERR_MAIN_CONFIG_CONSTRUCTOR_COM_ERROR)}, preserve=false aResultDetail=-6400
00:00:02.919272 Console: Machine state changed to 'PoweredOff'
00:00:02.925334 Power up failed (vrc=VERR_MAIN_CONFIG_CONSTRUCTOR_COM_ERROR, rc=E_FAIL (0X80004005))
00:00:03.426458 GUI: UIMachineViewNormal::resendSizeHint: Restoring guest size-hint for screen 0 to 800x600
00:00:03.426494 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={ab4164db-c13e-4dab-842d-61ee3f0c1e87} aComponent={DisplayWrap} aText={The console is not powered up}, preserve=false aResultDetail=0
00:00:03.426729 GUI: Aborting startup due to power up progress issue detected...

Thanks for your help
Last edited by socratis on 22. Aug 2019, 07:20, edited 1 time in total.
Reason: Replaced attachment with actual text.
Posts: 5
Joined: 4. Aug 2019, 17:44
Primary OS: MS Windows 7
VBox Version: OSE other
Guest OSses: Windows 7 Ubuntu

Re: Code d'erreur : E_FAIL (0x80004005)

Postby scottgus1 » 21. Aug 2019, 18:14

The forum gurus like logs to be zipped and posted as zip files using the forum's Upload Attachment tab. Screenshots should also be cropped & resized to fit the frum's 128kB limit, and posted using Upload Attachment.


This web search:


reveals that Virtualbox may not be installed properly. Try finding the installer and re-run it by right-clicking the installer icon and choosing Run As Administrator. (Note, 'Right-click Run As Administrator' is not 'log-off-log-back-on-as-an-administrator', nor is it 'I'm-already-admin-so-I-don't-need-to-right-click'. You need to do the right-click method even if you are already an admin on Windows hosts to get Virtualbox to install correctly. It's a Windows thing...)
Human government is like that crazy uncle who hides a quarter in his fist behind his back, then asks you to guess which fist the quarter is in...
No matter which side you choose, Left or Right, both Sides are empty.
Posts: 5792
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Return to VirtualBox on Windows Hosts

Who is online

Users browsing this forum: Google [Bot], Rich Sr and 37 guests