The solutions presented below require a little knowledge of working with virtual machines or tinkering with system settings.

How do I fix the CPU has been disabled error?

1. Reset the virtual machine

Not to disregard the system-recommended solution, we’ll be adopting this method as the first solution in this tutorial. The CPU has been disabled by the guest operating system error-message is aptly accompanied by a system-recommended solution, which reads Power off or reset the virtual machine. Therefore, as the first line of action, try and power off or reset the workstation, and check if it resolves the issue. If this fails, you can try and run the next troubleshooting technique to fix the error.

2. Enable virtualization in BIOS

Once this is done, check if the error is fixed in your virtual machine workstation. If it remains unfixed, there is probably another factor(s) in play, in which case, you can try the next solution.

3. Mask CPU ID

Relaunch your VM workstation and check if the issue is resolved. If not, you can try the next and final solution. In such a case, the error might be associated with a security function, which disables an unverified/unsupported processor. This is common where the virtual engines are not compatible with each other, especially in their build (architecture). When this happens, with a disabled processor, the ISO image (of the VM) will not be recognized by the system. masking the CPU identification tag can bypass this irregularity/inadequacy. Unfortunately, the VMware workstation lacks the graphical interface to run the masking procedure. Nevertheless, reconfiguring the virtual machine‘s code file in a text editor, as shown above, might work.

4. Create another guest engine in VMware Workstation

If, after trying the four techniques in this tutorial, the issue remains unsolved, you can as well consider third-party software that will help you out. Hence, to create a virtual machine easily without spending too much time and effort, simply choose a suitable tool from the best virtual machines for Windows 10. We hope that you managed to fix the error, though. Tell us which solution worked for you.

Name * Email * Commenting as . Not you? Save information for future comments
Comment

Δ