unable to install RHEL8/CentOS8 guests on Windows 10 Intel laptop

[GCR]

I have verified I can install Ubuntu 20.04, both server and desktop, in VirtualBox, on this Intel laptop. I have verified my RHEL8 and CentOS8 ISOs on an AMD Windows 10 laptop, and they install inside VirtualBox guests fine. But on this Intel laptop, they seem to be hanging. none of the seven Hyper-V boxes is checked in "Turn Windows features on or off". I have rebooted several times. I have tried both docked and undocked. it always seems to end up hanging, and I get "...TM: Giving up catch-up attempt at a..." over and over.
I have attached the log output from my most recent RHEL8 attempt. I'd love some more ideas of things I can try.

[scottgus1]

none of the seven Hyper-V boxes is checked in "Turn Windows features on or off"

Something is still using Hyper-V, though. See HMR3Init: Attempting fall back to NEM (Hyper-V is active)

[GCR]

none of the seven Hyper-V boxes is checked in "Turn Windows features on or off"

Something is still using Hyper-V, though. See HMR3Init: Attempting fall back to NEM (Hyper-V is active)

okay, in bcdedit hypervisorlaunchtype was indeed set to auto. I ran the command to set it to off, and shutdown. after powering on and booting back up, it is now set to "Off". but my problem persists. I had not noticed the green turtle icon previously, but it was there, and still is.

[scottgus1]

I have tried both docked and undocked

If this means Docker, then that uses Hyper-V. Otherwise, I have no other ideas. There must be something re-enabling Hyper-V.

[GCR]

I have tried both docked and undocked

If this means Docker, then that uses Hyper-V. Otherwise, I have no other ideas. There must be something re-enabling Hyper-V.

Ha, no, I meant connected to a USB-C docking station. when docked, I have a second GPU.
thanks for the help, I appreciate it.

[fth0]

Did you shut down Windows with the console command? If not, did you press the shift key when selecting Start Menu > Power > Shut down? Otherwise, you maybe have been using Windows 10 Fast Startup, circumventing the hypervisorlaunchtype setting.

[GCR]

Did you shut down Windows with the console command? If not, did you press the shift key when selecting Start Menu > Power > Shut down? Otherwise, you maybe have been using Windows 10 Fast Startup, circumventing the hypervisorlaunchtype setting.

don't know if that was it or not, but it appears to have worked! my virtualbox instance is now running normally. Thank you.
it's funny that I did not have to do any of this on my AMD laptop. it all just worked. when I check hyper-V there, it's set to auto.

[scottgus1]

don't know if that was it or not, but it appears to have worked!

Great! Glad you're up and running. The "shutdown -r -t 2' command or the Shift-Start-Menu-Shut Down click both tell Windows to forget about Fast Startup and do a full complete oldoschool shutdown, which allows the bcdedit command to take effect.

Re your laptop, it could be Windows just is not using anything related to Hyper-V. Neither of my Windows 10 hosts have needed the bcdedit command either, and both run non-Hyper-V-affected VMs just fine.