virtualbox.org

I recently have re-installed VirtualBox and recreated a VM because I was having a resolution error with scroll bars appearing due to all the troubleshooting I could find not working. After setting up the VM I started it up for the first time to install Windows 10. It went through the prompts just fine but upon restart it puts the VM in an aborted state. This will keep repeating if I try to restart the VM. Attached is the log.

P.S. I'm fairly new to VMs.

Thank to anyone whos willing to help with this.

You have 3D acceleration enabled, which requires good host graphics drivers, and Virtualbox Hardening finds a bad file in your Nvidia drivers:

00:00:02.754630 supR3HardenedErrorV: supR3HardenedScreenImage/LdrLoadDll: rc=VERR_CR_X509_CPV_NOT_VALID_AT_TIME fImage=1 fProtect=0x0 fAccess=0x0 \Device\HarddiskVolume8\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_2b99a29f071e5d25\nvldumdx.dll: Certificate is not valid (ValidTime=2020-06-21T21:27:51.000000000Z Validity=[2018-07-18T17:42:53.000000000Z...2019-07-18T17:42:53.000000000Z]): \Device\HarddiskVolume8\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_2b99a29f071e5d25\nvldumdx.dll

Nvidia may have just put out new drivers with an improperly- or not-signed file. This has come up a couple times in the last few days. Get on the chat with Nvidia or downgrade to drivers from a couple weeks ago.

scottgus1 wrote:You have 3D acceleration enabled, which requires good host graphics drivers, and Virtualbox Hardening finds a bad file in your Nvidia drivers:

00:00:02.754630 supR3HardenedErrorV: supR3HardenedScreenImage/LdrLoadDll: rc=VERR_CR_X509_CPV_NOT_VALID_AT_TIME fImage=1 fProtect=0x0 fAccess=0x0 \Device\HarddiskVolume8\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_2b99a29f071e5d25\nvldumdx.dll: Certificate is not valid (ValidTime=2020-06-21T21:27:51.000000000Z Validity=[2018-07-18T17:42:53.000000000Z...2019-07-18T17:42:53.000000000Z]): \Device\HarddiskVolume8\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_2b99a29f071e5d25\nvldumdx.dll

Nvidia may have just put out new drivers with an improperly- or not-signed file. This has come up a couple times in the last few days. Get on the chat with Nvidia or downgrade to drivers from a couple weeks ago.

You nailed it! I went in and disabled 3D acceleration and boom, worked like a charm. Thanks a bunch scottgus1

Good! Glad you're up and running.

Note that turning off 3D is a workaround to the problem, not a fix. No 3D simply doesn't use the host's video card and drivers to render the guest.

If you find that your guest's programs run just fine with 3D off, though, then it is perfectly OK to run without 3D.