Virtualization not working with 18312.1007

I've updated to windows insider build 18312.1007, and Virtual Box is no longer works. When I boot a VM they give me an error code (down below). It was working fine before, and I've already tried everything with BIOS VT-x, Disable Hyper-V, etc... (The usual forum things). Right now I'm very desperate since I have a computer science project that's due in 6 weeks and I need VM.

(VERR_NEM_MISSING_KERNEL_API).

VT-x is not available (VERR_VMX_NO_VMX).

Result Code:

E_FAIL (0x80004005)

Component:

ConsoleWrap

Interface:

IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

I just finished some experimenting with my VirtualBox and VMs and Hyper-V.  

First, VT is enabled in BIOS throughout.

I enabled Hyper-V in Windows Features, which gave me the same error you showed in your original post:

I removed the Hyper-V component through Control Panel - Windows Features.  Still received the error. 

I then Disabled HV Host Service in Services.msc, because it was still running after the reboot.  Received a new error- a vboxsvc wasn't loaded.  EDIT:  It wasn't vboxsvc it was vboxdrv error, wasn't loaded.  Hence, doing a Repair Install reinstalled the vboxdrv.

I then ran (not in compatibility mode) the installer for Oracle VirtualBox 5.2.26 and did a Repair.  Did a reboot as the installer requested.  

My VMs run as normal again.

The following is what additional Windows Features I have enabled that don't interfere with VBox.  

I hope this information can help you get yours working again.

2 people were helped by this reply

·

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Hello, try to perform these steps:

1) Disable the sandox and hyper-v. 2) Restart the pc 3) Enter the bios and disable the virtualization option (VMX) 4) Save the changes 5) Once finished to start the PC, restart again and enable the virtualization option (VMX) in the bios. Sorry for my English and I hope these steps help you.

4 people were helped by this reply

·

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Hi thank you for the advice I've already tried those steps a couple of time. I've since found a compromised "solution" to my problem. Since I am a photographer and an IT technician i needed VM access and since all of my files were backed up on a 10tb hhd I decided to just reinstall windows to creator update. This after t fixed my problems and all of my VMs went back up and running after transferring the files from my hhd to my m.2 drive.

To further prove my theory that the insider builds somehow disabled VT-x support I've gone ahead and did an experiment. I loaded up multiple insiders builds on 4 different computers and the ones that had the windows sandbox feature all had the same error message in virtural box and vm ware.

Anyways, Microsoft if your reading this (prob not). Please fix this and also stop adding so much useless bloat on windows iso images. I don't need candy crush saga on a seven thousand dollar workstation. 

Also, please work on optimizing your services like one drive and the Microsoft store since they use up 3 percent of my CPU when idle. (and yes this matters alot when you are rendering a video and one drive is taking up your precious CPU power

3 people were helped by this reply

·

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

 
 

Question Info


Last updated June 19, 2020 Views 6,454 Applies to: