Ошибка vmware workstation intel vt x

This document pertains only to Intel VT-x on Intel hardware. It does not pertain to AMD-V (aka SVM) on AMD hardware. Some portions of this document may be relevant to Intel VT-x on VIA hardware.

Common Issues

VT is enabled in the firmware, but your VMware product says that VT is disabled

When a VMware product says that VT is disabled, it is referring to «Intel Virtualization Technology,» otherwise known as VT-x.  Some firmware menus offer a separate setting for «VT-d,» which is «Intel Virtualization Technology for Directed I/O.»  Note that it is not sufficient to enable «VT-d.»  You must enable «Intel Virtualization Technology.» Moreover, the only VMware product that uses VT-d is ESX(i).  For other VMware products, the VT-d setting is irrelevant.

Because the VT-x setting is typically locked at power on, it is necessary to fully power down the system after changing any VT-x options in the firmware (BIOS/EFI). A simple reboot is not sufficient! After saving your firmware changes, I recommend that you either switch off the power supply itself or pull the power cord(s) out of the wall and wait ten seconds. For laptop systems, you may have to remove the battery as well, although such extreme measures are rarely necessary.

Note that VT-x is often unavailable to normal software if you have enabled «trusted execution,» which may restrict the use of VT-x to «trusted» code. If you have enabled both VT-x and «trusted execution» in the firmware, but your VMware product still says that VT is disabled, disable «trusted execution» in the firmware and power-cycle the system again.  Your firmware menu may refer to «trusted execution» as «trusted computing.»

Sometimes, buggy firmware fails to enable VT on all of the cores of the system. To diagnose this issue, see «Obtaining Detailed Diagnostics,» below.

VT is disabled only after Windows 7 «Hybrid Sleep»

If VT is enabled after a power-cycle, but it is disabled after hybrid sleep, the likely cause is buggy firmware (BIOS/EFI). The best solution is to obtain updated firmware from your system vendor. If this is not possible, or if the latest firmware does not resolve the issue, you may have to disable hybrid sleep. If the firmware leaves VT unlocked after hybrid sleep, current hosted VMware products will automatically enable and lock VT. A workaround exists for older VMware products. See «Enabling VT-x if Unlocked,» below.

VT is disabled only after hibernate and/or sleep

If VT is enabled after a power-cycle, but it is disabled after hibernate and/or sleep, the likely cause is buggy firmware (BIOS/EFI). The best solution is to obtain updated firmware from your system vendor. If this is not possible, or if the latest firmware does not resolve the issue, you may have to disable hibernate and/or sleep. If the firmware leaves VT unlocked after hibernate and/or sleep, current hosted VMware products will automatically enable and lock VT. A workaround exists for older VMware products. See «Enabling VT-x if Unlocked,» below.

Your VMware product says that your host does not support VT

Some Intel processors are not VT-capable. (For example, the Q8200 Intel Core 2 Quad Processor is not VT-capable). You can check to see if your processor(s) are VT-capable  here.

If the Intel site says that your CPU(s) support VT, but your VMware product says that your host does not support VT, you may have encountered an Intel chip erratum (possibly AW67, AV69, AX64, AY64, AZ69 or AAA70, depending on the CPU). The effect of this erratum is that some CPU features are reported incorrectly by the CPU. The only solution to this problem is to obtain an updated BIOS from your system vendor.

If you have a multi-processor system with mixed-stepping CPUs and the Intel site says that all of your CPU(s) support VT, but your VMware product says that your host does not support VT, your CPUs may support incompatible revisions of VT-x. This is known to be an issue with the «B» and «G» steppings of Intel processors codenamed «Clovertown» and «Woodcrest.» The only solution to this problem is to obtain an updated BIOS from your system vendor.

You are trying to run a nested VM with VT-x

VMware products prior to ESXi 5.0, Workstation 8, and Fusion 4 do not virtualize the VT-x features of the physical CPU, so the virtual CPU will always report that the «host» does not support VT. In this case, the «host» refers to the virtual machine. If you are using ESXi 5.0, Workstation 8, or Fusion 4, see Running Nested VMs for information on enabling virtualized VT-x.

You have McAfee Deep Defender installed on your host

