Unable to start guests on Windows 10 Insider build 14971

[teh_klev]

Windows 10 Pro (x64) Insider build 14971 arrived today and VirtualBox is know no longer to start any of my VM's

The following appears in a dialogue box:

Title: VirtualBox - Error In supR3HardNtChildPurify

Message:

supHardenedWinVerifyProcess failed with VERR_CR_X509_CPV_NOT_VALID_AT_TIME: (rc=-23033) Please try reinstalling VirtualBox.

where: supR3HardNtChildPurify what: 5 VERR_CR_X509_CPV_NOT_VALID_AT_TIME (-23033) - Certificate path validator: The certificate is not valid at the specified time.

I've tried reverting to VBox 5.1.6 & 5.1.7 and also installing the 5.1.9-111957 test build.

The VBoxHardening.log file reports some kind of certificate validation problem with ntdll.dll in \Windows\System32:

118c.1b38: supHardenedWinVerifyProcess failed with Unknown Status -23033 (0xffffa607): Certificate is not valid (ValidTime=2088-08-14T12:05:18.000000000Z Validity=[2014-05-28T17:33:33.000000000Z...2029-05-28T17:43:33.000000000Z]): \Device\HarddiskVolume4\Windows\System32\ntdll.dll

118c.1b38: Error -23033 in supR3HardNtChildPurify! (enmWhat=5)

118c.1b38: supHardenedWinVerifyProcess failed with Unknown Status -23033 (0xffffa607): Certificate is not valid (ValidTime=2088-08-14T12:05:18.000000000Z Validity=[2014-05-28T17:33:33.000000000Z...2029-05-28T17:43:33.000000000Z]): \Device\HarddiskVolume4\Windows\System32\ntdll.dll

[Bobbyw87]

I am experiencing the same exact problem.

[Socratis]

Please use the search functionality before opening a new bug. This is a duplicate of #16198.

Also, discussion on ​https://forums.virtualbox.org/viewtopic.php?f=38&t=80701

[teh_klev]

Sorry, my search-fu failed me utterly here. Also hadn't noticed the newish "VirtualBox on Windows pre-releases" forum.

[Klaus Espenlaub]

Duplicate of #16198, as mentioned before.

[Klaus Espenlaub]

Duh. Should've checked why #16198 was closed before closing this one as a duplicate.

The fix is in the latest testbuilds, and will be in 5.1.10.

[Socratis]

Replying to klaus:

Duh. Should've checked why #16198 was closed before closing this one as a duplicate.

It's OK, we've had a good 3 minutes of back and forth. Literally... :D

[Frank Mehnert]

Fix is part of VBox 5.1.10.

[MattPark]

Not trying to zombie this but when I got the error message, this was the first result, and not very helpful.

PSA: If you are running a windows insider preview build, they expire periodically if you don't update. Virtualbox will notice the expired cert and block you from starting your VMS. Check your windows expiration date with winver command.

For me, the build wasn't updating because I had blocked their diagnostic spying at some point. Hope this helps.

Back to the grave....