Is anyone else having problems with VB v6.1.32 booting up 64-bit Windows in 64-bit W10?

[fth0]

The Runtime Information continues to report the VM Execution Engine as Native API. Is there a way to force it onto the Hyper-V engine?

You're misinterpreting the information: "Native API" means Hyper-V, and you'd see "VT-x/AMD-V" otherwise.

Native API means the hypervisor API native to the host OS (e.g. Hyper-V on Windows, Hypervisor Framework on macOS). VirtualBox 6.1.x only uses the native API on Windows, and only if forced to do so.

[ant]

I saw v6.1.34 was released so I tried it even though I didn't see anything about this issue being fixed in its https://www.virtualbox.org/wiki/Changelog-6.1#v34. So, I upgraded, retested, and saw the same issue. I assume it wasn't fixed. I attached its log. So, back to v6.1.30 again!

[postnobills]

Saw that 6.1.34 is out (side note: the auto updater is still offering me 6.1.32 a month after release...) and yeah it's still not resolved. Case in point: Do a clean shutdown of W10 VM, take a snapshot, and start the VM using version 6.1.24: 21 seconds to boot to the login screen. Revert to the snapshot, upgrade to 6.1.34, and perform the exact same boot: almost 12 minutes to get to the login screen, and the VM is not responsive enough to even be able to shut it down properly at that point. Revert to 6.1.24 and everything goes back the way it was. Log is attached.

[fth0]

Saw that 6.1.34 is out (side note: the auto updater is still offering me 6.1.32 a month after release...)

FWIW, VirtualBox 6.1.34 was released on 2022-04-19, which was about two days ago. Did you use a time machine?

[postnobills]

Saw that 6.1.34 is out (side note: the auto updater is still offering me 6.1.32 a month after release...)

FWIW, VirtualBox 6.1.34 was released on 2022-04-19, which was about two days ago. Did you use a time machine?

Well the changelog says

VirtualBox 6.1.34 (released March 22 2022)

so that is the date I was going by

[mpack]

I am going to lock this topic, because the title is unacceptable vague ("problems") which encourages "me too" posts about a wide range of issues.

There is no general problem booting 64bit Windows guests, and referring to a 64bit hosts is redundant, since VirtualBox v6 will not run on any other kind. Problems with Hyper-v compatibility are well discussed elsewhere.