McAfee Deep Defender installs a hypervisor between the physical hardware and your host OS.  Thus, when you have McAfee Deep Defender installed, you are actually running the host OS in a VM.  McAfee Deep Defender does not virtualize the VT-x features of the physical CPU, so the virtual CPU will always report that the «host» does not support VT. In this case, the «host» refers to the virtual machine running under McAfee Deep Defender.

Your firmware has no option to enable/disable VT

If your firmware leaves VT unlocked at power-on, current hosted VMware products will automatically enable and lock VT. A workaround exists for older VMware products. See «Enabling VT-x if Unlocked,» below.  However, if your firmware locks VT off at power-on (e.g. some Sony VAIO firmware), you may be out of luck. Sony VAIO users may want to search the forums for relevant threads, but please be aware that editing your CMOS settings with third-party tools can render your computer useless.

You really are using SMX (trusted execution)

Maybe you work for the NSA, and you really are running a VMware product under SMX.  There is a different bit that reports whether or not VT-x is enabled under SMX.  Unfortunately, there is no way to tell if the host operating system is running under SMX, so we assume that it isn’t.  This means that the VMware product may be checking the wrong bit to see if VT-x is enabled.  A workaround is to set the following configuration option:

hv.assumeEnabled = TRUE

With this option set, VMware hosted products will assume that VT-x is available, regardless of the system configuration.

Obtaining Detailed Diagnostics

To verify that VT-x is enabled and locked on each core/thread of your system, download the attached ISO, burn it to a CD, and boot your host from the CD. Note that you must boot the physical machine from this CD image. It will do you no good to boot a VM from this image, since running this in a VM reports on the capabilities of the virtual CPU rather than the physical CPU.

For each core on your system (or for each thread, if your CPU(s) support hyper-threading),  the ISO will report one or more of the following:

CPU <n>: This core does not support long mode
CPU <n>: This core does not support VT
CPU <n>: Feature control MSR is unlocked!
CPU <n>: VT is disabled in the feature control MSR!
CPU <n>: VT is enabled on this core.

This core does not support long mode

If the ISO reports that some core(s) do not support long mode, you will not be able to use VT-x with current VMware products. You can use VT-x for 32-bit guests with Workstation 5.5 or 6.0.x, Fusion 1.x, or ESX 3.0, but this configuration is not supported. See  VMware Products and Hardware-Assisted Virtualization (VT-x/AMD-V).

This core does not support VT

If the ISO reports that some core(s) do not support VT, you will not be able to use VT-x. There are Intel CPU errata which may result in this capability being reported incorrectly. See «Your VMware product says that your host does not support VT,» above.

Feature control MSR is unlocked!

If the ISO reports that some core(s) leave the feature control MSR unlocked, current VMware hosted products will automatically enable and lock VT. A workaround exists for older VMware products. See «Enabling VT-x if Unlocked,» below.

VT is disabled in the feature control MSR!

If the ISO also reports that these core(s) leave the feature control MSR unlocked, current VMware hosted products will automatically enable and lock VT. A workaround exists for older VMware products. See «Enabling VT-x if Unlocked,» below.  However, if the ISO reports that VT is disabled on some core(s) and it does not also report that the feature control MSR is unlocked on these core(s), then it is impossible to enable VT-x through software.

Enabling VT-x if Unlocked

This is already the default behavior for current VMware hosted products (Workstation 7.x, Player 3.x, and Fusion 3.x or newer). For older products, the following workaround may help if your firmware leaves VT-x unlocked, either at power-on, or after hibernate or sleep. Simply add the following option to your system-wide configuration file:

hv.enableIfUnlocked = TRUE

On Linux systems, the system-wide configuration file is /etc/vmware/config. On Windows systems, the system-wide configuration file varies according to VMware product and Windows version. For VMware Workstation on XP hosts, the system-wide configuration file is C:Documents and SettingsAll UsersApplication DataVMwareVMware Workstationconfig.ini. For VMware Workstation on Vista or Windows 7 hosts, the system-wide configuration file is C:ProgramDataVMwareVMware Workstationconfig.ini. For other VMware products, adjust the path appropriately.

При установки 64-х битной операционной системы Windows в программе VMware Workstation вылетела ошибка:

This host supports intel vt-x but intel vt-x is disabled

Данная ошибка говорит о то, что на компьютере не включен параметр Virtualization Technology (Виртуализация) – что бы его включить, надо:

