Guest Additions 6.1.32 fails to install

[codeslayer2010]

I upgraded this morning to VirtualBox 6.1.32. The downloads website says "Note: After upgrading VirtualBox it is recommended to upgrade the guest additions as well." Immediately after downloading, I was presented with a popup that said something like "do you want to automatically install the guest additions now?" and I clicked affirmative. Guest Additions said it was successful, and it required a reboot. After the VM rebooted, the screen was small and did not auto resize anymore. Previous to the update this morning my Win 7 Ultimate VM was working perfectly.

Also, I tried to take a screenshot of the guest from the host and it didn't work. I successfully took a screenshot of the guest from within itself, but I couldn't get shared folders to work since the update.

Here is what I tried:

• - Closed VM and restarted VirtualBox -- no-go
  - Attempted to reinstall Guest Additons -- this time I got an error that said it didn't install properly and something like try again
  - Tried again. This time no error but still doesn't auto adjust

Specs:
- Host: Windows 10 64-bit
- Guest: Windows 7 Ultimate


My Questions:

1) Is this a known issue with a clear fix? I was unable to find anything in this forum to solve it, but I did find a few posts that mentioned downgrading to a different version. At least one advised against that strategy (viewtopic.php?f=6&t=105126&p=512816&hil ... ls#p512816)

2) Should I try to revert back to a different version? If so, which version number specifically?

3) How do I get Guest Additions correctly installed so that my guest VM screen will auto-resize once again?

[mpack]

The log shows that the 6.1.32 Guest Additions are installed.

00:00:21.177951 VMMDev: Guest Log: VBoxGuest: Windows version 6.1, build 7601
00:00:21.307791 VMMDev: Guest Additions information report: Version 6.1.32 r149290 '6.1.32'
00:00:21.307843 VMMDev: Guest Additions information report: Interface = 0x00010004 osType = 0x00037100 (Windows 7, 64-bit)

Try setting the display size using View|Virtual Screen 1|Resize to www x hhh.

[scottgus1]

The log also shows the VM OS BSODing with a DRIVER_IRQL_NOT_LESS_OR_EQUAL.

I'm going to guess that the driver for the Virtualbox video card did not install correctly.

Lately, Microsoft upgraded their security signing protocols to require SHA256. Web-search how to check to see if your Windows 7 OS has been patched to support SHA256 security hashing.

I think that the Guest Additions installer is a Windows MSI installer, meaning that logging can be enabled. Enable MSI logging, then uninstall/reinstall GAs again. If it error-messages or the full GAs capability does not re-appear, please post the log as a zip file using the forum's Upload Attachment tab.Basic troubleshooting steps for Windows Installer
Enable Windows Installer logging
https://docs.microsoft.com/en-US/troubl ... er-logging

• Repair MSI (Windows Installer) 2.8.8.
• Windows Repair 4.5.1 (includes the above).

[codeslayer2010]

Thanks for your reply scottgus1 and your insight about Microsoft and SHA256 and MSI logging. I will look into that and report back.

For a minute there I thought it was working. I reinstalled Guest Additions by right-clicking on the guest CD and choosing the install option displayed in black at the top of the context menu. It reinstalled and rebooted and was still small. I forgot to mention this before, but I had already made sure to select View > Auto-Resize Guest Display. But, somehow that got unchecked, so I enabled that option and it seemed to be working. But, then within about 5 minutes I got this error:

[img]

Application Error: Referenced memory issue

EH_ERROR_20220222_VirtualBoxVM_MemNotRead_01.01.jpg (31.45 KiB) Viewed 2788 times

[/img]

VirtualBox shut down immediately on clicking OK:

[mpack]

That's a host error isn't it? (VirtualBoxVM.exe is a host process, not a Guest Addition). In which case the error is likely to be related to hardening, probably an unsigned graphics DLL if installing the GAs kicks off the symptoms. You could prove that by disabling 3D acceleration in the VM settings.

[codeslayer2010]

In the interest of time I weighed my options and determined that I might be able to get up and running quickest by uninstalling VirtualBox then reinstalling (downgrading) to a different version, and then using that version's Guest Additions. That worked. Here are my specs for success:

VirtualBox 6.1.30
Guest Addtions 6.1.10