Hi everyone,
Sorry completely new to this.
I'm trying to run windows 10 virtually on windows 11 and keep getting a Guru Meditation critical error shown below. It wont let up load the full log file but this is the error code.
ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={6ac83d89-6ee7-4e33-8ae6-b257b2e81be8} aComponent={ConsoleWrap} aText={The VBoxGuestPropSvc service call failed with the error VERR_HGCM_SERVICE_NOT_FOUND}, preserve=false aResultDetail=-2900
Its boots to ~20% before giving the error message.
Does anyone know a fix for this error??
Thanks for your help!
Guru Meditation Critical Error (VERR_HGCM_SERVICE_NOT_FOUND)
-
- Posts: 2
- Joined: 29. May 2023, 15:11
-
- Site Moderator
- Posts: 38813
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: Guru Meditation Critical Error (VERR_HGCM_SERVICE_NOT_FOUND)
Please provide a VM log file. Make sure the VM is fully shut down, then right click it in the manager UI. Select "Show Log" and save "VBox.log" (no other file) to a zip file. Attach the zip here.
-
- Posts: 2
- Joined: 29. May 2023, 15:11
Re: Guru Meditation Critical Error (VERR_HGCM_SERVICE_NOT_FOUND)
Thanks for the help, I have attached it.
- Attachments
-
- VBox.log.zip
- (58.21 KiB) Downloaded 10 times
-
- Volunteer
- Posts: 5123
- Joined: 14. Feb 2019, 03:06
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Linux, Windows 10, ...
- Location: Germany
Re: Guru Meditation Critical Error (VERR_HGCM_SERVICE_NOT_FOUND)
The VERR_HGCM_SERVICE_NOT_FOUND error message is a red herring that you can most probably ignore.
The real issue is that some 3rd-party software (*) running on your host is using the hardware virtualization (VT-x) of your Intel CPU, and VirtualBox cannot use VT-x at the same time. Unfortunately, VirtualBox doesn't recognize this situation, which leads to the Guru Meditation -37 (VERR_NOT_SUPPORTED).
(*) FWIW, some so-called security software is known to use VT-x and provides a configuration item to disable that.
The real issue is that some 3rd-party software (*) running on your host is using the hardware virtualization (VT-x) of your Intel CPU, and VirtualBox cannot use VT-x at the same time. Unfortunately, VirtualBox doesn't recognize this situation, which leads to the Guru Meditation -37 (VERR_NOT_SUPPORTED).
(*) FWIW, some so-called security software is known to use VT-x and provides a configuration item to disable that.