viewtopic.php?f=3&t=81046&start=0
However, since that thread, I have tried a lot more things to fix this. I have completely reinstalled the os and all drivers (it was done correctly and through the manufacturer) and all my hardware is working correctly and up to date. I did not restore any of my old settings. The new virtual machines I have are experiencing the exact same problems. It does not matter what ISO I use. Guest Additions has been installed correctly. I am desperate for a solution. I have a few theories that I could use some opinions on. But first, here is all the information you should need:
Code: Select all
00:00:59.295392 supR3HardenedErrorV: supR3HardenedScreenImage/LdrLoadDll: rc=VERR_CR_PKCS7_KEY_USAGE_MISMATCH fImage=1 fProtect=0x0 fAccess=0x0 \Device\HarddiskVolume3\Windows\System32\DriverStore\FileRepository\nvmii.inf_amd64_742a1ef549eb6d0c\nvd3dumx.dll: WinVerifyTrust failed with hrc=CERT_E_CHAINING on '\Device\HarddiskVolume3\Windows\System32\DriverStore\FileRepository\nvmii.inf_amd64_742a1ef549eb6d0c\nvd3dumx.dll'
00:00:59.295562 supR3HardenedErrorV: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\WINDOWS\System32\DriverStore\FileRepository\nvmii.inf_amd64_742a1ef549eb6d0c\nvd3dumx.dll' (C:\WINDOWS\System32\DriverStore\FileRepository\nvmii.inf_amd64_742a1ef549eb6d0c\nvd3dumx.dll): rcNt=0xc0000190
00:00:59.295946 supR3HardenedErrorV: supR3HardenedScreenImage/LdrLoadDll: cached rc=VERR_CR_PKCS7_KEY_USAGE_MISMATCH fImage=1 fProtect=0x0 fAccess=0x0 cHits=1 \Device\HarddiskVolume3\Windows\System32\DriverStore\FileRepository\nvmii.inf_amd64_742a1ef549eb6d0c\nvd3dumx.dll
00:00:59.295984 supR3HardenedErrorV: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\WINDOWS\System32\DriverStore\FileRepository\nvmii.inf_amd64_742a1ef549eb6d0c\nvd3dumx.dll' (C:\WINDOWS\System32\DriverStore\FileRepository\nvmii.inf_amd64_742a1ef549eb6d0c\nvd3dumx.dll): rcNt=0xc0000190
So here are some of the oddities:
1) It is completely inconsistent. Sometimes it works fine, sometimes it does not. I have not been able to reliably reproduce it.
2) The only AV I use is Avast. I have tried completely disabling Avast, whitelisting all vbox processes, and a couple other things. Nothing works, so I do not think it's the AV.
3) I usually DO NOT have problems when I try to run the virtual machine whilst connected to my computer via RDP.
4) Sometimes restarting the computer 4-5 times will get it to work correctly, but this is not consistent, and sometimes restarting 20 times will do absolutely nothing.
After a lot of research, I feel like it may have something to do with incorrectly signed certificates on nvd3dumx.dll, but I do not know enough about certificates or how they work to troubleshoot this. Therefore, I have attached some pictures of this. Basically, the first odd thing I noticed is that there are 3 very similar folders, all containing basically the exact same files (not necesscarily the exact same because some appear to be newer than others, but they are all the same file names). Only one of the folders (nvmii.inf_amd64_742a1ef549eb6d0c) contains the nvd3dumx.dll that is causing the problem. The other two also have the own nvd3dumx. When I looked at them, they appear to have more signatures than the one that is being rejected (see pictures).
Could this cause a hardening error? Could I manually sign these files to make it stop? Is this NVIDIA's fault or virtualbox? Please help me. This is the most annoying error I've ever dealt with. I am aware that there is an older version of VBox that does not feature hardening. I am considering this is an all else fails solution.