Vmware workstation неисправимая ошибка vcpu 0

Make you have you enabled Secure Virtual Machine (SVM) in the EFI/BIOS.

If you have already enabled SVM, try disabling multithreading (SMT) in the EFI/BIOS.

In case you are overclocking, please disable any overclocking in the EFI/BIOS as well.

On an unrelated issue but presents potentially a problem, there are several lines that appear like this in the log as the virtual disk of the VM is being opened.

2017-08-06T20:06:18.583+01:00| vmx| I125: DISKUTILWIN32: DiskUtilW32IsATASSDDevice: Failed to send ATA IDENTIFY command to the target device.

2017-08-06T20:06:18.583+01:00| vmx| I125: DISKUTILWIN32: DiskUtilW32IsScsiSSDDevice: Reported rotation rate = 1

2017-08-06T20:06:18.585+01:00| vmx| I125: DISKUTILWIN32: DiskUtilW32IsATASSDDevice: Failed to send ATA IDENTIFY command to the target device.

2017-08-06T20:06:18.585+01:00| vmx| I125: DISKUTILWIN32: DiskUtilW32IsScsiSSDDevice: Reported rotation rate = 1

What is the physical drive model where this VM is stored? These lines in the log suggest something could be wrong with the drive.

Some users are encountering the VMware Workstation Unrecoverable Error: (vcpu-0) error when trying to install a second operating system on a particular computer. Some users report that the error occurs when setting up the second virtual machine while others report that it gets triggered whenever they try to boot from it. The issue doesn’t seem to be specific to a certain operating system since it’s reported to occur with OsX, Windows and Linux installations.

What is causing the VMware Workstation Unrecoverable Error: (vcpu-0)

We investigated this particular issue by looking at user reports and the repair strategies that they used to get the issue resolved. Based on what we gathered, there are several common scenarios that will trigger this particular error message:

If you’re currently struggling to resolve this particular error message, this article will provide you with a selection of potential repair strategies. Below you have a collection of methods that other users in a similar situation have used to get the VMware Workstation Unrecoverable Error: (vcpu-0) error resolved. For the best results, follow the potential fixes below in order until you encounter a method that is effective in your particular scenario.

Method 1: Updating the VMware Workstation application

Before you try anything else, it’s important to ensure that you’re running the latest VMware Workstation version. There are a lot of users reports that point towards a bug being responsible for the VMware Workstation Unrecoverable Error: (vcpu-0) error in Vmware Workstation 11.

Since this bug has already been patched by the developers, you will be able to eliminate the issue by ensuring that your VMware Workstation client is updated to the latest version. To do this, simply open VMware Workstation and go to Player > Help > Software Updates.

Once you get to the Software Updates screen, click on Check for Updates and see if a new version is available. If it is, follow the on-screen prompts to install it on your computer.

Once the newer version is installed, restart your computer and see if the issue has been resolved. If you’re still encountering the VMware Workstation Unrecoverable Error: (vcpu-0) error, move down to the next method below.

Method 2: Disabling / Uninstalling another organization’s virtualization software

You might be encountering this issue because VMware Workstation and Oracle VM VirtualBox are both running at the same time. Although this is mainly reported to occur when the user tries to run a macOS virtual machine, some affected users have reported that the issue was resolved as soon as they closed Oracle VM Virtualbox.

Other users have reported that the issue was only resolved after they uninstalled Oracle VM VirtualBox. Just to ensure that a software conflict is not facilitating the apparition of the VMware Workstation Unrecoverable Error: (vcpu-0) error, we urge you to follow the steps below to uninstall  Oracle VM VirtualBox (or similar rival virtualization software):

1. Press Windows key + R to open up a Run dialog box. Then, type “appwiz.cpl” and press Enter to open up Programs and Features.
2. Inside Programs and Features, scroll through the list of applications and locate Oracle VM Virtualbox (or a different rival virtualization software). Once you see it, right-click on it and choose Uninstall.
3. Once the rival organization’s software has been removed, restart your computer and see if the issue has been resolved at the next startup.

If you’re still encountering the VMware Workstation Unrecoverable Error: (vcpu-0) error, move down to the next method below.

