virtualbox.org

Since the upgrade from windows 1123H2 to 24H2 I have a big problem with the hyper-v in windows.
AFTER this upgrade I got the famous turtle.
The VMs started very slowly or not at all.
In the log file I saw a "note" with the remark:
"another virtualzer was active and therefore Oracle virtualbox could not function properly".
What have I done so far.
Finished the entire howto here on the forum.
Including all registry references removed or set to 0.
Safe boot in the bios disabled as well as all references to the hyper-v in the bios changed to not active.
Also the kernel isolation disabled as well as the kernel access and the control on driver program everything is disabled.
The system information continues to define that a hypervisor is active.
I can't get it to work.
In desperation I installed 23H2 windows on the system but also in this environment the famous turtle.
Downgrading to 7.0. 20 virtualbox also did not help the turtle again.
It must have been 2 years ago that I also had this problem with the w22H2 edition of windows.
I then finished the entire howto and lost the turtle.
I also followed procedures that the copilot coughed up but here too no result.
The computers on which I run virtualbox are a trio (2 desktops and 1 laptop) from HP.
Each of these computers runs 24H2 PRO.
What am I doing wrong?
Do others on this forum have this problem?
Please respond.

You need to disable virtualization based security.
Settings->device security->core isolation details->Memory integrity << disable
Reboot

https://www.microsoft.com/en-us/downloa ... x?id=53337, download the tool and from an elevated command prompt, execute it

DG_Readiness_Tool_v3.6.ps1 -Disable (correct the version number based on the file that you download)

Reboot

If your BIOS is not enabled with SecureBoot this is more than enough to address the current problems.

This is not understandable to me.
How do I do this via the terminal?

I am quite good with virtualbox but less with terminal stuff.

The software as offered cannot be used by me due to a lack of knowledge.
I do know that the kernel isolation is turned off and the device card has also been turned off via the template.
Plus (I'll just repeat) the total steps in the howto.
However, a hyperverse remains in the background that I can't get rid of and therefore has such an influence that I CANNOT run virtual box.
In the 10 years that I have been using virtual box, I have never experienced anything like this!

Today I performed a clean installation and then installed virtual box.
I have performed ALL possible steps mentioned in the howto and yet the green turtle remains visible when I start a VM.
So it could be that there is something in virtual box that does not communicate with windows or the other way around, no idea.
Another short summary of the steps followed.
1. All steps in the Howto, the bcdedit and the DISM command
2. Log out and turn off the computer for at least 2 minutes.
3. After booting, the systemguard and device guard were disabled
4. Also closed the device card via management templates.
5. Also disabled the registry references to the device card.
6. In the bios, secure boot disabled
7. The kernel isolation disabled, i.e. the memory integrity + security for local security authorities and finally the block list for microsoft vulnerable drivers
8. There were no references to hyper-v software when enabling and disabling windows components.
9. Finally, run the bcdedit /set vsmlaunchtype Off command.
10. Turned the computer off and on again after 2 minutes.
11. Checking via bcedit command produces the following image

hypervisorlaunchtype Off
vsmlaunchtype Off
The last entry of this command tells you that the hyper is off and the vsm is off(no idea.....)

I started up virtualbox again, saw the turtle in full glory again and started a vm.
However, the performance was okay so I'll leave it like this for now.
Conclusion
It is not a BIOS problem but a software problem of windows or virtual box.
I stop.......coffee......eat......compu OFF......

marcthin wrote: ↑6. Oct 2024, 12:56 This is not understandable to me.
How do I do this via the terminal?

I am quite good with virtualbox but less with terminal stuff.

The software as offered cannot be used by me due to a lack of knowledge.
I do know that the kernel isolation is turned off and the device card has also been turned off via the template.
Plus (I'll just repeat) the total steps in the howto.
However, a hyperverse remains in the background that I can't get rid of and therefore has such an influence that I CANNOT run virtual box.
In the 10 years that I have been using virtual box, I have never experienced anything like this!

Please see whether you can follow the below article. I had to hurry to post it & hope the given instructions are easy to follow

simpleoracle.com/2024/10/09/how-to-disable-windows-virtualization-device-based-security-vbs/

It is very very frustrating but I have done EVERYTHING in the link you gave.
The green turtle remains.
Also the commands given in the docs do NOT work, ALL error messages.
I think 24H2 uses different sets of commands.
The credential card is disabled via the gpedit.msc app.
Somehow the virtulasor is embedded deep in the software in a NEW way.
I think I have exhausted all options and will have to settle for a virtual box that is a bit less fast.......unfortunately....thanks anyway for your time.

I had the same problem with WIN 11 24H2.
The only thing that worked for me and what finally completely disabled VBS was the DG Readiness Tool (mentioned above).

I did exactly what is advised.
I only get errors in powershel that the file is not recognized.
What am I doing wrong????

I have admin rights.

try .\Dg_readiness.ps1

The current folder is probably not in your search path

.\ I try that.....errors..i reale don't understand. Use the cd and ls function.
The path is right...so what next?

PS C:\Users\mmcva\Downloads\dgreadiness_v3.6> .\DG_Readiness_Tool_v3.6.ps1 -Disable
.\DG_Readiness_Tool_v3.6.ps1 : File C:\Users\mmcva\Downloads\dgreadiness_v3.6\DG_Readiness_Tool_v3.6.ps1 cannot be loaded because running script
s is disabled on this system. For more information, see about_Execution_Policies at https:/go.microsoft.com/fwlink/?LinkID=135170.
At line:1 char:1
+ .\DG_Readiness_Tool_v3.6.ps1 -Disable
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : SecurityError: (:) [], PSSecurityException
+ FullyQualifiedErrorId : UnauthorizedAccess

Script is disabled....how the ......

JIPPPPPIIIIEEEEEE it works.
First changed the group policy for the powerchel and then the script did its job.
Then restarted the computer (sweet in my hands) a black screen appeared or if I wanted to press F3 to deactivate "the card". Restarted the computer and yes the turtle is gone.......thanks everyone for thinking along. Now my other computers!

Another point found.
Bitlocker cannot be used.
If I activate or deactivate bitlocker I can run the script again because the turtle appears again.
Very strange. If I run the script when bitlocker is active there is nothing wrong the turtle is gone.
If I deactivate bitlock then I have to run the script again because the turtle shows itself again!
Now no use bitlocker, script executed and the turtle is gone again.....

I'm not out of trouble yet.
One computer is now running fine, the other when I run the script and reboot then virtualbox is fine the big turtle is gone.
When I do a cold reboot then the turtle appears again also with a warm reboot the same the turtle is there again.
First of all I have of course gone through the entire howto again.
What else did I forget? Secure boot is disabled as well as kernel security and isolation.

I am al up to date and nothing works.....i search for oures....