[Solved] Win10 - Update KB4057247 - VMs fail to start - bcrypt.dll

[JoelTX2]

Hello all,

Oracle VB : Version 5.1.22 r115126 (Qt5.6.2)
OS : Windows 10 Professionnal 64 bits.

I have a problem with my Virtual Box. After update Windows 10 - KB4057247, the host can't start with the status "AVORTEE". The log VBoxHardening.log indicates the error :

143c.1148: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume3\Windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_5.82.16299.125_none_88782a244abc4c60\comctl32.dll)
143c.1148: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume3\Windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_5.82.16299.125_none_88782a244abc4c60\comctl32.dll
143c.1148: supR3HardenedScreenImage/NtCreateSection: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\winmmbase.dll [lacks WinVerifyTrust]
143c.1148: supR3HardenedScreenImage/NtCreateSection: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\IPHLPAPI.DLL [lacks WinVerifyTrust]
143c.1148: supR3HardenedScreenImage/NtCreateSection: cache hit (Unknown Status -626 (0xfffffd8e)) on \Device\HarddiskVolume3\Windows\System32\bcrypt.dll [lacks WinVerifyTrust]
143c.1148: Error (rc=0):
143c.1148: supR3HardenedScreenImage/NtCreateSection: cached rc=Unknown Status -626 (0xfffffd8e) fImage=1 fProtect=0x10 fAccess=0xf cHits=4 \Device\HarddiskVolume3\Windows\System32\bcrypt.dll
143c.1148: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0xc0000190 'C:\Program Files\Oracle\VirtualBox\VirtualBox.dll'
ff0.2180: supR3HardNtChildWaitFor[2]: Quitting: ExitCode=0x1 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 625 ms, the end);
cdc.fb4: supR3HardNtChildWaitFor[1]: Quitting: ExitCode=0x1 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 1312 ms, the end);

I have no mean to desinstall KB4057247 > commande line : wusa /uninstall /kb:KB4057247 no functionnal with this pack. I try to duplicate my host : UNSUCCESS > same error

Any ideas ? Do you some issue to fix or resolve it ?

Thanks.
Joel.

[Martin]

You have rc=0, so that is not the problem.
Your VirtualBox 5.1.22 is way too old for a current Windows 10.
Please try again with the current VirtualBox 5.2.4 from https://www.virtualbox.org/wiki/Downloads

[JoelTX2]

Hello Martin,

Thanks for your asistance,
My VM was fonctionnal with this version before update Windows.
In addtionnal, there is these lines in the VBox.log with the word 'ERROR' :

00:00:03.086282 AIOMgr:     C:\Program Files\Oracle\VirtualBox\VBoxGuestAdditions.iso
00:00:03.086285 AIOMgr:     D:\Virtualbox\TX2EDI-EBR-32.vmdk
00:00:03.086865 Changing the VM state from 'POWERING_ON' to 'RUNNING'
00:00:03.086883 Console: Machine state changed to 'Running'
00:00:03.090194 VMMDev: Guest Log: BIOS: VirtualBox 5.1.22
00:00:03.091636 PIT: mode=2 count=0x10000 (65536) - 18.20 Hz (ch=0)
00:00:03.103010 ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={02326f63-bcb3-4481-96e0-30d1c2ee97f6} aComponent={DisplayWrap} aText={Could not take a screenshot (VERR_NOT_SUPPORTED)}, preserve=false aResultDetail=0
00:00:03.108926 Display::handleDisplayResize: uScreenId=0 pvVRAM=0000000000000000 w=720 h=400 bpp=0 cbLine=0x0 flags=0x0
00:00:03.114606 AHCI#0: Reset the HBA
00:00:03.114854 AHCI#0: Port 0 reset
00:00:03.116015 VMMDev: Guest Log: BIOS: AHCI 0-P#0: PCHS=16383/16/63 LCHS=1024/255/63 0x0000000004000000 sectors
00:00:03.116088 AHCI#0: Port 1 reset
00:00:03.116224 PIT: mode=2 count=0x48d3 (18643) - 64.00 Hz (ch=0)

An ideas ? A other control or check to do ?

[socratis]

Partial logs are not that helpful I'm afraid. Please ZIP and attach the full log. See the "Upload attachment" tab below the reply form.

Please read really carefully the following FAQ: Diagnosing VirtualBox Hardening Issues for some guidelines.

[JoelTX2]

Hello all,

I solved my pb by reinstalling OVM with the last version and recreate a new machine with the same .vmdk file.

Thanks for your assistance.

Regards.

[socratis]

Glad you got it going. Marking as [Solved].

[Patrick25]

Hello
I confirm that the update of VirtualBox also allowed me to no longer have this error when updating Windows 10 and to do like JoelTX2 done.
Translation done by Google