This looks like a known problem with Vista not liking dual certificates on drivers. Instead of using the weaker certificate it recognizes, it complains about the stronger certificate it doesn't recognize, which is intended for later OS. This is nothing to do with it being a VM: Vista holdouts would have the exact same problem with any modern driver. I suggest that you Google for solutions.
I was having this issue and I think I solved it. I don't know what the defining solution was - but I went into C:\Program Files\Oracle\VirtualBox Guest Additions on the Guest (Vista VM) and ran every application as administrator. I can't remember which one, but either VBoxControl or VBoxDrvInst errored and said "This might not have installed properly, reinstall with recommended settings?" I reluctantly hesitated on this - but went back to using the recommended settings and it seemed to complete with no issues. Then, I ran the VBoxWindowsAdditions-x86 (on the Disk Drive) as administrator. It completed successfully and seems to be functioning as intended. I'm using Vista 32 bit as my guest vm on a Windows 10 Host. To clarify, I think the VBoxDrvInst is the one that was giving me problems - but I honestly don't remember. I just ran every application listed on the disk iso and in that VirtualBox Guest Additions folder on the C drive as administrator and then retried the -x86 executable. It was only after using those recommended settings that it functioned correctly upon running the x86 executable.
billynps wrote:Estou com este mesmo problema no Windows 10
I assume that Windows 10 is your host, and that you have a Vista GUEST. The host is not relevent to this discussion, the problem is with Vista itself.
billynps wrote:Alguém tem a solução para resolver isso?
Short of going back in time and fixing Vista, I'm not sure what can be done here. Removing the later certification would make the GAs incompatible with Win8 and Win10, and if it's a choice of Vista vs Win10... well it isn't a real choice. The other option is to build two versions of the Windows GAs instead of using dual signatures, I assume the devs have looked at that but I'm not aware of any comments made.
bpoconno wrote:I was having this issue and I think I solved it. I don't know what the defining solution was - but I went into C:\Program Files\Oracle\VirtualBox Guest Additions on the Guest (Vista VM) and ran every application as administrator. I can't remember which one, but either VBoxControl or VBoxDrvInst errored and said "This might not have installed properly, reinstall with recommended settings?" I reluctantly hesitated on this - but went back to using the recommended settings and it seemed to complete with no issues. Then, I ran the VBoxWindowsAdditions-x86 (on the Disk Drive) as administrator. It completed successfully and seems to be functioning as intended. I'm using Vista 32 bit as my guest vm on a Windows 10 Host. To clarify, I think the VBoxDrvInst is the one that was giving me problems - but I honestly don't remember. I just ran every application listed on the disk iso and in that VirtualBox Guest Additions folder on the C drive as administrator and then retried the -x86 executable. It was only after using those recommended settings that it functioned correctly upon running the x86 executable.
OMG two years of not being able to install a current copy of Guest Additions.
Windows 2008, 2012 R2 guests. The install would abort at vboxmouse.inf and blather on about signatures.
On the Virtualbox guest additions cd.. open the cert directory. double click on the sha256 or sha1 cert. View the Oracle cert. Click on certificate path. Double click on the top one.. .Digi. Install the cert. Put it into Trusted Root Certs. Rerun install. it finishes this time without problems.
for fun, you can put the Oracle into Trusted publishers, and the first Digi cert into Trusted intermediate cert authorities... but that is not fully necessary.
aldrichs wrote:OMG two years of not being able to install a current copy of Guest Additions.
More like, OMG two years of "me too" artists not bothered to read the previous comments. Executive summary: if you want Vista fixed, go speak to Microsoft, but I suspect you may wait way longer than two years.