1. перезагрузить компьютер
2. войти в BIOS
3. найти параметр Virtualization Technology
4. перевести его в Enable
5. сохранить настройки и перезагрузится
6. проверяем и радуемся что теперь виртуальная машина заработала

таким нехитрым способом мы включили Virtualization Technology и победили ошибку supports intel vt-x 

i have Ubuntu 64bit Boot disk , i configured everythihng in VMWare , created virtual machine ….
and when i power on the virtual machine , there is a black screen with VMWare Logo on it and loading then a error pops on with error :

This virtual machine is configured for 64-bit guest operation systems.
However, 64-bit operation in not possible

This host supports Intel VT-x, but Intel VT-x is disabled

Intel VT-x might be disabled if it been disabled in the BIOS/firmware settings or the host has been power-cyclen since changing this setting.

(1) Verify that BIOS/firmware settings enable Intel VT-x and disable 'trusted execution'.

(2)Power-cycle the host if either of these BIOS/firmware settings have been changed.

(3)Power-cycle the host if you have not done so since installing VMware Workstation

(4)Update the host's BIOS/firmware to the lastest version.

My Info :

Sony/Vaio VGN-FW378J
Windows 10 64-bit
Intel(R) Core(TM)2 Duo CPU p8600 @ 2.40GHz 2.40 GHz
4.00 GB Ram

I only updated BIOS driver ( i downloaded update from sony site )

How I Can Fix This ?

Thanks,

ИТ База знаний

Курс по Asterisk

Полезно

— Узнать IP — адрес компьютера в интернете

— Онлайн генератор устойчивых паролей

— Онлайн калькулятор подсетей

— Калькулятор инсталляции IP — АТС Asterisk

— Руководство администратора FreePBX на русском языке

— Руководство администратора Cisco UCM/CME на русском языке

— Руководство администратора по Linux/Unix

Навигация

Серверные решения

Телефония

FreePBX и Asterisk

Настройка программных телефонов

Корпоративные сети

Протоколы и стандарты

Привет, друг! Если ты читаешь эту статью, то скорее всего столкнулся с ошибкой VT-x/AMD-V hardware acceleration is not available on your system когда пробовал создать виртуальную машину в Virtual Box, или такой ошибкой при работе с VMWare: This host supports Intel VT-x, but Intel VT-x is disabled или чем-то похожим при работе с другой средой виртуализации. Продолжай читать и ты обязательно найдёшь причину!

Вместе и с нуля пройдем все этапы проектирования, администрирования, резервирования и масштабирования БД с использованием PostgreSQL, MS SQL и MySQL

Для начала, позволь вкратце объяснить, что такое VT-x и AMD-V.

VT-x – это технология, разработанная компанией Intel в 2005 году, которая позволила процеcсорам (CPU) данного производителя поддерживать аппаратную виртуализацию. Грубо говоря, появилась возможность имея один компьютер, создать другой внутри него и даже с другой операционной системой!

AMD-V — это технология аппаратной виртуализации от компании AMD. Первые процессоры от производителя AMD появились на рынке годом позже, в 2006 году.

Итак, теперь вот тебе топ 3 причин, по которым ты мог встретить вышеупомянутые ошибки:

• Процессор твоего «комплюктера» попросту не поддерживает технологии виртуализации VT-x/AMD-V.

Возможно ты являешься обладателем очень старого или наоборот крайне специфичного девайса, CPU которого просто не умеет в виртуализацию. В таком случае, ты не сможешь устранить те ошибки и запустить виртуалку в любой среде виртуализации. Но не огорчайся, есть масса способов покрутить виртуалки, например, воспользоваться услугами VDS/VPS хостера!

Hyper-V это проприетарная технология виртуализации от Microsoft, которая по умолчанию вырубает поддержку VT-x/AMD-V, чтобы избежать конфликтов. Короче придётся выбирать между Hyper-V и другой конфликтующей средой виртуализации.

• Технология VT-x или AMD-V просто выключены и их нужно включить.

По умолчанию, поддержка виртуализации выключена в BIOS и чтобы победить ошибки из начала статьи и, наконец запустить заветную виртуалку, тебе нужно просто зайти в BIOS и включить VT-x/AMD-V!

В зависимости от производителя твоего компьютера, может быть несколько вариантов перехода в BIOS. Обычно, тебе нужно просто перезагрузить компьютер и дождаться на экране надписи: Press to enter BIOS, а вот какая-то кнопка может быть разной.

Вот тебе несколько примеров для разных производителей:

• Asus, Lenovo, DELL
• Как правило просят нажать F2
• Перейти на вкладку Advanced, выбрать Virtualization Technology и нажать Enter
• Сменить состояние строки с Disabled на Enabled после чего нажать F10, чтобы сохранить изменения и перезагрузить компьютер

• Acer, HP
• Как правило просят нажать F2 ну или F1 или же CTRL+ALT+ESC или F10
• Нажать на правую стрелку и перейти на вкладку System Configuration, выбрать Virtualization Technology и нажать Enter
• Сменить состояние строки с Disabled на Enabled после чего нажать F10, чтобы сохранить изменения и перезагрузить компьютер

• Компьютеры с процессорами AMD
• Как правило просят нажать F2
• Выбрать вкладку Advanced затем CPU Configuration, после чего выбрать SVM Mode и нажать Enter
• Сменить состояние строки с Disabled на Enabled после чего нажать F10, чтобы сохранить изменения и перезагрузить компьютер

Интенсив по Виртуализации VMware vSphere 7

Самое важное про виртуализацию и VMware vSphere 7 в 2-х часовом онлайн-интенсиве от тренера с 30-летним стажем. Для тех, кто начинает знакомство с виртуализацией и хочет быстро погрузиться в предметную область и решения на базе VMware

Полезно?

Почему?

😪 Мы тщательно прорабатываем каждый фидбек и отвечаем по итогам анализа. Напишите, пожалуйста, как мы сможем улучшить эту статью.

😍 Полезные IT – статьи от экспертов раз в неделю у вас в почте. Укажите свою дату рождения и мы не забудем поздравить вас.

Источник

Intel vt x error in vmware

I just upgraded to Workstation 16 Pro as it said it would work with Hyper-V, and I want to run docker desktop.

However I am getting the error: «Error «Virtualized Intel VT-x/EPT is not supported on this platform». Every time I search it I get the result of «disable hyper-v», but I just spent a bunch of money to be able to run this with hyper v.

The thing I am trying to run is Cisco Modeling Labs (CML): a VM that spins up VMs of routers/switches/etc.

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

As you’re mentioning Hyper-V, your host OS must be windows.

Not all versions of Windows however are supported for this to work and this might be what you are running into.
AFAIK, this only works on Windows 10 and the minimum version of Windows 10 is 20H1 build 19041.264 or newer.

edit: Wait.. oh dear. I now realize that I might to be misreading it.

The above requirements are for being able to run a guest OS in VMware Workstation while Hyper-V is enabled at the host OS.
This does NOT allow you to run a guest OS in your VM itself. The only way to run a nested VM is to disable the Hyper-V role on the host OS where you run VMware Workstation. In that scenario nested VMs work fine and you can even run Hyper-V in your guest OS.

Hope this helps,
—
Wil

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

moderator: Moved the thread to VMware Workstation Pro discussions. Your question is indeed about nested virtualization, but the discussion area where it was posted was specific for vSphere. You’re likely to get better answers here.

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

Unfortunately, Hyper-V API does not allow for nested virtualisation – the only way to use that is to disable Hyper-V on the host and let Workstation use its own virt.

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

This host supports Intel VT-x, but Intel VT-x is disabled.

Intel VT-x might be disabled if it has been disabled in the BIOS/firmware settings or the host has not been power-cycled since changing this setting.

(1) Verify that the BIOS/firmware settings enable Intel VT-x and disable ‘trusted execution.’

(2) Power-cycle the host if either of these BIOS/firmware settings have been changed.

(3) Power-cycle the host if you have not done so since installing VMware Workstation.

(4) Update the host’s BIOS/firmware to the latest version.

This host does not support «Intel EPT» hardware assisted MMU virtualization.

VMware Workstation does not support the user level monitor on this host.

Module ‘MonitorMode’ power on failed.

Failed to start the virtual machine.

i enabled the v tech in my bios, but it still say the same thing, before it was not enabled, it was still saying the same thing as well

how can i overcome and win,

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

This problem starts in case you update your existing windows 10 version to 20H1, 21H2 or later version.

