We have found that we can install Process Hacker 2.39124 on Windows 10 1809 17763.316 in a VMWare VM with secure boot enabled. We think that the secure boot is working correctly because it will prevent our counter-signed filter driver from being installed whereas it will allow our Microsoft cross-signed driver to be installed. Does anyone know why the Process Hacker driver kprocesshacker.sys which is only counter-signed, is able to get installed with secure boot enabled?
It looks like you're new here. If you want to get involved, click one of these buttons!
|Upcoming OSR Seminars|
|Developing Minifilters||29 July 2019||OSR Seminar Space|
|Writing WDF Drivers||23 Sept 2019||OSR Seminar Space|
|Kernel Debugging||21 Oct 2019||OSR Seminar Space|
|Internals & Software Drivers||18 Nov 2019||Dulles, VA|