Product: Avast Update Helper — Error 1316. The Specified Account Already Exists.

When launching a virtual machine, such as Windows 10, Linux, or macOS, the “CPU has been disabled by the guest operating system” problem is common. Incorrect VT-X settings are frequently to blame.

A disc configuration issue, file corruptions and an invalid CPU ID are also to blame. Here are the appropriate answers. So, let’s take a look at each of these options one at a time.

Product: Avast Update Helper -- Error 1316. The Specified Account Already Exists.

Fix 1: Enable VT-X in the BIOS

It is possible to run numerous operating systems in a virtualized environment on a single server. When you disable VT, you’ll run into issues like VirtualBox not supporting 64-bit and VMware’s CPU being disabled. As a result, check sure that virtualization is activated.

  1. Restart your computer and click Delete or F2 when the starting screen shows to enter BIOS, then restart.
  2. Using the arrow keys, pick the Intel Virtualization Technology or VTx or VTd option and change it to Enabled.
  3. Press the F10 key to save the BIOS settings and exit the BIOS window. After that, your computer will reboot.

To see if “the CPU has been disabled by the guest operating system,” relaunch your virtual machine. In this manner, the “power off or reset the virtual computer” problem is resolved.

Fix 2: Mask Your CPU’s Identifier

A security function, according to some users, is to blame for the issue. This CPU may not be supported or validated by the manufacturer. If this is the case, you may be able to get around the problem by concealing the CPU ID. Using a note editor like Notepad++ is the only option because VMware Workstation doesn’t have a masking capability. In this manner:

Step 1: If you don’t already have one, click here to get one. For this example, we’ll use Notepad++.

Step 2: Once you’ve opened the note editor, you’ll need to open your VMware Workstation and change the ISO image state to OFF.

Step 3: Click on Edit virtual machine settings after selecting your guest virtual machine.

Step 4: In the Hardware tab, pick the Hard Disk (SCSI) device and copy the Disk file’s precise path from the right pane.

Step 5: Locate the Disk file path by pressing Win + E on your keyboard. Now, locate a.vmx file, right-click it, and select Edit with Notepad++ from the context menu.

Step 3: Using Notepad++, open the vmx file and type the following code in the bottom-right hand corner. Close Notepad++ by pressing Ctrl + S to save your changes.

“0000:0000:0000:0000:0001:0000:0110;1010:0101” is the cpuid.1 eax value.

Once the virtual machine has been started, you may see if “The CPU has been disabled by the guest operating system” is true. “Reset the virtual machine to its factory settings.” There was a mistake that was corrected.

Fix 3: A New Virtual Machine Should be Created.

A faulty virtual machine may be the source of the VMware the CPU has been deactivated by the guest operating system problem. A fresh guest machine must be created in this situation. However, you will lose any data on the guest virtual computer as a result of this procedure. As a result, you should always have a backup prepared. You can use this article to learn how to construct a new virtual machine.

Fix 4: Upgrade VMware WorkStation Version 4

The CPU has been deactivated by the guest operating system.” if you still get this message. After trying the following options, you may want to consider upgrading your VMware Workstation to the latest version. VMware Workstation Pro 15.5 has been shown to be able to correct the mistake by some users. It’s definitely worth a shot.

Recent on WEF

Popular on WEF