Not Valid Kernel Code

Discussions related to using the OSE version of VirtualBox.

Not Valid Kernel Code

Postby NTI » 17. May 2016, 16:42

I recently tried to build VBox v5.0.18 (signed) on Win7 x86. It built successfully, but upon loading a VM, it failed. Checking the log file, it complains a number of dlls not having kernel code signature. These dlls are pre-built by me. I tried to use a test signing certificate or a proper certificate from GoDaddy, but they all failed. Interestingly, I used the same set of dlls in my previous build of VBox 5.0.0 without problems. Does anyone know what's causing the new version not recognising them?

The dlls that VBox complains about are:
libeay32.dll
ssleay32.dll
libcurl.dll
QtOpenGL4.dll
QtGui4.dl
QtCore4.dlll

Code: Select all   Expand viewCollapse view
abc.96c: supHardenedWinVerifyImageByHandle: -> -5659 (\Device\HarddiskVolume2\VBox\VirtualBox-5.0.18\out\win.x86\release\bin\libeay32.dll) WinVerifyTrust
abc.96c: Error (rc=0):
abc.96c: supR3HardenedScreenImage/Imports: rc=Unknown Status -5659 (0xffffe9e5) fImage=1 fProtect=0x0 fAccess=0x0 \Device\HarddiskVolume2\VBox\VirtualBox-5.0.18\out\win.x86\release\bin\libeay32.dll: Not valid kernel code signature.: \Device\HarddiskVolume2\VBox\VirtualBox-5.0.18\out\win.x86\release\bin\libeay32.dll

abc.96c: supHardenedWinVerifyImageByHandle: -> -5659 (\Device\HarddiskVolume2\VBox\VirtualBox-5.0.18\out\win.x86\release\bin\ssleay32.dll) WinVerifyTrust
abc.96c: Error (rc=0):
abc.96c: supR3HardenedScreenImage/Imports: rc=Unknown Status -5659 (0xffffe9e5) fImage=1 fProtect=0x0 fAccess=0x0 \Device\HarddiskVolume2\VBox\VirtualBox-5.0.18\out\win.x86\release\bin\ssleay32.dll: Not valid kernel code signature.: \Device\HarddiskVolume2\VBox\VirtualBox-5.0.18\out\win.x86\release\bin\ssleay32.dll

abc.96c: supHardenedWinVerifyImageByHandle: -> -5659 (\Device\HarddiskVolume2\VBox\VirtualBox-5.0.18\out\win.x86\release\bin\libcurl.dll) WinVerifyTrust
abc.96c: Error (rc=0):
abc.96c: supR3HardenedScreenImage/Imports: rc=Unknown Status -5659 (0xffffe9e5) fImage=1 fProtect=0x0 fAccess=0x0 \Device\HarddiskVolume2\VBox\VirtualBox-5.0.18\out\win.x86\release\bin\libcurl.dll: Not valid kernel code signature.: \Device\HarddiskVolume2\VBox\VirtualBox-5.0.18\out\win.x86\release\bin\libcurl.dll

abc.96c: supHardenedWinVerifyImageByHandle: -> -5659 (\Device\HarddiskVolume2\VBox\VirtualBox-5.0.18\out\win.x86\release\bin\QtOpenGL4.dll) WinVerifyTrust
abc.96c: Error (rc=0):
abc.96c: supR3HardenedScreenImage/Imports: rc=Unknown Status -5659 (0xffffe9e5) fImage=1 fProtect=0x0 fAccess=0x0 \Device\HarddiskVolume2\VBox\VirtualBox-5.0.18\out\win.x86\release\bin\QtOpenGL4.dll: Not valid kernel code signature.: \Device\HarddiskVolume2\VBox\VirtualBox-5.0.18\out\win.x86\release\bin\QtOpenGL4.dll
abc.96c: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume2\VBox\VirtualBox-5.0.18\out\win.x86\release\bin\QtOpenGL4.dll
abc.96c: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'qtgui4.dll'...
abc.96c: supR3HardenedWinVerifyCacheProcessImportTodos: 'qtgui4.dll' -> '\Device\HarddiskVolume2\VBox\VirtualBox-5.0.18\out\win.x86\release\bin\qtgui4.dll' [rcNtRedir=0xc0150008]
abc.96c: supHardenedWinVerifyImageByHandle: -> -5659 (\Device\HarddiskVolume2\VBox\VirtualBox-5.0.18\out\win.x86\release\bin\QtGui4.dll) WinVerifyTrust
abc.96c: Error (rc=0):
abc.96c: supR3HardenedScreenImage/Imports: rc=Unknown Status -5659 (0xffffe9e5) fImage=1 fProtect=0x0 fAccess=0x0 \Device\HarddiskVolume2\VBox\VirtualBox-5.0.18\out\win.x86\release\bin\QtGui4.dll: Not valid kernel code signature.: \Device\HarddiskVolume2\VBox\VirtualBox-5.0.18\out\win.x86\release\bin\QtGui4.dll
abc.96c: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume2\VBox\VirtualBox-5.0.18\out\win.x86\release\bin\QtGui4.dll
abc.96c: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'qtcore4.dll'...
abc.96c: supR3HardenedWinVerifyCacheProcessImportTodos: 'qtcore4.dll' -> '\Device\HarddiskVolume2\VBox\VirtualBox-5.0.18\out\win.x86\release\bin\qtcore4.dll' [rcNtRedir=0xc0150008]
abc.96c: supHardenedWinVerifyImageByHandle: -> -5659 (\Device\HarddiskVolume2\VBox\VirtualBox-5.0.18\out\win.x86\release\bin\QtCore4.dll) WinVerifyTrust
abc.96c: Error (rc=0):
abc.96c: supR3HardenedScreenImage/Imports: rc=Unknown Status -5659 (0xffffe9e5) fImage=1 fProtect=0x0 fAccess=0x0 \Device\HarddiskVolume2\VBox\VirtualBox-5.0.18\out\win.x86\release\bin\QtCore4.dll: Not valid kernel code signature.: \Device\HarddiskVolume2\VBox\VirtualBox-5.0.18\out\win.x86\release\bin\QtCore4.dll


Thank you!
NTI
 
Posts: 21
Joined: 23. Jul 2015, 12:35

Re: Not Valid Kernel Code

Postby OraIsNotcal » 19. Mar 2018, 15:07

I have caught the same trouble as you!!!
OraIsNotcal
 
Posts: 1
Joined: 18. Mar 2018, 17:49

Re: Not Valid Kernel Code

Postby mpack » 19. Mar 2018, 16:40

If you need VirtualBox built for Windows with hardening enabled then I suggest that you download the official build. If nothing else it'll also be less ancient than 5.0.18.
mpack
Site Moderator
 
Posts: 27698
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

Re: Not Valid Kernel Code

Postby mhanor » 22. Mar 2018, 13:17

You need to build and sign all the required dlls. I use the same testsigning certificate for building and signing VirtualBox, Qt, libcurl, openssl. Linking must be done with the /integritycheck option.
mhanor
Volunteer
 
Posts: 296
Joined: 7. Oct 2009, 12:40
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: various


Return to VirtualBox OSE

Who is online

Users browsing this forum: No registered users and 2 guests