virtualbox.org

Hi everyone! I am getting to get desperate. I've got a new Win 10 Pro machine and none of my Windows 7 VMs do work, neither can I install Win 7 in a fresh VM. I googled, reinstalled VB, deactivated the AV (G Data), switched all kinds of settings within the VM (acceleration, hypervisor, chipset, with and without usb) and they all freeze at a certain point. I also tried it with a different Windows 7 ISO (incl. an md5 check). The VMs when booting are draining some CPU power, but nothing happens even after hours.
I am using Virtualbox 6.1.16 r140961. The old VMs worked perfectly on the old Windows 7 pro host and all my other Linux VMs work absolutely fine, btw.
VB is my loyal companion for many years now, but I never got too deep into the internal workings, which is why I attach the log file of an already installed machine that I've tried to boot up.
Does anyone know anything, maybe about something that has to be changed on Windows 10?

SOLVED... sorta... The different thing now is the ICY Box docking station. Somehow windows 7 does not like it.
I found out when I got to get it to install by turning off USB and setting it to PS/2. I did the same thing to an old Win 7 VM and it showed a BOD after a while (stop 0x101, USB related). Both didn't work yesterday, but whatever. Then it dawned, that the only thing USB related that might interfere is the new docking station.

Glad you kept up the hunt and found a solution!

With Windows 10 there may be other causes of trouble. Start the guest from full normal shutdown, not save-state. Run until you see the problem happen, then shut down the guest from within the guest OS if possible. If not possible, close the Virtualbox window for the guest with the Power Off option set.

Right-click the guest in the main Virtualbox window's guest list, choose Show Log. Save the far left tab's log, zip it, and post the zip file, using the forum's Upload Attachment tab.

Thanks @scottgus1!

Save the far left tab's log, zip it, and post the zip file

I already did, as you may see. It is in deed a problem with the USB btw. I do not know how to work around it, but I'll continue to try

VMFox wrote:I already did, as you may see.

No, that's the hardening log, 2nd tab from the left. Care to try again?