Virtual Box 6.1.16 was running great until this morning after Windows Defender did a definition update.
After booting up this morning and attempting to start VB, I get the following error.
supHardenedWinVerifyProcess failed with Unknown Status -23033 (0xffffa607): Certificate is not valid (ValidTime=2021-02-02T02:06:57.178135200Z Validity=[2020-04-01T19:28:51.000000000Z...2021-01-31T19:28:51.000000000Z]): \Device\HarddiskVolume4\WINDOWS\System32\ntdll.dll
The error dialog tells me to re-install Virtual Box. I upgraded to VB 6.1.18 and still getting the same error.
All of the specifics are hopefully in the uploaded VBoxHardening.log.
Hardening Issue with Windows Defender update
Hardening Issue with Windows Defender update
- Attachments
-
VBoxHardening.log- VBoxHardening log
- (21.29 KiB) Downloaded 162 times
Re: Hardening Issue with Windows Defender update
The reporting hardening issue was with Windows Insider 20201 which was a stable version running current releases of VirtualBox prior to yesterday's experience.
I updated to Windows Insider 21301 and now VirtualBox 6.1.18 is running just fine.
I was pausing any updates beyond 20201 because they were breaking VirtualBox. Well it now seems 21301 is the go to version for running VirtualBox.
When the next version of Windows Insider is installed, if breaks VirtualBox I'll have the option of retreating to 21301.
It would nice to have a definitive answer as to why Windows Insider is breaking VirtualBox.
I updated to Windows Insider 21301 and now VirtualBox 6.1.18 is running just fine.
I was pausing any updates beyond 20201 because they were breaking VirtualBox. Well it now seems 21301 is the go to version for running VirtualBox.
When the next version of Windows Insider is installed, if breaks VirtualBox I'll have the option of retreating to 21301.
It would nice to have a definitive answer as to why Windows Insider is breaking VirtualBox.