[Solved] Virtual Box error (0x80004005) prevents me from running all VM'S

Discussions related to using VirtualBox on Windows hosts.

[Solved] Virtual Box error (0x80004005) prevents me from running all VM'S

Postby MANTECON » 4. Sep 2019, 20:13

Hi,

I'm trying to understand the logs and troubleshoot myself but I've been unsuccessful so far. Hoping you guys can help me understand or fix this issue.
  • Bios Settings = Virtualization is ON
  • Hyper-V = Off
  • Windows Sandbox is OFF
  • Windows Subsystem for Linux is OFF
  • Windows antivirus is OFF
  • Windows > Security > Device Security > Core isolation is OFF
Attached file includes coreinfo.txt + VirtualBox Logs.

Thanks in advance,
Attachments
Coreinfo_VirtualBox_Logs.zip
All my logs are belong to us
(35.57 KiB) Downloaded 12 times
Last edited by MANTECON on 4. Sep 2019, 20:39, edited 1 time in total.
MANTECON
 
Posts: 3
Joined: 4. Sep 2019, 20:03

Re: Virtual Box error (0x80004005) prevents me from running all VM'S

Postby scottgus1 » 4. Sep 2019, 20:17

Good on you for trying to find the trouble yourself! Looks like you're on the right track.

The two guest run logs have this:
00:00:01.651718 HM: HMR3Init: Attempting fall back to NEM: VT-x is not available
00:00:01.698102 NEM: WHvCapabilityCodeHypervisorPresent is TRUE, so this might work...

This indicates something related to Hyper-V is still running. See I have a 64bit host, but can't install 64bit guests Carefully go through each command in the 2nd & 3rd posts. Based on my perusal of successful fixes for this problem, the silver bullet appears to be the "bcdedit" command & complete power-down in post 2 point 1.
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.
scottgus1
Volunteer
 
Posts: 4691
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Win7

Re: Virtual Box error (0x80004005) prevents me from running all VM'S

Postby MANTECON » 4. Sep 2019, 20:30

Hi @scottgus1, thank you for your reply. I did follow this guide verbatim with no results. I'm going to re-check the bios settings to check if I missed something.
MANTECON
 
Posts: 3
Joined: 4. Sep 2019, 20:03

Re: Virtual Box error (0x80004005) prevents me from running all VM'S

Postby MANTECON » 4. Sep 2019, 20:39

FOUND IT!!!
in my BIOS
Execute Disable Bit was ENABLED.

Now Execute Disable Bit is DISABLED and I'm able to run all my VM'S!

TL;DR = Solution* = disable Execute Disable Bit

* = this was the final thing I had to do in order to get it to work. Please follow the guide suggested on this post because I did.

Thank you all!
MANTECON
 
Posts: 3
Joined: 4. Sep 2019, 20:03

Re: [Solved] Virtual Box error (0x80004005) prevents me from running all VM'S

Postby socratis » 5. Sep 2019, 10:27

MANTECON wrote:Execute Disable Bit was ENABLED.
Correctamundo! :)

The "Execute Disable Bit" (or NX bit), must be disabled in order for the host to have NX-enabled, which is a requirement for some (almost all these days) VMs. See viewtopic.php?f=6&t=88942#p426401 and note that the last line in your VBox.log, right before the crash is:
00:00:01.464912 CPUM: SetGuestCpuIdFeature: Enabled NX
00:00:01.465534 VMSetError: F:\tinderbox\win-6.0\src\VBox\VMM\VMMR3\NEMR3Native-win.cpp(1463) int __cdecl nemR3NativeInitAfterCPUM(struct VM *); rc=VERR_NEM_VM_CREATE_FAILED

BTW, the "coreinfo.txt" wouldn't have helped. It shows you what the CPU is capable of, not if it's actually available to use, huge difference...

Thank you for the feedback and the solution, hope someone finds it useful in the future. And thank you for marking the topic as [Solved]... ;)
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
socratis
Site Moderator
 
Posts: 26871
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

Re: [Solved] Virtual Box error (0x80004005) prevents me from running all VM'S

Postby fth0 » 6. Sep 2019, 02:08

socratis wrote:(1) The "Execute Disable Bit" (or NX bit), must be disabled in order for the host to have NX-enabled [...]
(2) [...] the host to have NX-enabled, which is a requirement for some (almost all these days) VMs.
(3) See viewtopic.php?f=6&t=88942#p426401

While (2) and (3) are correct, IMHO I have to object to (1):

The page table entry bit called NX (No-eXecute) or XD (eXecute Disabled) has to be enabled in the BIOS. The corresponding BIOS setting may have a (double) negative designation/description that can be misunderstood, though, so one has to be careful with it. If the BIOS allows the CPU/OS to use the NX/XD bit (and Windows 10 requires using it), then everything is fine.

Regarding the VirtualBox default of the PAE/NX setting: For Windows 10 64-bit the default is off (doesn't matter), because the NX bit (bit 63 of page table entries) is available anyway, whereas for Windows 10 32-bit the default is on (and necessary), because the page table entries would have only 32 bits when not using PAE and wouldn't have the NX bit available then.

scottgus1 wrote:00:00:01.651718 HM: HMR3Init: Attempting fall back to NEM: VT-x is not available
00:00:01.698102 NEM: WHvCapabilityCodeHypervisorPresent is TRUE, so this might work...

I don't know how the NX/XD BIOS setting interacts with the fallback to NEM case of the OP, though. The OP's alleged solution seems to contradict my statements above, but may be attributed to a misunderstanding on either side.
fth0
Volunteer
 
Posts: 248
Joined: 14. Feb 2019, 03:06
Location: Germany
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Linux, Windows 10, macOS, ...


Return to VirtualBox on Windows Hosts

Who is online

Users browsing this forum: No registered users and 76 guests