NOTE: Windows 7 pro 64bit guest 7.08 drops shared folders and gets permission error if manually mapping to Linux host Samba shares; 7.0.9r156960 fails to install for digital signing and disabling digital signing in Windows 7 to get GA 7.0.9r156960 installed results boot hang at Windows repair and fails to repair. I keep rsync'd backup(s) so restored a 7.06 backup of the Win7 guest for now.
No issues with Fedora38 and Ubuntu LTS 1604 guests installing/using 7.0.9r156960.
EDIT: 7.0.9r156960 drops Shared Folders in Fedora38
EDIT: 7.0.97r158046 blue screens Windows XP guest, and fails to complete installation in Ubuntu guest results in non-bootable guests.
roll-back to 7.0.97r158010 resolves both issues.
EDIT: 7.0.97r158246 Windows XP and Ubuntu guests good to go.
Last edited by WFV on 12. Jul 2023, 06:44, edited 8 times in total.
I can confirm that VBoxGuestAdditions_7.0.9-156986.iso seems to be working fine on Win10, WinXP and Win2K. Thanks all for the quick resolution of this problem!
Had the same issue; sticking with the old extensions for now. I'm sure the developers will soon release a fix, but until then, the old extensions still work.
lylejk wrote:Had the same issue; sticking with the old extensions for now. I'm sure the developers will soon release a fix, but until then, the old extensions still work.
The discussion above concerns the Guest Additions, not the Extension Pack. See the user manual. And please do not confuse people by conflating these two unrelated features.
lylejk wrote:Had the same issue; sticking with the old extensions for now. I'm sure the developers will soon release a fix, but until then, the old extensions still work.
The discussion above concerns the Guest Additions, not the Extension Pack. See the user manual. And please do not confuse people by conflating these two unrelated features.
Thought they were one and the same. Regardless, not updating the Guest Additions (i.e., keeping the ones from 7.06) still works, otherwise, not having any issues with 7.08 itself. Definitely glad I saved recovery point.
Presumably the reason is that there is no current build that the devs need you to test. Meaning that a previous build has been withdrawn and nothing yet replaces it.
There is no formal release schedule for test builds, nor any committment to keep them around, maintain them or support them.