For me it was working with old Windows 10 Version. Windows 10 was automatically updated and problems starts for me and I was unable to work with VMware Workstation Pro 16. Even I replace workstation version with 12 & 14 but same issue. The higher version of Windows 10 is coming with Hyper-V which can’t allow to work VMware workstation together.

After a lots of struggle I was able to resolve this issue with below changes:-

1. Go to windows services with type services.msc in RUN

2. Stop all Hyper-V services.

3. Go to control panel —- program and features—Turn windows feature ON/OFF—Untick Hyper-V—Ok- —to remove from Windows 10.

4. Run below PowerShell command for VMware Nested Virtualization issues:-

If u want use vmware : use this command in powershell and reboot system:

To disable Hyper-V use this command:- bcdedit /set hypervisorlaunchtype off

( If u want use hyper-v: use this command : bcdedit /set hypervisorlaunchtype auto)

5. Hyper-v and Vmware still don’t work together so make below changes in windows Registry:-

To disable Device Guard or Credential Guard :—

Disable the group policy setting that was used to enable Credential Guard.

1. On the host operating system, click Start > Run, type gpedit.msc, and click Ok. The Local group Policy Editor opens.
2. Go to Local Computer Policy > Computer Configuration > Administrative Templates > System > Device Guard > Turn on Virtualization Based Security.
3. Select Disabled .

Restart desktop and try to check .

I hope this can work for all of you as this working for me now.

Источник

Quick Guide to fix Error «This host supports Intel VT-x» in VMware Workstation

Hello Everybody,
Have you ever installed and used VMware virtual machine to work? If you have already used it, then it is inevitable that a frequent error occurs during the installation of VMware Workstation as below:

The specific error contents are as follows:

This host supports Intel VT-x, but Intel VT-x is disabled.
Intel VT-x might be disabled if it has been disabled in the BIOS / firmware settings or the host has not been power-cycled since changing this setting.
(1) Verify that the BIOS / firmware settings enable Intel VT-x and disable ‘trusted execution.’
(2) Power-cycle the host if either of these BIOS / firmware settings have been changed.
(3) Power-cycle the host if you have not done so since installing VMware Player.
(4) Update the host’s BIOS / firmware to the latest version.
This host does not support «Intel EPT» hardware assisted MMU virtualization.
This host does not support virtualizing real mode. The Intel «VMX Unrestricted Guest» feature is necessary to run this virtual machine on an Intel processor.
Module ‘CPUIDEarly’ power on failed.Failed to start the virtual machine

Reason:
Normally by default, the VT-x function (which supports running virtual machines) is turned off or disabled by the manufacturer. When you install the VMware program and launch it, the computer will report the error as above.
Today, QTit will give you a quick guide to help you fix this common error.

Keyboard shortcut to access BIOS SETUP

Step 2: Access to the Virtualization function (usually located on the Security or Virtualization Support tab)

Step 3: Find 2 items with similar content:
+ Intel (R) Virtualization Technology
+ Intel (R) VT-d Feature
You will now see that the functions are in Disabled mode. Please Enabled them.

By default, the Virtualization function is disabled by the manufacturer

Select Enabled mode to enable Virtualization function in BIOS SETUP

After customization is complete, press F10 to save your settings. Now try again on VMware to see if the error is gone!

Simple, right? With a few basic steps you can fix the error and and enable virtualization technology in windows 10.

In addition, if you have any problems with your computer, please contact us directly through the QTitHow fanpage. We will try to help and answer you as soon as possible. Thank you!

Tags: this host supports intel vt-x but intel vt-x is disabled, this host supports intel vt-x, how to enable virtualization in bios windows 10, how to enable virtualization in windows 10, how to enable vt in windows 10, how to enable vt on windows 10, how to enable virtualization technology in windows 10

Источник

VMware Workstation is a professional virtualization solution that allows you to do a lot of things and is able to manage many virtual machines at the same time (if the resources of the host PC allow it).
However, in rare cases (and especially when you edit manually some settings in the vmx files), VMware Workstation can become unstable and arrive in a state where you will not be able to access or close some virtual machines.

Again, this is very rare, but here is how to solve ou avoid these problems.

1. Take ownership error
2. Freeze of a virtual machine
3. Conflict detected : Panda USB vaccine
4. Conflict detected : Disk Management
5. The device was unable to connect to its ideal host controller
6. This VMware USB Device can perform faster
7. This host supports Intel VT-x, but VT-x is disabled

