Virtualbox код ошибки fail 0x80004005 consolewrap

Hi,

I am new here in the forum. I was wondering if anybody can help me with my Virtualbox Machine issues.

My VB was working fine with different OS installed inside previously about 2 to 3 months ago. Just now I tried to explore again the different OS on my VB.
I could not open any of them and its really disappointing.

I already upgraded to 5.2.22 just awhile ago plus the 5.2.22 extension pack. Still the issue persisted.

All are prompting Failed to open a session for the virtualbox machine. Below are the VB errors per machine:

Windows XP

Failed to open a session for the virtual machine Windows XP.

Raw-mode is unavailable courtesy of Hyper-V. (VERR_SUPDRV_NO_RAW_MODE_HYPER_V_ROOT).

Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

Windows10 (64bit)

Failed to open a session for the virtual machine Windows10.

VT-x is not available (VERR_VMX_NO_VMX).

Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

Debian8

Failed to open a session for the virtual machine Debian8.

Raw-mode is unavailable courtesy of Hyper-V. (VERR_SUPDRV_NO_RAW_MODE_HYPER_V_ROOT).

Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

Ubuntu18.04 (64bit)

Failed to open a session for the virtual machine Ubuntu18.04.

VT-x is not available (VERR_VMX_NO_VMX).

Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

I would be glad to see generous feedback and expert help on this forum.

Jiren wrote:If only I found the same issue on other threads, i don’t have to ask..

So, you’re telling me that you searched for the following errors, and you couldn’t find a thread (or 1000) or an answer?

Jiren wrote:

• Raw-mode is unavailable courtesy of Hyper-V. (VERR_SUPDRV_NO_RAW_MODE_HYPER_V_ROOT).
• VT-x is not available (VERR_VMX_NO_VMX).

You might want to switch search engines…

I was thinking more of a forums restricted search, something like:

• «VERR_SUPDRV_NO_RAW_MODE_HYPER_V_ROOT site:forums.virtualbox.org» or
• «VERR_VMX_NO_VMX site:forums.virtualbox.org«

But, hey, whatever works.
Marking as [Resolved].

socratis wrote:
But, hey, whatever works.
Marking as [Resolved].

Quite shameful solution, it didn’t work on my machine error..

I need to find other options. Still not resolve for now. I hope it will soon enough.

Jiren wrote:Quite shameful solution, it didn’t work on my machine error.

In defence of Socratis (not that he needs me to fight his battles), when you say…

Jiren wrote:I got the solution from 2 different helpful threads

…it is a reasonable interpretation that you have found a solution to your problem and have resolved it.

You haven’t explicitly stated what you host is. If it is Windows 10 then one of the updates may have enabled Hyper-V specifically or added/enabled a new feature which uses it and without informing you. That will stop VirtualBox dead in its tracks. Likewise, if you have installed a third-party anti-virus tool that may also do the same.

-Andy.

Sorry about that. I didn’t pertain to Socrates. It was the solution I found on Stack overflow. He only recommended to change search engine. I was even thankful.
I was just excited to try and check if the solution works. It was a failure for the time being.

Well anyways, it might be an update on Windows 10. I got Windows Defender on my LT.

I will try to recheck if tweaked something on the the latter. Thanks for the advice Andy.

I want to necro this, as this is the first google result for my specific problem, and it might be easily searchable for others too.

With the error pertaining to WHvSetupPartition on windows 10 may update and beyond one easy solution i found after searching for about 30 minutes. (no vmware or virtualbox would start until i did this)

Open up a command prompt, run as administrator and

bcdedit /set hypervisorlaunchtype off

Enter, reboot.
This might solve the original posters problem as well.

Arturojp77 wrote:Kind regards, I took the trouble to register just to thank this last post, for those of us who speak Spanish, the answer to our problem was not so easy to locate, it happened to me as the friend from the beginning, I read 1000 answers and none solved the problem except this, thanks really. I think I’ll even make a short video giving the solution in Spanish.
A simply line ///// bcdedit /set hypervisorlaunchtype off /// solve all

aun haciendo todo eso no me funciona alguien me ayuda
even doing all that does not work for me someone help me

asked Dec 9, 2017 at 19:53

For anyone getting this more recently where the stderr does not mention VT-x, but instead is something like this:

Stderr: VBoxManage.exe: error: Call to NEMR0InitVMPart2 failed: VERR_NEM_INIT_FAILED (VERR_NEM_VM_CREATE_FAILED)

I finally found that it was a virtualbox update that broke it for me; trying to fix NEM in Windows 11 I guess, but breaking it in Windows 10? See discussion here on virtualbox’s forum.

Basically if you have W10 and upgraded VirtualBox to 6.1.28, you’ll want to downgrade to 6.1.26.

answered Oct 23, 2021 at 16:01

Just go to network setting in VMware and uncheck Enable Network Adapter in the adapter 3 setting.

answered Jun 7, 2020 at 9:45

I solved it without downdrading VirtualBox.
Instead, I used the advice here. In short, here it is:

1. Open the «Turn Windows features on or off» settings (type optionalfeatures in the start menu)

2. Untick all the followings:
   Application Guard
   Credential Guard
   Device Guard
   * Guard
   Containers
   Hyper-V
   Virtual Machine Platform
   Windows Hypervisor Platform
   Windows Sandbox
   Windows Subsystem for Linux (WSL)

3. Restart twice.

answered Mar 22, 2022 at 12:47

answered Apr 7, 2022 at 8:31

answered May 31, 2022 at 14:39