I get the following message: "only users with administrator privileges can run this demo".By looking at the code, it seems that your demo also managed to load the driver successfully but failed to inject the dll.

if not InjectLibrary(CDriverName, 'HookPrintAPIs32.dll', ALL_SESSIONS, true, 'Project1.exe') then begin // if you want your stuff to run in under-privileges user accounts, too, // you have to do write a little service for the NT family // an example for that can be found in the "HookProcessTermination" demo MessageBox(Handle, 'only users with administrator privileges can run this demo', 'information...', MB_ICONINFORMATION); ExitProcess(0); end;

The driver is configured with my hook dll's of course with madConfigDrv.

Yep, it worked, here's the screenshot. I run your demo with my driver + dlls.I don't sign dlls, and never did actually. The dlls that came with your demo wasn't signed as well, already checked that.I sign the drivers after configuring it, that is, after running madConfigDrv...

The extended validation certificates are there for Windows 10 SecureBoot compatability. But there's some discussion about whether they are needed at all. Microsoft is rather unclear about the exact needs. See more details in this long thread:

Looks like I found a solution, maybe someone will find it useful. The trick is to use 32 bit windows, not 64 bit. Also I tested only on Windows 7 (with Driver Signature Enforecement disabled of course) and it works. Looks like that's the ideal OS for madcodehook development