Questions and Answers :
Windows :
still can't get LHC@home to run
Message board moderation
| Author | Message |
|---|---|
|
Send message Joined: 11 Sep 05 Posts: 64 Credit: 4,990,691 RAC: 14,997 |
Ive been working on this for months and I can't get LHC@home to run at all. I have no idea what to do now. I am on the latest verison of BOINC I do have Podman isntalled and VirtralBox. Im on windows 11 but it jsut will not run. Ive formatted the computer a few times and jsut isntalled drivers BOINC virtralbox and Podman and still can't get LHC@home to run. what do you all even do to get this running? This is the msot compled project on BOINC and it will not work. system specs are Windows 11 Enterprise, Intel 14900KS, RTX5070. This is so hard adn depressing and frustering and there is no real guide or real help. why did you all make this so depressing and frusterting? and I been trying to reach out for help for months and it goes no where but in circles. |
|
Send message Joined: 4 Mar 11 Posts: 41 Credit: 4,010,798 RAC: 0 |
While you have installed Virtual Box you do not appear to have enabled CPU virtualisation in the BIOS of either of your computers. |
|
Send message Joined: 11 Sep 05 Posts: 64 Credit: 4,990,691 RAC: 14,997 |
Yes, of course it's enabled also not that you said it but Hyperviser is disabled. It jsut wont work and I don't know why |
|
Send message Joined: 11 Sep 05 Posts: 64 Credit: 4,990,691 RAC: 14,997 |
I don't know what else to do. the motherboard is a z890 proart, the BIOS is up to date, and yes virtralzation is enabled in the BIOS. |
|
Send message Joined: 14 Jan 10 Posts: 1481 Credit: 9,977,837 RAC: 1,022 |
Yes, of course it's enabled also not that you said it but Hyperviser is disabled. It jsut wont work and I don't know whyFrom your machine: 2025-12-14 00:07:28 (19656): Guest Log: Successfully finished the ATLAS job! |
|
Send message Joined: 24 Jan 06 Posts: 8 Credit: 9,573,670 RAC: 2,314 |
When I first moved to Windows 11 VirtualBox reported that virtualisation wasn't enabled. Solution for me was to disable "Memory integrity", which also disables the dependency "Kernel-mode Hardware-enforced Stack Protection", in Windows Security. Prior to the upgrade, while running Windows 10 on the same PC, "Memory integrity" was disabled and couldn't be enabled but as part of the upgrade process it was enabled and broke VirtualBox. |
©2026 CERN