1. Take ownership error

At some moments, you may not have access to a virtual machine (even if it’s down and not password protected).

When you want to access it from VMware Workstation, a «This virtual machine appears to be in use» warning is displayed.
VMware Workstation offers you to obtain the rights on it by clicking on : Take Ownership.

Plain Text

If this virtual machine is not in use, press the "Take Ownership" button to obtain ownership of it. Otherwise, press the "Cancel" button to avoid damaging it.

This warning can occur in 2 cases :

• you have opened 2 windows of VMware Workstation and you are trying to open the same virtual machine from the 2 windows. In this case, click : Cancel.
• VMware Workstation has become unstable or a bug is temporarily blocking you from accessing it. In this case, click : Take Ownership.

Most of the time, it will fail and this message will appear :

Plain Text

Could not open virtual machine ... .vmx

Taking ownership of this virtual machine failed.

The virtual machine is in use by an application on your host computer.

Configuration file: ... .vmx

Click Cancel.

Note that in older versions of VMware Workstation, the icon displayed was an error icon and the «Remove» button did not exist.
With these older versions, you had to click OK.

Since VMware Workstation can’t open this virtual machine, a red icon appears on it.

To solve this problem, close all open VMware Workstation windows and open VMware Workstation again, but as an administrator.

Click Yes.

Now, you will have access to your virtual machine.
From now, you will be able to access it again normally (without having to restart VMware Workstation every time as administrator).

2. Freeze of a virtual machine

When you run too many virtual machines at the same time or you have mismanaged the amount of RAM allocated to them, your virtual machines may fail.

If it’s not too late, try pausing them to prevent the guest OS from being damaged. Then, restore the virtual machines one by one by stopping them correctly before «booting» the next virtual machine.

If it’s too late, you may not be able to force the virtual machine to shutdown from VMware Workstation.
Indeed, in this case, we wanted to shut down Windows properly by sending the Windows shutdown ACPI signal from VMware Workstation (via the «Shut Down Guest» option).
The problem is that the virtual machine never stopped, and because the virtual machine was shut down, no more options were available for this virtual machine.
Even when you want to close VMware Workstation to force the virtual machine to shut down, it will not work because VMware Workstation will display this warning : Virtual machine is busy.

In this case, you will only have 2 possibilities :

• shut down your computer : except that shutting down your computer will take a long time, because of this problem. Even if in the end after a few minutes, even 10 minutes, the host PC will finally turn off properly.
• stop other virtual machines that you can still shut down properly, then kill the «vmware-vmx.exe» process that allows the virtual machine to run on the host PC.

The only problem is that you can’t know which instance of the «vmware-vmx.exe» process corresponds to which virtual machine.
For security, you will have to shut down all possible virtual machines before killing this process or processes. Otherwise, you risk cutting off a virtual machine that was still running correctly.

Confirm the action.

Like magic, the virtual machine will be considered shut down by VMware Workstation.
Nevertheless, don’t forget that the sudden shutdown of the «vmware-vmx.exe» process only allows you to recover your hand on the management of the host PC.

Indeed, by killing the «vmware-vmx.exe» process, the host PC will become unstable because of the information left in its RAM.
This may result in a slower shutdown of your host PC when you shut down Windows this time.
Once the host PC is shutdown and then power on again (and not with an automatic restart from Windows), the RAM will be correct again.

This solution therefore only allows you to save what you were doing, rather than losing important changes because of a virtual machine that would have become unstable.

3. Conflict detected : Panda USB vaccine

On our InformatiWeb.net website, we talked about the Panda USB Vaccine program that automatically vaccinate USB keys that you connect to your computer to prevent a virus on a USB key infect your physical PC.

The problem is that from the moment you use VMware Workstation, you will not be able to use the automatic vaccination of USB keys with Panda USB Vaccine.

When at least 1 virtual machine is running with VMware Workstation, if you plug an USB key on your physical PC, VMware Workstation and the currently powered virtual machine will be freezers.
Which is very problematic.

To avoid this conflict, we recommend that you no longer use Panda USB Vaccine on your PC where VMware Workstation is installed.

Update : this problem no longer occurs on Windows 10 v2004.

4. Conflict detected : Disk Management

As you probably know, on Windows, you can manage disks (and their partitions) by right-clicking on Computer (or This PC), then clicking on : Disk Management.

