My VBox settings:
- VRAM: 128 MB
3D Acceleration: Enabled
VM: Debian (Buster) 64 bits
VBox Guest Additions: 6.1.12 r139181
Virtual Box: 6.1.12 r139181
Is there a solution for this problem so i can use the 3D acceleration mode in Virtual Box?
NVIDIA knows about the problem since the 1st of July, see nVidia Driver 451.48 appears to break VirtualBox 3D Acceleration on Windows 10 1909.scottgus1 wrote:Get on Nvidia's help channels or forums to see if someone has let them know
Exactly! I installed 446.14 and it works swiftly! I also noted that the Signatory Name of the nvd3dumx.dll of this version is different: GlobalSign TSA for MS Authenticode - G2fth0 wrote:The driver version 446.14 will probably work, whereas the driver versions 451.48, 451.58 and 451.67 will not.
scottgus1 wrote:Nvidia's file is missing a portion of its security signing.
Your analysis is not correct IMHO. The root authority "Microsoft Digital Media Authority 2005" doesn't pose a problem. Otherwise, the older NVIDIA drivers would also be rejected.squall leonhart wrote:signature verification that relies only on access to the certificate root store
Yeah, fth0 also mentioned that there's more to it than my basic understanding of the problem. But I suspect that the average Virtualbox user is down near my level of understanding of the subject.squall leonhart wrote:no it isn't.scottgus1 wrote:Nvidia's file is missing a portion of its security signing.
Digital signing is a multitier thing, the expiry on one certificate is made irrelevant by additional countersignatures on the file, where windows is concerned the single sha1 would fail to start on its own on windows but the countersignatures and being from a kernel root authority makes the expiration ignored.fth0 wrote:Your analysis is not correct IMHO. The root authority "Microsoft Digital Media Authority 2005" doesn't pose a problem. Otherwise, the older NVIDIA drivers would also be rejected.squall leonhart wrote:signature verification that relies only on access to the certificate root store
The real problem (as you've also mentioned) is that VirtualBox requires all signatures to be valid, not only one of them. Whether this makes sense from an overly hardening point of view, is of course debatable.
Trouble is, the file isn't old,scottgus1 wrote:Yeah, fth0 also mentioned that there's more to it than my basic understanding of the problem. But I suspect that the average Virtualbox user is down near my level of understanding of the subject.squall leonhart wrote:no it isn't.scottgus1 wrote:Nvidia's file is missing a portion of its security signing.
For the average folks, I figure a quick "the file is bad get a new or older one" hopefully will get their Virtualbox going again.
Where exactly is this stated?jacobd wrote:NVIDIA are advising that their digital signing is not incorrect
NVIDIA still used the expired certificate when signing the 451.85 NVIDIA drivers.jacobd wrote:New NVIDIA hotfix driver just released