Error while running vagrant up E_FAIL (0x80004005)

Discussions related to using VirtualBox on Windows hosts.

Error while running vagrant up E_FAIL (0x80004005)

Postby Tarik Manktala » 6. Dec 2018, 09:13

Hi All,

I am getting below error while running vagrant up on windows 10. I am using virtual box version 5.1.22. I can't switch to higher version as we are using client box which supports 5.1.22 version only.
Any kind of help will be much appreciated. Thanks in advance.
VBoxManage.exe: error: The virtual machine 'canon-desktop-ATG11.2' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\tmanktal\VirtualBox VMs\canon-desktop-ATG11.2\Logs\VBoxHardening.log'
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component MachineWrap, interface IMachine

PFB vboxManager logs:
894.4978: supR3HardenedScreenImage/NtCreateSection: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\winmm.dll [lacks WinVerifyTrust]
894.4978: supR3HardenedScreenImage/NtCreateSection: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\glu32.dll [lacks WinVerifyTrust]
894.4978: supR3HardenedScreenImage/NtCreateSection: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\mpr.dll [lacks WinVerifyTrust]
894.4978: supR3HardenedScreenImage/NtCreateSection: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\winspool.drv [lacks WinVerifyTrust]
894.4978: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #1 'advapi32.dll'.
894.4978: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #2 'gdi32.dll'.
894.4978: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #4 'user32.dll'.
894.4978: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume3\Windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_5.82.16299.214_none_8877407e4abd19b9\comctl32.dll)
894.4978: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume3\Windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_5.82.16299.214_none_8877407e4abd19b9\comctl32.dll
894.4978: supR3HardenedScreenImage/NtCreateSection: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\winmmbase.dll [lacks WinVerifyTrust]
894.4978: supR3HardenedScreenImage/NtCreateSection: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\IPHLPAPI.DLL [lacks WinVerifyTrust]
894.4978: supR3HardenedScreenImage/NtCreateSection: cache hit (Unknown Status -626 (0xfffffd8e)) on \Device\HarddiskVolume3\Windows\System32\bcrypt.dll [lacks WinVerifyTrust]
894.4978: Error (rc=0):
894.4978: supR3HardenedScreenImage/NtCreateSection: cached rc=Unknown Status -626 (0xfffffd8e) fImage=1 fProtect=0x10 fAccess=0xf cHits=5 \Device\HarddiskVolume3\Windows\System32\bcrypt.dll
894.4978: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0xc0000190 'C:\Program Files\Oracle\VirtualBox\VirtualBox.dll'
29fc.302c: supR3HardNtChildWaitFor[2]: Quitting: ExitCode=0x1 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 680 ms, the end);
4508.32d4: supR3HardNtChildWaitFor[1]: Quitting: ExitCode=0x1 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 2017 ms, the end);

Regards,
Tarik Manktala
Last edited by socratis on 6. Dec 2018, 10:29, edited 1 time in total.
Reason: Enclosed the information in [quote] tag for better readability
Tarik Manktala
 
Posts: 1
Joined: 5. Dec 2018, 14:35

Re: Error while running vagrant up E_FAIL (0x80004005)

Postby socratis » 6. Dec 2018, 10:49

Tarik Manktala wrote:I am getting below error while running vagrant up
Vagrant is a program that relies on VirtualBox, but modifies its configuration files in unknown ways to us, and with unknown consequences. 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 (after a complete uninstallation of Vagrant), then we can continue this discussion.

Tarik Manktala wrote:I can't switch to higher version as we are using client box which supports 5.1.22 version only.
I'm sorry, but this sentence doesn't make too much sense. Even if you were using 6.0.0b3, that wouldn't make a difference between what you're using and what your client's box is using. If you're using the latest for your OS, you should better use the latest for VirtualBox.

Tarik Manktala wrote:PFB vboxManager logs
No, that's a partial log, and partial logs are not useful. If you want to continue this discussion, you should upgrade to the latest VirtualBox (it might contain hardening fixes) and provide a complete, ZIPPED VBoxHardening.log.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
socratis
Site Moderator
 
Posts: 23883
Joined: 22. Oct 2010, 11:03
Location: Greece
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5


Return to VirtualBox on Windows Hosts

Who is online

Users browsing this forum: No registered users and 23 guests