Method 3: Enabling Secure Virtual Machine (SVM) or Intel Virtualization Technology from BIOS/UEFI

SVM (Secure Virtual Machine) is the equivalent of Intel VT-x/Intel Virtualization technology on some machines. But regardless of the virtualization technology that your computer is using, it needs to be enabled in order to ensure that virtual machines are running smoothly.

Enabling SVM or Intel Virtualization is only possible by entering your BIOS/UEFI settings – this procedure will be different according to your motherboard manufacturer. However, there are some similarities.

The first step would be to enter your BIOS/UEFI settings – This procedure will require to press the Setup key during the initial booting sequence. The Setup key should appear on the initial screen, but just in case it doesn’t, you can do an online search with “your motherboard mother + setup key ” to discover your Setup key.

Now, the next screen will be different depending on if you have entered the legacy settings (BIOS) or the newer UEFI. Keep in mind that every major motherboard manufacturer will have different menus and settings names. Most commonly, you will be able to find the SVM Mode under Advanced > CPU Configuration. Just set it to Enabled and don’t forget to save the changes before exiting the BIOS/UEFI settings.

Once SVM mode or Intel Virtualization Technology has been enabled, restart your computer and see if the VMware Workstation Unrecoverable Error: (vcpu-0) error has been resolved. If you’re still seeing the error when trying to launch or create a virtual machine using VMware Workstation, move down to the next method below.

Method 4: Disabling simultaneous multithreading (SMT) in the BIOS/UEFI

There are a few reasons why you’d want to disable SMT (Simultaneous multithreading). Although keeping this option disabled might yield slightly better performance with some GPU’s, we don’t recommend doing so unless you really need to.

Several users encountering the VMware Workstation Unrecoverable Error: (vcpu-0) error have managed to resolve it after disabling simultaneous multithreading (SMT) from their BIOS settings. Although there’s no official explanation from the developers, affected users are speculating that VMware Workstation is conflicting with SMT on several different configurations.

To disable SMT, you’ll need to enter your BIOS settings. To do this, access your BIOS settings by pressing the Setup key during the initial screen.

Keep in mind that depending on your CPU manufacturer, the name of the SMT option will be different. For example, Intel (R) Hyper-Threading is Intel’s proprietary simultaneous multithreading technology.

Once you get into your BIOS settings, it becomes a matter of finding out the control options for SMT. Typically, you will be able to find it under one of the following sub-menus: Tweaker Config, CPU Feature, Advanced BIOS, Performance, Processor, CPU.

Depending on which BIOS/UEFI version and motherboard manufacturer you’re working with, the control option dedicated to this technology might be one of the following: Intel (R) Hyper-Threading, Hyper-Treading technology, Hyperthreading function, CPU Hyper-Threading or Hyper thread control.

Once you manage to find this option, set it to disable, restart your computer and see if the VMware Workstation Unrecoverable Error: (vcpu-0) error is resolved. If you are still seeing the same error message when trying to run a virtual machine, move down to the next method below.

Method 5: Reverting to the default clocking frequencies

Several users struggling to resolve the VMware Workstation Unrecoverable Error: (vcpu-0) error have finally discovered that the issue was only occurring if the CPU frequency was overclocked. As soon as they reverted to the default CPU frequency, the issue went away.

This suggests that the issue can also be triggered if the initial checks performed by VMware Workstation reveals some inconsistencies regarding your CPU frequencies. As it turns out, the software might throw this error if it notices that the host machine CPU resources are different than the original specs.

If you know you are overclocked, access your BIOS/UEFI settings, go to the Overclocking sub-menu and revert to the default frequencies.

Once the CPU is reverted to the default frequencies, run the virtual machine again and see if the issue has been resolved. If you’re still encountering the VMware Workstation Unrecoverable Error: (vcpu-0) error, move down to the next method below.

Method 6: Modifying the VMX file

If you’re encountering the VMware Workstation Unrecoverable Error: (vcpu-0) error when trying to run or configure a Mac OS Virtual machine, you’re most likely encountering this issue because VMware Workstation is not designed to virtualize Apple Hardware. Normally, in order to run Mac OS, you’ll need a Mac Book coupled with VMware Fusion.

