When using ctrlX Works I find my virtual ctrlX runs extremely slow with errors. Before it runned smoothless.
Checking ctrlX works settings I find the following messages.
Trying to install the HAXM again failed (this option is mentioned in the error message). System requirements are not okay, but that seems strange to me while it worked faultless before. I did not change anything.
In the installation file of HAXM there is a check tool. It tells me VMX is not supported. But it should be supported as in the example left.
My PC is managed by the organisation and sometimes I get updates. Maybe this has something to do with it.
What could be the problem here?
Solved! Go to Solution.
I found that the Virtualisation Based Security caused the problem. It did not allow me to re-install HAXM.
With disabling the VBS my problem was eliminated directly !
To check the status of VBS-
Go to Search → System information → Virtualization based security ( Status should not be running )
If VBS is running and you want to stop it.
Step 1 - Open Windows Powershell as administrator
NOTE: You need (temporary) admin rights.
Execute the below command in cmd.exe command prompt, PowerShell, or using the Run feature.
powershell Start-Process powershell -Verb runAs
This opens the powershell console as an administrator.
Step 2 - Download and run the script using Windows Powershell
Download the disableVBS-file (attachement) and save it in file explorer
Browse to the location you stored the disableVBS-file in File Explorer and copy the path from the file into the Administrator: Windows PowerShell opened in the first step.
Press Enter to continue.
if you see output :
To Verify VBS is running or not ,
If the first option is not working follow the option2
On My PC I had to use option 2
I found the root cause of the problem. Looking at my Network settings I saw the Hyper-V switch enabled every restart.
Instead of stopping the Hyper-V manually I wanted to delete the Hyper-V permanently.
While my computer is managed by the organisation I had to arrange that over the central IT-portal
Problem was permanently solved