Win7 Pro (64) guest still fails to shutdown since 7.0.16

[WFV]

Windows 7 Pro 64 bit guest hangs on "Shutting down" indefinitely since 7.0.16, problem persists in 7.0.18. Linux host is up to date kernel and VirtualBox. Have to kill the PID to close the session, reboot is out of question as well.

VBox.log.tar.gz

(38.51 KiB) Downloaded 12 times

[JKelly]

I believe the issue is with the USB HIDMouse (Per your Log file you see the hang at "Detached 'HidMouse' from port 1 on RootHub#1") in Windows. The USB HIDMouse often will not shut down under Version 7.0.16, for Windows versions older than Win 11. I tested Win10(32) - won't shut down, but Win 8.1(32), Win7(64 - Ultimate), and Win98SE will shut down with no issues. Linux guests do not have this issue.

Possible work around (worked for me):
Select the Windows VM you want to change.
1) In VM Settings choose PIIX3 chipset (I did not test if you already had selected that chipset).
2) In VM Settings choose PS/2 Mouse (not USB Tablet).
2.5) Start up Windows
3) Reboot Windows, to get everything recognized by Windows (to get the changes made above to work)
4) Once it restarts, in Windows Device Manager, uninstall HID Mouse in the Mice section
5) Reboot Windows again.
6) For good measure, reset the VM
That solved my issues with shutdown.

[WFV]

Thank you very much for the reply @ JKelly.
1) PIIX3 was already selected (default for Win7 guest from initial build long time ago)
2) changed mouse to PS/2
Booted up guest, device mgr showed PS/2 mouse and HID mouse to remove anywhere.
Shutdown still hangs, black screen indefinitely after Logging off, Shutting down,
end of the log now reads:

Code: Select all

00:09:15.777018 AHCI#0: Reset the HBA
00:09:15.777049 VD#0: Cancelling all active requests
00:09:16.373084 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago
00:09:22.244281 VMMDev: Guest Log: VBoxGuest: BugCheck! P0=0xfe P1=0x8 P2=0x6 P3=0x6 P4=0xfffffa80088ba000
00:09:22.246221 GIM: HyperV: Reset initiated through MSR
00:09:22.246252 Changing the VM state from 'RUNNING' to 'RESETTING'
00:09:22.248069 GIM: HyperV: Resetting MMIO2 regions and MSRs
00:09:22.248206 PIT: mode=3 count=0x10000 (65536) - 18.20 Hz (ch=0)
00:09:22.249154 Display::i_handleDisplayResize: uScreenId=0 pvVRAM=0000000000000000 w=1920 h=984 bpp=0 cbLine=0x0 flags=0x2 origin=0,0
00:09:22.255801 GUI: UISession::sltAdditionsChange: GA state really changed, notifying listeners
00:09:22.255860 GUI: UIMachineViewNormal::adjustGuestScreenSize: Adjust guest-screen size if necessary
00:09:22.256133 GUI: UISession::sltAdditionsChange: GA state change event came, notifying listeners
00:09:22.256141 GUI: UIMachineLogicNormal::sltCheckForRequestedVisualStateType: Requested-state=1, Machine-state=6
00:09:22.256474 Display::i_handleDisplayResize: uScreenId=0 pvVRAM=0000726c40000000 w=640 h=480 bpp=0 cbLine=0x140 flags=0x0 origin=0,0
00:09:22.258843 GUI: UIMachineLogic: Guest-screen count changed
00:09:22.315762 AHCI#0: Reset the HBA
00:09:22.315803 VD#0: Cancelling all active requests
00:09:22.315920 PIIX3 ATA: Ctl#1: finished processing RESET
00:09:22.315946 HDA: Codec reset
00:09:22.315954 HDA: Reset
00:09:22.315994 PIIX3 ATA: Ctl#0: finished processing RESET

[JKelly]

Another suggestion:

You are using the current version (7.0.18) of Guest Additions in the Guest VM for Win7.

I have found that Win7 is not happy using recent versions of Guest Additions. However, VirtualBox does not like it when you downgrade Guest Additions, so save a copy of the VM Win7.vdi file BEFORE you make any change to the Guest Additions version. That will allow you to recover relatively easily if VBox throws a new error when you downgrade Guest Additions. That way I have not made matters worse.

I use the Guest Additions from 6.1.42 (from Jan. of 2023, but nothing else from that version of VirtualBox) on Win7 and I never update it when I install the current VirtualBox on the host. I also would run the Windows command "SFC /scannow" (run in a CMD.EXE window as an Administrator) to see if you have another Windows error that can be fixed by Windows.

You can get the old version of Guest Additions from the download file.
"https://download.virtualbox.org/virtual ... 77-Win.exe". Use 7Zip to extract Guest Additions from the file (I don't know how to do this from Linux using p7zip, only from within Windows using 7zip). The file is named "file_VBoxGuestAdditions.iso" You should rename the ISO file as "GuestaddWin7.iso" (so you don't install it on newer Windows by mistake). The run/mount the renamed ISO as a CD in Wn7 and run it inside Win7 to install the old Guest Additions version 6.1.42

[WFV]

Thanks again JKelly, yes running VBox 7.0.18 with its current GA. Downgrading to GA 7.0.14 along with a good guest backup of same version resulted in same shutdown hang with Host at 7.0.18; downgrading Host to 7.0.14 caused host to lock up unable to switch TTY's or ssh into from other machine. So for now I restored system to current VBox 7.0.18, except using another Win7 backup guest 7.0.16 - I keep a few rsync'd backups. It's not a showstopper as its not a production guest. Just a minor annoyance to have to close the Win7 guest via sigterm PID. Have found almost no info out there with others having same issue so really appreciate your input.
EDIT: got a clean reboot after upgrading GA to 7.0.18 but still have to kill PID for shutdown (7.0.16 was also hanging on reboot)
EDIT: sfc scannow results no errors, no repairs however, guest shutdown clean. Nothing changed here.

[WFV]

Marking this solved though don't know root cause/solution. It's shutdown without issue two times now.

Code: Select all

sfc /scannow

resulted no errors or repairs however, the DISM and CBS logs had a couple lines indicating repairs completed but no mention of corruption. Also virtualbox-host-modules-arch (unsupported here) updated from 7.0.18-1 to 7.0.18-2. Host and guest all current (7.0.18...)

[csmccarron]

Having the same problem with Windows 10 Guest on a Windows 10 Host. Was having major issues with video drivers in 7.0.14, they kept resetting. Upgraded to 7.0.18 and virtual machine will not shutdown, what a pain in the backside!

[WFV]

Had two normal shutdowns, now back to killing PID.