However, there is a way to circumvent the issue and allow MacOS to be virtualized by Workstation 11. All you have to do is add a code line to the VMX file. Here’s a quick guide on how to do this:

1. Visit this link (here) and click on the Download button to download the latest version of Notepad++.

   Note: You can skip step 1 to 3 and open the .vmx file with Notepad, but you run the risk of inserting the code line in the middle of another one – which can ruin the configuration file.

2. Open the Notepad++ installation and follow the on-screen prompts to install the software on your computer.
3. Once Notepad++ is installed, navigate to the location of the virtual machine that is showing you the Workstation Unrecoverable Error: (vcpu-0) error. Once you get there, right-click on the .vmx file and choose Edit with Notepad++.

   Note: If you didn’t install Notepad++, choose Open with… > Notepad instead.

4. With the VMX file opened, paste the following line of code:

   smc.version = 0

   Note: You don’t have to paste it in a specific place. Anywhere is fine as the file will be auto-sorted after you save it. All you have to do is make sure that you don’t paste it in the middle of another code line.

   

5. Save the .VMX file and re-open the virtual machine. You should no longer encounter the VMware Workstation Unrecoverable Error: (vcpu-0) error.

According to some users, when trying to install a new Operating System, they see VMware Workstation Unrecoverable Error (vcpu-0). The error is very notorious as it doesn’t allow users to install an OS. The second paragraph of the error message may vary from user to user, but the error is the same.

Therefore, in this article, we are going to see why you are seeing this error and how you can fix it.

What is causing the VMware Workstation Unrecoverable Error (vcpu-0)?

VMware Workstation Unrecoverable Error can be caused by many different things such as interference of another Virtual Machine. So, you have to close all the other Virtual Machines before using this one. Other than that the issue can be because of some BIOS/UEFI settings, such as disabled Hardware Virtualization, that we need to alter in order to run the game. We will also see some workarounds and some setting adjustments that helped other victims resolve this issue.

If you want to fix VMware Workstation Unrecoverable Error (vcpu-0) then start by updating your computer. Install the latest update and then execute the solutions given below to resolve the issue.

1. Close other Virtualization Programs
2. Update VMware Workstation
3. Enable Hardware Virtualization
4. Stop Overclocking
5. User Fewer Cores

Let us talk about them in detail.

1] Close other Virtualization Programs

If you have another Virtualization application such as VirtualBox running in the background then you will see the error in question. You need to close all of them before opening a VM in VMware Workstation. A better way to do the same would be to check the Task Manager and see if the process is running. If it is, then you need to right-click on it and select End Task. After doing that, check if the issue persists.

2] Update VMware Workstation

The error can appear because of a bug, but the bug can be removed by an update. Hence, we are going to update VMware Workstation and see if the issue persists. To check for Software Updates, you can open VMware Workstation and click Help > Software Updates.

After installing pending updates, you need to restart your system and then check if the issue persists.

3] Enable Hardware Virtualization

You need to make sure that you have enabled Hardware Virtualization from the BIOS/UEFI. So, check its state and enable the feature if it is disabled. After enabling Hardware Virtualization, check if the issue persists.

4] Stop Overclocking

If you have overclocked your CPU with the help of an application then this can cause issues. Overclocking can crash a game or stop the functioning of Virtual Machines. So, if you have done Overclocking, set it back to normal and see if the issue persists.

5] Use Fewer Cores

You need to make sure that VMware is not using more than one core. According to many users, assigning more than one core to VMware with Windows VMs can cause such issues, whereas, for something like Ubuntu, it works fine even with four cores. So, we need to alter some settings and see how VMware works afterward. Follow the given steps.

1. Open Task Manager.
2. Go to Details.
3. Look for VMware Workstation or vmware.exe, right-click on it and select Set affinity.
4. Now, just tick one core (CPU 0) and click Ok.

Finally, restart your system, reopen VMware and see if the issue persists.

How do I unfreeze my VMware workstation?

