klaus wrote: 3. Feb 2025, 19:08
Impossible to tell what kind of "performance issue" you're talking about. You need to give much more detail.
Typical example is build of operating system from source tree on FreeBSD guest.
Before upgrading 24H2 it was completed in about a hour.
And if I checked CPU usage of host with task manager, it was around 80%.
I don't limit CPU usage of guest at all.
After upgrading 24H2, however, build takes about 4.5 hours and CPU usage on host is at most 30%.
And it doesn't change after I take steps to disable VBS.
Yesterday another PC was forcibly upgraded to 24H2. And situation is different from previous case. Performance regression also happens but it isn't so terrible. Build of operating system from source tree on FreeBSD guest only takes about 150% time of 23H2. And the issue is completely fixed by disabling VBS. So my first case may have nothing to do with VBS.
Same problem here. It's insanely slow, like 10x slower than before, maybe even more.
However in my case, I have to point out I still have that green turtle icon. But I have tried EVERY steps mentionned in the dedicated thread, but the green turtle is still here. And according to this thread, removing it won't change much apparently...
Is there something I could do to help? provide some logs or configuration or anything? It really is annoying and considerably damage my productivity
There may be another method but what worked for me on 24H2 was using this dg-readiness tool from Microsoft. You can Google it and it should be near the top of the search results.
With Powershell navigate to the extracted zip folder and run
Set-executionpolicy unrestricted
.\dg_readiness_tool_v3.6.ps1 -disable
On reboot you will get a prompt to disable VBS and Device Guard. Hit F3 for both cases.
When I log back into Windows and start any Virtualbox VM, I no longer have the turtle and performance issue.
I'm currently on Windows 11 23H2, and I've also started noticing issues with Virtualbox (r7.1.8) cooperating with MS Hyper-V. It's becoming more and more important to leave Hyper-V enabled for security purposes on the host OS, and whatever method I had used before is no longer working. In investigating this, I saw one trick someone had suggested, which is copying the current Windows boot entry into a new one, and then setting both hypervisorlaunchtype and vsmlaunchtype to Off, and then rebooting into that boot entry whenever you want to run Virtualbox. However, some Device Security setting causes Windows to ignore these options and force Hyper-V to run.
It seems fairly clear that MS will make Hyper-V an indispensable part of Windows 11, not unlike the Internet Explorer madness of days gone by.
I have killed Hyper-V in my laptop, and it took a lot of work, with changes in several places. In spite of that, there is another issue which is a full stop: The guest window supports nothing greater now than 1024x768, and on a 2560x1600 screen, is unusable.
VirtualBox can handle much higher resolutions than 1024x768. Please create a separate thread, provide VBox.log and so on. Then we have a chance to help troubleshooting (usually Guest Additions are missing).
Yes, I know. I have used VBox for 16 years. Never had such problems before. See viewtopic.php?t=113555
I have had numerous suggestions, and have uploaded log files repeatedly. Tried Test Builds, and so on. Week after week, since the beginning of the year. I recently created https://www.virtualbox.org/ticket/22392
So I have done as much as makes any sense. Not one of the many suggestions I have received altered the reality that 1024x768 has become a limit. And on my Windows 10 machine, no such problem has ever existed. It is running VBox 7.1.8, as is my laptop.
I saw someone mention earlier that Hyper-V compatibility was being looked into fairly recently -- is there a central ticket or topic where this work can be followed?
csmccarron wrote: 24. Jan 2025, 22:04
Here is what worked for me to disable Virtualized Based Security (VBS). I am running Windows 11 24H2 OS Build 26100.2894.
Step 1
Use Group Policy Editor (gpedit.exe) to completely disable VBS
Computer Configuration > Administrative Templates > System > Device Guard > Turn On Virtualization Based Security - Set to Disable
Step 2
Open a Command Prompt using Run as Administrator and run the following commands:
1. bcdedit /set hypervisorlaunchtype off
2. bcdedit /set vsmlaunchtype Off
3. DISM /Online /Disable-Feature /FeatureName:Microsoft-Hyper-V
Step 3
Set CredentialGuard Enable DWORD bit to 0
1. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceGuard\Scenarios\CredentialGuard
"Enabled"=dword:00000000
thank you for this, that was my issue, especially step 3, somewhere about a month or 2 ago the VB guest become so slow in certain cases, but since always Fullscreen did not see the turtle.
csmccarron wrote: 24. Jan 2025, 22:04
Here is what worked for me to disable Virtualized Based Security (VBS). I am running Windows 11 24H2 OS Build 26100.2894.
Step 1
Use Group Policy Editor (gpedit.exe) to completely disable VBS
Computer Configuration > Administrative Templates > System > Device Guard > Turn On Virtualization Based Security - Set to Disable
Step 2
Open a Command Prompt using Run as Administrator and run the following commands:
1. bcdedit /set hypervisorlaunchtype off
2. bcdedit /set vsmlaunchtype Off
3. DISM /Online /Disable-Feature /FeatureName:Microsoft-Hyper-V
Step 3
Set CredentialGuard Enable DWORD bit to 0
1. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceGuard\Scenarios\CredentialGuard
"Enabled"=dword:00000000
thank you for this, that was my issue, especially step 3, somewhere about a month or 2 ago the VB guest become so slow in certain cases, but since always Fullscreen did not see the turtle.