LHC@home

As the title says Windows 11 Pro got a feature update this morning and now all Atlas tasks are failing after 20 seconds. This applies to new tasks and those that I paused for the update and are restarted after the update. This is a AMD Ryzen 9 7950X system with 64 GB memory and a RTX 4070 Ti Super. Boinc is 8.0.2 and VirtualBox is 7.0.6 with extension pack.

So far I have checked:
- Virtualization support is enabled
- Hyper-V is disabled
- Memory protection is Off
- I added the WindowsHello/Enable = 0 registry key (this was missing originally)

Here's a link to a failed task: https://lhcathome.cern.ch/lhcathome/result.php?resultid=419739088 Only thing I can find there is:

Command:
VBoxManage -q startvm "boinc_4a2bfde5750eaf48" --type headless
Output:
VBoxManage.exe: error: The virtual machine 'boinc_4a2bfde5750eaf48' has terminated unexpectedly during startup with exit code 1 (0x1).  More details may be available in 'C:\ProgramData\BOINC\slots\1\boinc_4a2bfde5750eaf48\Logs\VBoxHardening.log'
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component MachineWrap, interface IMachine
Waiting for VM "boinc_4a2bfde5750eaf48" to power on...

So what I should look next?
[edit] The VirtualBox media manager doesn't have any yellow triangles on vdi-files.

---

The message suggests to look through 'VBoxHardening.log'.
Hence, you should upgrade to the most recent VirtualBox version and start a fresh task (not a suspended one!).

If the fresh task fails with the same error, look through it's 'VBoxHardening.log'.
If you need help for this you should post it at the VirtualBox forum.

bcdedit.exe /set nointegritychecks on
after installing the required drivers
bcdedit.exe /set nointegritychecks off

This is from KI Copilot from Microsoft.

The message suggests to look through 'VBoxHardening.log'.
Hence, you should upgrade to the most recent VirtualBox version and start a fresh task (not a suspended one!).

If the fresh task fails with the same error, look through it's 'VBoxHardening.log'.
If you need help for this you should post it at the VirtualBox forum.

Installing the new version seems to do the trick. At least the tasks have started OK. Now I'll wait to see if they will process some events.

By the way, how do you catch up the log files? The 21 second was time Boinc saw them running but actually they errored already in 10 seconds and then the logs were already gone.

---

bcdedit.exe /set nointegritychecks on
after installing the required drivers
bcdedit.exe /set nointegritychecks off

This is from KI Copilot from Microsoft.

The problem seems solved when I installed the latest version of VirtualBox. But I am just curious, how should this advice have helped?

---

By the way, how do you catch up the log files? The 21 second was time Boinc saw them running but actually they errored already in 10 seconds and then the logs were already gone.

On Linux
Before you start a task open a separate console where you run something like
tail -F expected_interesting_log > safe_location

On Windows
Try something like this in PowerShell (not tested, check the available options)
Get-Content expected_interesting_log -Tail 10 -Wait

OK, thank you.

---

The message suggests to look through 'VBoxHardening.log'.
Hence, you should upgrade to the most recent VirtualBox version and start a fresh task (not a suspended one!).

If the fresh task fails with the same error, look through it's 'VBoxHardening.log'.
If you need help for this you should post it at the VirtualBox forum.

Installing the new version seems to do the trick. At least the tasks have started OK. Now I'll wait to see if they will process some events.

By the way, how do you catch up the log files? The 21 second was time Boinc saw them running but actually they errored already in 10 seconds and then the logs were already gone.

Harry, which version is the "new VBox version" you're mentioning above. Your recent ATLAS tasks show 5.2.44 which is a pretty old one,

The reason why I am asking is that I bought a new Windows11 host recently and never got ATLAS to run on it. My VB version is 7.1.4 (which was the newest one at the date of installation).

Harry, which version is the "new VBox version" you're mentioning above. Your recent ATLAS tasks show 5.2.44 which is a pretty old one,

The reason why I am asking is that I bought a new Windows11 host recently and never got ATLAS to run on it. My VB version is 7.1.4 (which was the newest one at the date of installation).

The 5.2.44 is on my WIndows 10 machine and it is working fine. The Win11 machine now has version 7.1.6

---

The 5.2.44 is on my WIndows 10 machine and it is working fine. The Win11 machine now has version 7.1.6

Thanks, Harry. So I caught the wrong host :-(
What I might do then is to upgrade from 7.1.4 to 7.1.6, maybe it helps. I'll tell you

...What I might do then is to upgrade from 7.1.4 to 7.1.6, maybe it helps. I'll tell you

I upgraded, and now is seems to work :-) So, my Win11 is able to crunch also Atlas (besides CMS and Theory which have not been a problem before anyway).

...What I might do then is to upgrade from 7.1.4 to 7.1.6, maybe it helps. I'll tell you

I upgraded, and now is seems to work :-) So, my Win11 is able to crunch also Atlas (besides CMS and Theory which have not been a problem before anyway).

Good!

---