If VMware Workstation freezes, then there are two things that you can do, either go to Task Manager, right-click on VMware, and select End Task, or force shutdown by long-pressing the power button. But if this issue is frequent then you can through the solutions mentioned here and see if that helps. If that doesn’t help then try to lower the strain on your CPU, you can do this by restarting the computer before using the VMs, turning off your Internet, or stopping all your processes and apps.

Read Next:

• VMware Workstation Pro can’t run on Windows 10 computer
• Fix VMware operating system not found Boot error

Решил поместить пока что в отдельный блог.

На данный момент найдено два решения сей проблемы, оба до конца не проверены.

Исходные корни проблемы — в динамической системе распределения памяти во VMware. Запустив виртуалку, вы теоритески должны отнять весь объем памяти виртуалки у основной машины. Но программа-гипервизор (научное название основного элемента VMware) выдает не весь объем, а лишь необходимый для пуска, остальное «выклянчивается» у системы по мере необходимости. Но почему-то в определенный момент Windows отказывает на выделении памяти — итого мы видим ошибку vcpu

Способ 1. Смена Windows

Идея такая — какая-то из версий Windows может более удачно работать с памятью, заставив систему протянуть больше времени до часа х. В первую очередь тут ставка на серверные редакции, т. к. они создавались с учетом возможности такой эксплуатации

Предварительно есть такие данные:

Windows XP — ошибка присутствует

Windows 2003 Server — не тестировалась

Windows 2003 Server R2 — ошибка присутствует

Windows Vista — не тестировалась

Windows 2008 Server — не тестировалась

Windows 7 — не тестировалась, предположительно ошибка наступает позже

Windows 2008 Server R2 — не тестировалась, предположительно ошибка наступает позже

Windows 8 — не тестировалась, предположительно ошибка наступает позже

Windows 2012 Server — не предположительно ошибка наступает позже

О строчках с припиской Server

1) Серверные Windows, начиная Windows Server 2003 R2, так или иначе оптимизированы под запуск на виртуальных машинах

2) Они в состоянии после установки не способны запустить более-менее современное 3D приложение, да и серверная система входа и логирования сделает вам мозг. Нужна настройка, подобный гайд я писать не хочу, а информации о переделке серверной системы для работы в режиме рабочей станции полно в интернете.

3) Не стоит пытаться найти Windows Server 2008 R2 и 2012 под 32 бита. Такие попросто не выпускались. Т. е. вам нужен процессор с поддержкой х64 инструкций, даже если у вас х86 основная система. Соответсвенно вы получите соответствующее х64 системе поглощение памяти. Решайте нужно ли вам это на и так слабой х86 системе.

Способ 2: Настройка VMware

Для этого нужно

1) Открыть файл C:Program FilesVMwareVMware Workstationconfig.ini

2) Ввести там строку vmmon.disableHostParameters = «TRUE», сохранить файл

Если такого файла нет — открываем блокнот и создаем его. Ну а если это для вас сверх трудно. Извлечете файлик config.ini в выше указанную папку если его там нет, если есть, то придется ручками вводить строчку.

3) Открыть Edit Virtual mashines Settings (т. е. настройки виртуальной машины) — Options — Advanced и там поставить галку Disable Memory Page Trimming.

 скрытый текст

4) Отключаем файл подкачки в виртуальной машине Панль Упраления — Система — Дополнительно — Быстродействие — Дополнительно — Виртуальная Память — Изменить — Без файла подкачки

 скрытый текст

5) Перезапускаем виртуалку (если была запущена), желательно и комп.

Дополнительно делаем

1) Открываем файл C:Documents and SettingsИмя_пользователяМои документыVirtual MashinesНазвание_машиныназвание_машины.vmx

2) Вписываем в конец файла строки

mainMem.useNamedFile=FALSE

monitor_control.disable_mmu_largepages=TRUE

3) Сохранить, перезапустить виртуальную машину если запущена

СПОСОБ 2 ПРОВЕРЕН НЕ ДО КОНЦА!!!

Как издежать необходимости перезагрузки в случае vcpu0

Итак? такой «костыль» — после вылета идем в папку расположения жесткого диска машины и удаляем папку названиемашины.lck

В случае неработоспособности какого-нить варианта — пишите об этом в комментариях. То что работает у меня не обязательно что сработает на другой системе.