The problem is that when virtual machines run on VMware Workstation on your PC, there is a good chance that your PC (including VMware Workstation and the «Computer Management» console) will start blocking (freezing).

Update : this problem no longer occurs on Windows 10 v2004.

It’s pretty annoying, but be aware that this bug only occurs if virtual machines are running when you want to manage physical PC disks.
If no virtual machine is currently running, disk management will be possible without any problem.

PS : if you konw other conflicts that occur each time in the same way, don’t hesitate to point them out in comments for us to add them in this tutorial.

5. The device was unable to connect to its ideal host controller

Depending on the guest OS you are virtualizing, VMware Workstation selects the most suitable version for the USB controller of your virtual machine.
However, this can be problematic in some cases.

For example : you can’t plug an USB 3.0 key into an USB 3.0 port on the host PC and pass it to a virtual machine using a USB 2.0 or lower controller.

If VMware Workstation displays the «New USB Device Detected» window, select the virtual machine to which you wish to connect the USB key (or any other USB support).

As mentioned above, you will not be able to plug an USB 3 key into an USB 3 port on the host PC and pass it to a virtual machine using version 2.0 or lower of the USB controller.
In this case, an error will be displayed :

Plain Text

The device '[Name of the USB 3.0 key]' was unable to connect to its ideal host controller. An attempt will be made to connect this device to the best available host controller. This might result in undefined behavior for this device.

Click OK.

Due to the previous error, an error will also be displayed in the guest OS :

Plain Text

USB Device Not Recognized
One of the USB devices attached to this computer has malfunctioned, and Windows does not recognize it.
For assistance in solving this problem, click this message.

If you click on this message, you will see a window appear with an «USB Root Hub» and an «Unknown Device» (which corresponds to your USB key).

In the device manager, you will see the same problem.

To solve this problem, simply plug your USB key into a USB 2.0 port on your host PC.
Or change the version of the virtual machine’s USB controller to USB 3.0 if you want to connect it to a USB 3.0 port on your host PC.

6. This VMware USB Device can perform faster

If you plug an USB 3.0 key or any other USB storage medium (such as an external hard drive) to an USB 2.0 port on your host PC, this message will be displayed on the host PC where VMware Workstation is installed.

Plain Text

This device can perform faster.
This VMware USB Device can perform faster if you connect it to a Hi-Speed USB 3.0 port.

When you pass this USB 3.0 key to your virtual machine, a similar message will appear :

Plain Text

This USB Mass Storage Device can transfer information faster ...

However, the USB key will be accessible from the guest OS.
As you can check in the device manager.

7. This host supports Intel VT-x, but VT-x is disabled

When you launch one of your virtual machines, one of these messages appears :

Plain Text

Binary translation is incompatible with long mode on this platform.
Disabling long mode. Without long mode support, the virtual machine will not able to run 64-bit code. For more details see https://vmware.com/info?id=152.

Plain Text

This virtual machine is configured for 64-bit guest operating systems.
However, 64-bit operation is not possible.

This host supports Intel VT-x, but VT-x is disabled.

Intel VT-x might be disabled if it has been disabled in the BIOS/firmware settings or the host has not been power-cycled since changing this setting.

(1) Verify that the BIOS/firmware settings enable Intel VT-x and disable 'trusted execution.'

(2) Power-cycle the host if either of these BIOS/firmware settings have been changed.

(3) Power-cycle the host if you have not done so since installing VMware Workstation.

(4) Update the host's BIOS/firmware to the latest version.

For more detailed information, see https://vmware.com/info?id=152.

Depending on your version of VMware Workstation Pro, the error message may be a bit longer and include this :

Plain Text

VMware Workstation does not support the user level monitor on this host.

Module 'MonitorMode' power on failed.

Failed to start the virtual machine.

These errors occur when processor virtualization is not supported by your processor (CPU), motherboard BIOS, or not enabled by default in your motherboard BIOS.

If your processor supports processor virtualization (Intel VT-x or AMD-V), you just need to enable it in your motherboard BIOS.

Important : if you have just installed VMware Workstation and the «This host supports Intel VT-x, but VT-x is disabled» error message appears, restart your computer at least once.
If this error message persists, then processor virtualization is not enabled and/or supported by the BIOS of your motherboard.