Здравствуйте, я хочу запустить свою виртуальнуб машину на Virtualbox, но при запуске пишет «The native API dll was not found (C:\Windows\system32\WinHvPlatform.dll) (VERR_NEM_NOT_AVAILABLE)», что делать?
-
Вопрос задан
-
1078 просмотров
Пригласить эксперта
вам же русским по белому
включть в биос поддержку
вру конечно, но прога не видит WinHvPlatform.dll
включи в биос поддержку и перенакати vbox
я не знаю как там в виндоусе
проверить в биос виртуализацию
проверить в компонентах винды — отключен ли Hyper-V
перенакатить VB и попробовать предыдущую версию
Войдите, чтобы написать ответ
-
Показать ещё
Загружается…
Минуточку внимания
-
DevCap
- Posts: 5
- Joined: 28. Dec 2019, 18:23
Getting Error on Launching Virtual Box 6.1…
I am getting below error on starting Sandbox HDP 3.0 in Virtual Box 6.1 :
////////////
The native API dll was not found (C:\WINDOWS\system32\WinHvPlatform.dll) (VERR_NEM_NOT_AVAILABLE).
VT-x is not available (VERR_VMX_NO_VMX).
Result Code:
E_FAIL (0x80004005)
Component:
ConsoleWrap
Interface:
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
///////////////
I have already enabled the Virtualisation Technology in the BIOS Settings.
I also disabled the Hyper-V and Hyper-V Platform in the settings.
Here is the configuration settings of my HP system :
Processor : Intel(R) Core(TM) i5-8350U CPU @ 1.70GHz 1.90GHz
RAM : 8GB
System : 64-bit Operating System, x64 based processor.
Also, I am not able to change anything in the settings of virtualbox as OK button is disabled.
Please find attached the logs file.
Please help.
Thanks in advance.
- Attachments
-
- VBox.log
- (61.95 KiB) Downloaded 740 times
-
scottgus1
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Windows, Linux
Re: Getting Error on Launching Virtual Box 6.1…
Post
by scottgus1 »
Those errors may mean that some service in Windows 10 that uses Microsoft Hyper-V is active in your host PC OS. In most cases Hyper-V blocks Virtualbox. Often, just making sure that the Hyper-V checkbox is unchecked is not enough.
To turn Hyper-V off completely, do this:
1. Shut down all programs. You will have to reboot your host.
2. Find the Command Prompt icon, right click it and choose Run As Administrator.
3. Enter this command:
bcdedit /set hypervisorlaunchtype off
4. Enter this command:
shutdown -s -t 2
5. When the computer turns off, unplug it for 20 seconds. Then plug it in again and boot up Windows 10.
Your Virtualbox should be running now. If Virtualbox still complains of the «VERR_NEM_VM_CREATE_FAILED» error, try all the steps again. If you still have the error, post back exactly what you did and we’ll try to help some more.
For further info, see I have a 64bit host, but can’t install 64bit guests and https://www.tenforums.com/tutorials/139 … puter.html
-
DevCap
- Posts: 5
- Joined: 28. Dec 2019, 18:23
Re: Getting Error on Launching Virtual Box 6.1…
Post
by DevCap »
Hi scottgus1
Thanks for the reply, but the problem still persists. I am still getting same error.
I performed the below steps twice :
— Shut down all the programs.
— Run Command Prompt as an Administrator.
— Execute Command : bcdedit /set hypervisorlaunchtype off
— Execute Command : shutdown -s -t 2
— Boot the system after around 10 minutes.
I also disabled the Device Guard in Group Policy, but still same.
Please help here.
-
fth0
- Volunteer
- Posts: 5690
- Joined: 14. Feb 2019, 03:06
- Primary OS: Mac OS X other
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Linux, Windows 10, …
- Location: Germany
Re: Getting Error on Launching Virtual Box 6.1…
Post
by fth0 »
00:00:02.330834 Host RAM: 8039MB (7.8GB) total, 4184MB (4.0GB) available [...] 00:00:02.430406 RamSize <integer> = 0x0000000280000000 (10 737 418 240, 10 240 MB, 10.0 GB)
You are trying to provide much more RAM to the guest than you have available, which could be the real cause for the abort. Try to provide only 2 GB. If you have to provide 4 GB, reboot your host before starting the VM to free more memory.
-
DevCap
- Posts: 5
- Joined: 28. Dec 2019, 18:23
Re: Getting Error on Launching Virtual Box 6.1…
Post
by DevCap »
Hi fth0,
Thanks for the reply.
Reducing the memory solves the first error : The native API dll was not found (C:\WINDOWS\system32\WinHvPlatform.dll) (VERR_NEM_NOT_AVAILABLE).
Now, I am not getting this error. Thank you.
But I am still getting second error :
VT-x is not available (VERR_VMX_NO_VMX)
Please help in solving this error as well.
Please find attached VBox.log and VBoxHardening.log zip file.
- Attachments
-
- VBoxHardening.zip
- (27.89 KiB) Downloaded 306 times
-
- VBox.log
- (61.68 KiB) Downloaded 103 times
-
fth0
- Volunteer
- Posts: 5690
- Joined: 14. Feb 2019, 03:06
- Primary OS: Mac OS X other
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Linux, Windows 10, …
- Location: Germany
Re: Getting Error on Launching Virtual Box 6.1…
Post
by fth0 »
VBox.log file wrote:
VirtualBox VM 5.2.18 r124319 win.amd64 (Aug 14 2018 12:39:01) release log 00:00:01.620133 Oracle VM VirtualBox Extension Pack (Version: 6.1.0 r135406; VRDE Module: VBoxVRDP unusable because of 'VBoxExtPackVMRegister returned VERR_VERSION_MISMATCH, pReg=0000000000000000 ErrInfo='Helper version mismatch - expected 0x3 got 0x10002'')
Version mismatch.
VBox.log file wrote:
00:00:01.768760 VMSetError: F:\tinderbox\win-5.2\src\VBox\VMM\VMMR3\HM.cpp(752) int __cdecl HMR3Init(struct VM *); rc=VERR_VMX_NO_VMX 00:00:01.768787 VMSetError: VT-x is not available
Since there is no indication of Hyper-V interfering any more, I’d recheck the BIOS settings …
-
DevCap
- Posts: 5
- Joined: 28. Dec 2019, 18:23
Re: Getting Error on Launching Virtual Box 6.1…
Post
by DevCap »
Hi fth0,
The version mismatch is because I was trying with different version (5.2.18) of Virtualbox in the hope that it will work.
The only thing with older version (5.2.18) is that I am not getting dll error . I am only getting one error : VT-x is not available (VERR_VMX_NO_VMX).
But, I again installed new version (6.1.0) of virtual box , and again it start showing both the errors:
(C:\WINDOWS\system32\WinHvPlatform.dll) (VERR_NEM_NOT_AVAILABLE) , and
VT-x is not available (VERR_VMX_NO_VMX).
Steps taken to solve these problems :
I have enabled the Virtualisation Technology in the BIOS Settings (verified multiple times in bios settings)
I also disabled the Hyper-V and Hyper-V Platform in the settings.
Run this command : bcdedit /set hypervisorlaunchtype off
Also, disable the device guard in Policy settings.
Turned off the core Isolation.
Provide only 2GB memory as suggested.
I tried most of the solutions available continuously for 2 days, but no lead.
Please please please help me here.
Please find attached new log files for new version of virtual box.
- Attachments
-
- VBoxHardening.zip
- (30.42 KiB) Downloaded 116 times
-
- VBox.log
- (64.3 KiB) Downloaded 43 times
-
DevCap
- Posts: 5
- Joined: 28. Dec 2019, 18:23
Re: Getting Error on Launching Virtual Box 6.1…
Post
by DevCap »
It is working for me now.
Actually, the problem is my system had Windows 10 Enterprise ( 1709 Version ).
I updated it to 1809 Version.
Reboot the system , and it started working.
Thank you everyone for the help.
Вы успешно пользуетесь VirtualBox не первый день, но вот однажды запускаете установленную виртуальную системы и вдруг получаете сообщение «Не удалось открыть сессию для виртуальной машины…». Пробуете запустить другую WM и получаете то же сообщение об ошибке. Раскрыв детали, видите следующую картину: во-первых, VirtualBox ссылается на отсутствие некоего файла WinHvPlatform.dll, во-вторых, указывает на отключение в BIOS аппаратной виртуализации.
Итак, давайте разбираться.
Файл WinHvPlatform.dll
Библиотека WinHvPlatform.dll может отсутствовать на вашем компьютере, но это никак не должно влиять на работу VirtualBox, поскольку нужна она только штатному гипервизору Hyper-V. Не стоит тратить время на поиск этой библиотеки в интернете, не даст результата и переустановка компонентов Visual C++ и Microsoft .NET Framework, так как на истинный источник проблемы указывает вторая ошибка — VT-x is disabled in the BIOS for all CPU modes.
Включена ли виртуализация
Если на компьютере имел место системный сбой, а с приведенной нами ошибкой нередко приходится сталкиваться как раз после таких сбоев, в том числе прерывания завершения работы компьютера или его отправки в гибернацию нажатием Reset (в случае зависания), необходимо проверить состояние функции аппаратной гибернации.
Откройте Диспетчер задач, переключитесь на вкладку «Производительность», выберите «ЦП» и посмотрите под графиком загруженности, доступна ли виртуализация.
Также вы можете посмотреть статус виртуализации в BIOS, перейдя в раздел Advanced -> CPU Configuration -> Intel Virtualization Technology (в разных моделях BIOS название может отличаться). Отвечающая за аппаратную виртуализацию опция должна иметь значение Enabled.
Антивирусы
Если аппаратная виртуализация включена, а VirtualBox, тем не менее, утверждает обратное, причина неполадки кроется в программной части, а именно в настройках вашей антивирусной программы, которые могут быть изменены при обновлении приложения.
В частности, причиной ошибки с кодом 0x30004005 при запуске виртуальных машин в VirtualBox может стать включенная политика Защитника Windows «Средство обеспечения безопасности на основе виртуализации».
Если у вас она включена, установите для нее значение либо «Отключена», либо «Не задана» и перезагрузите компьютер.
Другой пример — популярный антивирус Avast с включенной опцией «Виртуализация с аппаратной поддержкой».
Эта функция «обеспечивает дополнительную защиту для некоторых функций виртуализации, что не позволяет вредоносным программам покидать песочницу», но она же может привести к проблемам использования аппаратной виртуализации вообще.
Отключите ее и перезагрузите компьютер.
Кстати, это уже не первый случай, когда Avast препятствовал работе сторонних гипервизоров, причем не только VirtualBox, но и VMware Workstation.
Сброс BIOS
Наконец, причиной проблемы может стать сбой BIOS — не слишком часто встречающееся явление. Если никакие другие способы устранения неполадки не дали положительного результата, попробуйте сбросить BIOS к исходным настройкам.
Since version 6.0, VirtualBox is able to use the Hyper-V API to coexist next to Hyper-V.
But, performance will be worse and it doesn’t work with all versions of Windows 10.
This solution is therefore only useful if you want to be able to use virtual machines simultaneously with Hyper-V and VirtualBox.
Note that you can also use a multi-boot to boot or not with Hyper-V (if you want) so you don’t have to uninstall and reinstall Hyper-V every time.
Note : tutorial also tested without problem with VirtualBox 6.1 and 7 on Windows 10.
Screenshots available at the end of step 2 of this tutorial.
- Prerequisites
- Use Hyper-V paravirtualization with VirtualBox 6
- Info : versions 1079 and earlier of Windows 10 are not supported
1. Prerequisites
For this to work, you must use a version of Windows 10 that is supported by VirtualBox 6.
According to our tests, only Windows 10 v1803 x64 is supported by versions 6.0 and 6.0.14 of VirtualBox (even if the virtual machines will be slower).
Indeed, for this to work, the «Hyper-V» AND «Windows Hypervisor Platform» features need to be enabled on Windows 10.
However, the «Windows Hypervisor Platform» feature is only available from Windows 10 v1803.
And from the version 1809 of Windows 10, the virtual machine will try to start and will freeze on a black screen.
Important :
- this will not work on Windows 8, because this «Windows Hypervisor Platform» feature is not present.
- make sure that the «Hyper-V Platform» box present in the «Hyper-V» feature is also checked and not greyed out.
If this box is grayed out, it’s usually because processor virtualization is not enabled in your motherboard’s BIOS.
To solve the problem, refer to our tutorial : Enable virtualization (Intel VT-x / AMD-V).
2. Use Hyper-V paravirtualization with VirtualBox 6
If Hyper-V is enabled in Windows 10 features, but the «Windows Hypervisor Platform» feature is disabled, VirtualBox will only use Hyper-V Paravirtualization.
If you attempt to start the virtual machine, VirtualBox will tell you that the «Windows Hypervisor Platform» feature must be enabled in Windows 10 and that Intel virtualization technology (VT-x) is not available.
Plain Text
WHvCapabilityCodeHypervisorPresent is FALSE! Make sure you have enabled the 'Windows Hypervisor Platform' feature.
(VERR_NEM_NOT_AVAILABLE).
VT-x is not available (VERR_VMX_NO_VMX).
Result Code : E_FAIL (0x80004005)
Composant : ConsoleWrap
Interface : IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
Once you have enabled the «Hyper-V» and «Windows Hypervisor Platform» features in Windows 10, VirtualBox will use accelerations : VT-x/AMD-V, Nested Paging, Hyper-V Paravirtualization.
This time, you can start your virtual machine without any problem.
In addition, you will see a green bird icon (with a V) at the bottom right indicating that VirtualBox is using Hyper-V paravirtualization instead of its own virtualization technology.
Once the guest OS is installed, install the guest additions as usual by going to : Devices -> Insert Guest Additions CD image.
As you can see, the guest additions have been installed correctly even though the virtual machine is virtualized via Hyper-V.
Indeed, you will still benefit VirtualBox virtual hardware and therefore VirtualBox features.
3. Info : versions 1079 and earlier of Windows 10 are not supported
As mentioned at the beginning of this tutorial, you will need Windows 10 v1803 for this to work.
Indeed, the «Windows Hypervisor Platform» is only available from version 1803 and this one allows VirtualBox to be based on the native Hyper- V to work next to it.
Info : enabling the Hyper-V feature masks the availability of Intel VT-x for other virtualization software.
But, enabling the «Windows Hypervisor Platform» feature can fix this problem. However, since this feature is not available before version 1803 of Windows 10, VirtualBox can no longer work next to Hyper-V.
If you create a virtual machine in VirtualBox, you will see that the Hyper-V Paravirtualization acceleration is displayed, because Hyper-V is installed on the host PC.
But, the «VT-x/AMD-V» acceleration is not displayed, because Hyper-V reserve it and it’s no longer accessible by VirtualBox.
As a result, the virtual machine will not boot, because the native Hyper-V API is not present in your version of Windows 10 and the Intel virtualization technology (VT-x) is not available for VirtualBox.
Plain Text
The native API dll was not found (C:\Windows\system32\WinHvPlatform.dll) (VERR_NEM_NOT_AVAILABLE). VT-x is not available (VERR_VMX_NO_VMX). Result Code : E_FAIL (0x80004005)