bug after windows 10 update... I think

[viper610]

Hi there,

yesterday windows 10 did some updates and now when I try to run a windows 10VM I have been using, or an ubuntu VM I get the following error

Failed to open a session for the virtual machine Windows 10 CONEST.

Failed to load API DLL: WinHvPlatform.dll: VERR_MODULE_NOT_FOUND; vid.dll: VERR_MODULE_NOT_FOUND (VERR_NEM_INIT_FAILED).

VT-x is not available (VERR_VMX_NO_VMX).

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

Any suggestions? I do not believe anything else has changed. I running virtual box 6.0 so downloaded the install and ran the repair function and the problem remained

Thanks Ray

[Socratis]

1. It's usually better and faster, if issues get first addressed in the ​VirtualBox forums, a lot more eyes there. More than 95% of the issues are resolved over there, which keeps the developers focusing on the bug fixes and enhancements, and there is no need for another ticket to keep track of. For example, yours is most probably not a bug and someone from the developers has to deal with it and close it as "Invalid".

This is caused by some tool activating and using Hyper-V on your host. But for us to figure out that, see the next part.

2. You were supposed to follow these steps when you filed the bug, and provide a VBox.log:

   Attach a (full) log file ("Machine" menu/"Show Log" in the main VirtualBox Manager window) straight away to save time for you and for us. The log file contains a lot of useful information about both the host and the guest systems as well as information about what happened during a particular machine run. Please do not cut and paste it.

So, if you can, please open a new thread in the ​VirtualBox on Windows Hosts section of the forums. Please be sure to mention that you came from the bug tracker and include the ticket number.

[Socratis]

Related discussion in the forums: ​https://forums.virtualbox.org/viewtopic.php?f=6&t=91207

[Socratis]

According to the OP (​https://forums.virtualbox.org/viewtopic.php?f=6&t=91207#p438419):

...so did a windows reset and now it works.

Guess the ticket could be closed as [WorksForMe]...

[David Castell]

I also have this problem.

Mine occurred on Jan 18th 2019 after I shut down my VM, rebooted my machine for the first time since Jan 5th and then tried to restart my VM. Updates are managed by my organization. When I look in Check for Updates > View Update History it merely shows an unrelated driver update that predates Windows 10 being installed on my machine. Normally when there is an update there is a visual notification, so I don't believe that there was a Windows 10 update. This, I suspect it was just the reboot that was the immediate trigger for the problem.

As mentioned in an viper610's post on ​https://forums.virtualbox.org/viewtopic.php?f=6&t=91207, I looked at the Windows Hypervisor Platform setting in Windows Features. I also found it not checked. I checked it and it prompted a reboot. After rebooting I started VirtualBox and my VM. This time no Failed to load API DLL error. But as my Red Hat 7 VM started up it panicked. I shut down the VM and my Windows 10 reported a serious error and rebooted.

I tried the VM again and once more I got the Kernel panic. This time the host machine was fairly locked up as fans whirred at high speed, but Ctrl+Alt+Del did bring up the task manager allowing me to kill VirtualBox. After that my host Windows 10 recovered.

I even tried reinstalling my VM, but the same Kernel panic whilst trying to install.

[Socratis]

Replying to David Castell:

I also have this problem.

No. You don't. As I told you on the thread in the forums, don't piggyback on another user's thread/ticket, especially when the Original Poster (OP) has declared the problem to be solved!

Same characteristics doesn't mean same problem. Please let's not taint this ticket anymore, let's continue the discussion in your brand new, separate, just your own thread which I split from the original in the forums: ​https://forums.virtualbox.org/viewtopic.php?f=6&t=91423

[Socratis]

Closing as [WorksForMe], see comment:3.