Fixed: Failed to query SMC value from the host (VERR_INVALID_HANDLE)

If you got “Failed to query SMC value from the host (VERR_INVALID_HANDLE)” while any macOS on your VirtualBox then here is how you are going to fix the error.

This error message indicates an issue with the communication between the virtual machine and the host system, particularly related to querying values from the System Management Controller (SMC) interface.

The error typically appears when you install macOS Sonoma, macOS Ventura, macOS Monterey on Windows 11, and more. While the error might look intimidating, you can fix the issue easily.


Failed to query SMC value from the host (VERR_INVALID_HANDLE)
Failed to query SMC value from the host (VERR_INVALID_HANDLE)

There are three simple ways to fix Failed to query SMC value from the host (VERR_INVALID_HANDLE) error. But before we begin check these simple tricks that can fix the issue.

  • Update VirtualBox: Ensure that you are using the latest version of Oracle VirtualBox. Newer versions often come with bug fixes and improvements that might resolve compatibility issues.
  • Update Guest Additions: If you are using a guest operating system inside the virtual machine, make sure that you have installed the corresponding Guest Additions for that operating system. Guest Additions are drivers and utilities that enhance the integration between the guest and host systems.
  • Disable Hypervisor Features: If you are using other virtualization technologies or hypervisors, such as Windows Hyper-V, they might conflict with VirtualBox. Disable or turn off these features to see if it resolves the issue.
  • Reboot Host Machine: Sometimes, a simple reboot of the host machine can resolve communication issues between the host and the guest.
  • Check Hardware Virtualization: Ensure that hardware virtualization is enabled in your host system’s BIOS/UEFI settings. This is usually called Intel VT-x or AMD-V. Enabling this feature can improve virtualization performance and compatibility.

Now that you have checked these, you can check the methods given to fix the error.

Method 1: Check Virtual Machine Settings

The first thing that you are going to do is to enable “Enable EFI (special OSes only)” in VirtualBox settings. Here is how to do it:

   – Open the VirtualBox manager.

   – Select the virtual machine experiencing the issue.

   – Go to Settings > System > Motherboard and check if the Enable EFI (special OSes only) option is selected. Try toggling this option to see if it makes a difference.

Tip: Try to change your CPU Processors to 1 and check your VM. This is for users who have selected 2 or more processors for their VM.

This is a simple bug in VirtualBox that can cause the error. If this method fixed the issue, then well and good else you will apply the next method.

Method 2: Use commands on CMD

For the second method, you will close your VirtualBox and run CMD as administrator. Remember you will need admin privileges to apply the changes.

Open CMD and use the commands given:

VBoxManage.exe setextradata “VM name”
“VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC” 0

Now open VirtualBox and start your VM. If the error still persists then you will check the next method.

Method 3: Reinstall VirtualBox

If none of the above methods worked then you might consider reinstalling VirtualBox. Ensure that you uninstall the existing version before installing the new one.

If the problem persists then you are recommended to try earlier versions of VirtualBox. There might be an issue with the new version of VirtualBox that needs to be fixed. Until the new update is brought by the officials, you are recommended to use earlier versions of VirtualBox.

Related: How to Fix “VT-x is not available (VERR_VMX_NO_VMX)”?

Related: Fix VirtualBox 0x80004005

You may also like...

Leave a Reply

Your email address will not be published. Required fields are marked *