Page 1 of 1

Version 4.3.20 r96997 gives kernel32.dll [lacks WinVerifyTru

Posted: 19. Jan 2015, 08:20
by Nitin
Hi I have installed various version of Virtual Box but getting same error.

ENV:
Win Ver : Windows 7 Enterprise 64Bit (6.1 Build 7601)
Processor : Intel(R) core (TM) i7-4470 CPU @ 3.40Ghz 8CPU,
Memory : 16GB.
Antivirus : Symantic Endpoint Protection.

Code: Select all

2620.154c: supHardenedWinVerifyImageByHandle: -> 22900 (\Device\HarddiskVolume2\Windows\System32\kernel32.dll)
2620.154c: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume2\Windows\System32\kernel32.dll
2620.154c: supR3HardenedMonitor_LdrLoadDll: pName=C:\Windows\system32\kernel32.dll (Input=kernel32.dll, rcNtResolve=0xc0150008) *pfFlags=0xffffffff pwszSearchPath=0000000000000000:<flags> [calling]
2620.154c: supR3HardenedScreenImage/NtCreateSection: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume2\Windows\System32\kernel32.dll [lacks WinVerifyTrust]
2a84.dc0: Error (rc=258):
2a84.dc0: Timed out after 60008 ms waiting for child request #1 (CloseEvents).
2a84.dc0: Error 258 in supR3HardNtChildWaitFor! (enmWhat=5)
2a84.dc0: Timed out after 60008 ms waiting for child request #1 (CloseEvents).
I have tried disabling the Antivirus but it is showing same error.

Attached is log file for more details.

Re: Version 4.3.20 r96997 gives kernel32.dll [lacks WinVerif

Posted: 19. Jan 2015, 08:44
by socratis
Take a look at the discussion: Windows 4.3.20 specifically for errors due to security. That's where you should post your information. You might find some newer test builds and/or other helpful hints. Here is one hint; try 4.3.12.

Re: Version 4.3.20 r96997 gives kernel32.dll [lacks WinVerif

Posted: 19. Jan 2015, 13:17
by mpack

Re: Version 4.3.20 r96997 gives kernel32.dll [lacks WinVerif

Posted: 31. Jan 2015, 03:01
by tl
I am waiting on IT to make the suggested change, but check out tSymantec Bulletin TECH225620

Re: Version 4.3.20 r96997 gives kernel32.dll [lacks WinVerif

Posted: 31. Jan 2015, 11:43
by mpack
Thanks for the tip, however that will not actually help with the OPs problem, which is caused by a Windows Update snafu, not Symantec AV.