karabaja4 wrote: ↑8. Nov 2023, 13:56
Can you elaborate on what the root cause was?
The missing cross-cert, which klaus and I already mentioned in this thread, had to be added to the build servers as a separate file, because it's not contained in any of the Windows certificate stores.
Actually it was the other way round: the cross-cert was expected to be in the Windows certificate store where it wasn't.
Either way, there is more fixing in the queue. I hope that the next test builds (if everything goes as expected they'll be finished sometime tomorrow) will resolve the remaining issues with Windows 7 and older.
Installed VirtualBox-7.0.13-160137-Win; the Gust Additions packaged is VirtualBox-7.0.13-160034, so I installed VBoxGuestAdditions_7.0.13-160137 instead.
First impressions are good, Win XP, Win 7 and Win 11 are ok. I'll check Linux later and report if there are issues.
Note that the so far last fix relevant for code signing of Windows Guest Additions (and the Windows host package) was applied to the various branches in revision 160106 to 160108. So if you have Guest Additions with this revision or later then there's no immediate need to try the "very latest revision", because after that we just updated a 3rd party library to a newer version which won't make any functional difference.
Ah, I just spotted that the build of Guest Additions 7.0.13r160108 failed last night (usual reason, Attestation signing taking forever running into a timeout). That explains why the 7.0.13r160137 packages contain the outdated GA ISO.
Installed VirtualBox-7.0.13-160164-Win (the packaged Gust Additions is 7.0.13-160137). I installed VBoxGuestAdditions_7.0.13-160164 instead.
Win XP, Win 7 and Win 11 are running fine, I don't notice issues as yet.
Update:
While both Shared Clipboard and Dar'n'Drop are enabled Bidirectional (in all my Guest installations):
I can Drag & Drop from the Guest to the Host but not from Host to Guest.
I cannot cut/copy and paste from Guest to Host nor from Host to Guest.
Notice:
I have a shared folder where files can be moved both ways.
Host: Windows 10 21H2 64 bit
Guest: Windows 10 2015 LTSB 32 bit
Upgraded virtualbox to 7.0.12, boots ok with 7.0.10 guest additions (but the taskbar hang). Installed 7.0.12 guest additions, no problem when installing. Reboot, then failed with invalid boot/bcd code: 0xc000014c.
What works for me:
1. attach windows installation iso
2. enter repair command prompt
3. rename C:\windows\system32\drivers\vboxguest.sys to vboxguest.sys-disabled
Char, a better solution than disabling part of Guest Additions is posted above. When posting a me-too, it is recommended and expected that the poster will read the topic first.
scottgus1 wrote: ↑12. Nov 2023, 14:02
Char, a better solution than disabling part of Guest Additions is posted above. When posting a me-too, it is recommended and expected that the poster will read the topic first.
I have read the thread, why do you assume I haven't?
The solution I found in the thread is to install 7.0.10 (how am I to install it when Windows can't boot?) or 7.0.13 (same problem). Disabling code signing from the repair console also didn't work. Booting windows with disable driver verification also didn't work. Also note that most previous reports are with windows 7/8. My guest is windows 10. Also AFAIK my issue is the first with invalid boot/bcd code: 0xc000014c.
First I have to rename the driver so that windows can boot and then I can downgrade to 7.0.10.
char101g wrote: ↑13. Nov 2023, 06:51
First I have to rename the driver so that windows can boot and then I can downgrade to 7.0.10.
This piece of information, the reason for renaming the driver, is not in your first post. You did not say that the intent of renaming the driver was to get the system to boot so you could upgrade/downgrade Guest Additions to the the recommended versions. Thus the idea arises that you're completely fixing your problem with Guest Additions only by disabling part of it. One must be taken at one's word.
Knowing that you're disabling the driver so you can boot the VM to replace the Guest Additions with the recommended versions rounds out your first post. Congrats on figuring a way to get the VM to boot so replacement can be made!
Its Virtual Machine not real PC, Virtual Disk can access with many way
rename the file is not explain the reason of the main problem
any way what I did was not just rename the file
I did access folder called (last good configuration) in Windows folder
this folder for option in boot menu that is disabled by Microsoft in Windows 8.1
moved the file from their into original location in DRIVER folder
now Guest addition installed version installed 7.0.12 except VBoxGuest.sys
which is from 7.0.10
Last edited by mpack on 17. Nov 2023, 17:38, edited 1 time in total.
Reason:Remove unnecessary bbcode.
I too have seen "Windows cannot verify the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software form an unknown source." today.
I ended up downgrading my Virtual Box installation to 7.0.10 to get my new Windows 7 VM up and running.
I like the new (to me) side bar for the notifications, but it is a nuisance having to click on the delete finished notifications button in the VM's window every time I start it up.
I would like them to auto disappear every time I start the VM after n seconds.
I might be missing something here, but I can't find a setting to enable such behaviour.
MikeWilliams_UK wrote: ↑22. Nov 2023, 15:07
I like the new (to me) side bar for the notifications,
If 7.0.12 is your first dive into 7.0, then I think you're the first poster to say "I like the side bar". All we get are complaints to get rid of it. viewtopic.php?t=110022
MikeWilliams_UK wrote: ↑22. Nov 2023, 15:07
I would like them to auto disappear
I don't think there is such a setting. The closest one can get is to turn off the common messages using the "slash through the speech bubble" icon to make the error not show anymore ever. Once common messages, like mouse integration and keyboard capture, are disabled, the side bar won't pop out, until an uncommon message happens.
You can put in an enhancement request for time-out disappearing of the side bar in the Bugtracker.