Hi, I've a strange issue with my Surface Laptop Studio with 24H2 and all Hyper-V related stuff. When I install Hyper-V, Windows Sandbox and WSL (WSA working with no issues), my PC is a little bit slowed down. If I don't run any of the previously mentioned components, there aren't any other issue. WHEN I RUN ONE OF THE HYPER-V COMPONENT: The startup (not the boot) of the virtual machine is extremely slow, with about 5 minutes of delay before start to booting; I noticed that seems the VM waits for the creation of the vEthernet interface and its auto-configuration. During this wait I've also noticed that every RDP connection to other PC will fail. When I shutdown the host machine (with fast startup enabled), the PC seems off, but the fan is still active (for about 5 minutes) and I can't turn on the PC until it's completely off. When I turn on the PC, after Windows Hello Facial Recognition, I have about a 50% chance that there is no Desktop for about 5 minutes, only a dark grey screen. I can press Ctrl+Shift+Esc for the Task Manager and see that Explorer is already running. Instead, if I reboot the PC I have to wait about 5 minutes of the animation post-logoff. When the PC start again, it's only a little bit slowed down. If I disable all the Hyper-V stuff (like in this moment) the PC is perfect. With 23H2 everything was working perfectly. After the update I noticed all this issues. So I clean installed 24H2, but nothing changes. In the Desktop PC in the office with 24H2 and almost the same configuration, there is no issue with Hyper-V stuff. Any idea?
I thought about it too, but even after disabling the flags in Windows Defender, the issues persist...
Hello, Just asking, did you try with just Hyper-V? Disable Windows Sandbox / WSL. Just install Hyper-V with a clean installation of Win11 24H2 and in case you have multiple VMs, ensure to provide enough gap, like 15/20sec for each VMs start up on boot. Secondly, which type of vEthernet are you using for that virtual switch? Thanks.
I've also tried with single components enabled, but the issue is always still there... the vEthernet is the default virtual switch.
On the Surface, the virtualization can't be disabled by the BIOS. Thanks, I'll check this during the weekend. In the meantime, I noticed that if I plug my 10Gbit Ethernet Thunderbolt NIC before power-on the laptop, I experience the 5 minutes of dark grey screen (for now Hyper-V and its other related stuff are not installed). If I plug the Thunderbolt NIC after the Desktop is available, I've no issue, but Windows Security shows only a blank page for about 5 minutes... I'm starting to think it's a firmware issue or something like that...
Make sure you have enough CPU cores and also, Memory RAM is most key are hungry ram! Just word advice.. ATGPUD2003
I can confirm that the problem is not directly related to Hyper-V, but to whenever the system detects a new NIC at logon, whether physical or virtual.
I found the issue. The presence of the Marvell AQC113 driver triggers everything. If I uninstall my Thunderbolt 10GbE NIC, all the issues are gone. I tried all the versions of the driver, and the issue persists with all of them. I hope that Microsoft or Marvell fixes this issue.