LHC@home

As title, the log file keeps saying "SCheduler request completed: got 0 tasks"

Virtualisation is enabled and Memory integrity is disabled, running latest versions of Boinc and Virtualbox.

Any ideas what I missed?

On your Windows machine? Don't select "run native".

As title, the log file keeps saying "SCheduler request completed: got 0 tasks"

Virtualisation is enabled and Memory integrity is disabled, running latest versions of Boinc and Virtualbox.

Any ideas what I missed?

https://lhcathome.cern.ch/lhcathome/show_host_detail.php?hostid=10664526
Your computer details report:
Virtualbox (7.1.4) installed, CPU does not have hardware virtualization support

This points out you need to revise your local setup.
Please check the forum for all steps that are required, it has been explained many times.

Windows and the bios is reporting it as enabled, can you link me to the steps please?

Still not managed to sort this.

IOMMU is enabled in the bios and Windows reports Virtualisation is enabled.
Core Isolation is off
Hyper V is disabled
Virtual Machine Platform is disabled

What have I missed?

win 11 24h2?

---

Yes that Windows 11 Update last december 24H2 started this problem and just before that Update Windows 11 had no problem running VB
Instead of them doing something to change it they probably want us to wait and change to Windows 12 around the same day they stop supporting Windows 10 later this year.

The problem exists with Windows 11 24h2/Windows 12/Win13....Windows uses Hiper V as its own virtualizer.....other than this you have 2 paths: use Docker/WSL or combine both. Logic tells you to use Windows' own virtualization system, Hiper V.
With these last 2 paths, WSL/Docker, you may end up blocked later on; sooner or later you will be blocked from using any virtualization outside of Hyper V...

---

This was the one I needed.

bcdedit /set hypervisorlaunchtype off

The other reg tweeks did not work anymore.

uncheck Hyper-V, Windows Hypervisor Platform AND Virtual Machine Platform.
Control it if BIOS AMD-V or VT-X is on after reboot!

That only works with Windows 10 and Windows 11 before the 24H2 update

That was what new users always had to do but that won't work now and I have been doing this since 2011

I tried that 20 times at least and many other things you can google around for and those basic settings make no difference

It will say Virtualbox is on in the task manager but here it will say .....

Virtualization Virtualbox (7.1.6) installed, CPU does not have hardware virtualization support

I have 3 newer pc's in the last 5 months but the first one that does work had the VB here running before 24H2 and the other 2 pc's I added in January will not work with all of those settings and all of the security turned off in windows 11 Privacy & Security settings

So I use the 28 core and 24 core pc's to do work at other projects

Now Windows 11 with 24h2 has built-in security at the UEFI TPM level, you may need to modify the UEFI BIOS. It doesn't matter if you modify the software, the UEFI BIOS will continue to activate parameters that you disable via software. So the attack can only be physical.

This has an easier path, there you have your own operating system which is Alma Linux... you could make a slightly modified version that has VirtualBox and Boinc already installed within Alma Linux itself with the installer.

For these tasks, the user only needs to install Alma Linux. The rest of the task is already done with VirtualBox and Boinc installed, without having to type code. Or, option 2, you make a version where you have a functional repository of icons that automatically download VirtualBox and Boinc in the Windows style.Push icon.....install...

---

So are VM units just not runable on Windows anymore?

I have Virtualisation enabled, confirmed via task manager
IOMMU is enabled
Everything Hyper V is disabled and bcdedit /set hypervisorlaunchtype off run
LeoMoon shows AMD-v supported and enabled
DEP enabled
SLAT disabled
VM Monitor Mode Extensions disabled

Disable AMD-v

I have an AMD system running Win 11 24H2 https://lhcathome.cern.ch/lhcathome/show_host_detail.php?hostid=10875081 that has been running LHC for a while now, so it is possible.

---

SLAT disabled
VM Monitor Mode Extensions disabled

Looks like a problem.

Is WSL disabled?
Are you able to create a local VM in VirtualBox and install and run a Linux distribution in it?

WSL and all Hyper V components are disabled, not sure how you enable SLAT and VM Monitor Mode Extrensions?
Just tried installing Ubuntu in a Vbox VM and it worked fine.

So, VirtualBox is healthy. That reduces the scope of the problem we are trying to solve.

In System Information (msinfo32) it must show this in the System Summary:

Virtualization-based security Not enabled

and

Hyper-V - VM Monitor Mode Extensions Yes
Hyper-V - Second Level Address Translation Extensions Yes
Hyper-V - Virtualization Enabled in Firmware Yes

From what is reported by LeoMoon is seems some of those that need to be enabled are not enabled.

Perhaps the system needs to be started once with Hyper-V enabled to set some necessary registry entries, then again with Hyper-V disabled to allow LHC@home to run its VMs. In that case it may be necessary to run 'bcdedit /set hypervisorlaunchtype off' again after re-unchecking all the Hyper-V related stuff in 'Turn Windows features off and on'. Regardless of how it is done, SLAT and VM Monitor Mode Extensions should be enabled.

If there is a separate entry for RVI (rapid virtualization indexing) in BIOS, it must be enabled along with SVM/AMD-V

Ok its showing Virtualisation based security is running, core isolation is off though so I thought this was disabled, ill look into this, how safe is it on a general purpose Windows 11 machine to have this off?

For Hyper V it just says "A Hypervisor has been detected. Features required for Hyper-V will not be displayed"

There are security implications of disabling Virtualization-based security. Unless you are a high-value target not behind a firewall my personal opinion is that it isn't a big deal.

I asked Copilot about the Hypervisor stuff:

When msinfo32 reports “A hypervisor has been detected. Features required for Hyper-V will not be displayed,” it means a hypervisor is actively running on your system, which masks certain hardware virtualization features. This is expected behavior when virtualization is in use.

Here are common causes:

* Hyper-V Is Already Running
If Hyper-V is installed and active, it becomes the system hypervisor.

This message simply confirms that Hyper-V is functioning.

* Virtualization-Based Security (VBS)
Features like Memory Integrity, Core Isolation, or Credential Guard use a lightweight hypervisor.

These can trigger the message even if Hyper-V isn’t explicitly installed.

* Other Hypervisors Installed
VMware Workstation, VirtualBox, or WSL2 (Windows Subsystem for Linux) may install components that activate a hypervisor.

Even if Hyper-V is disabled, these can still cause the message to appear2.

* Running Inside a Virtual Machine
If your Windows system is itself a guest VM (e.g., on VMware or Hyper-V), it will detect the host hypervisor.

Nested virtualization setups often show this message.

It looks like there is quite a lot to dig through, but VBS seems like the most likely culprit. There may be more types of VBS than Copilot mentioned. This isn't an area where I have relevant experience. My Win 11 24H2 system doesn't generate that message even though VirtualBox is actively running LHC@home tasks.