install problem kernel dll windows 7

Hi experts,

I’ve been trying to develop inf to install a kernel driver (driver.sys) together with wrapper.sys an export driver / kernel dll. Its built with WDK 10 and VS2015 to target Win 7 – 10 for x32 & amd64 bit. The driver/dll are legacy WDM model. I’m using test signing with a self signed certificate (generated with Win 10 tools) and target in test mode.
It “appeared to install” in prototype form at home on Windows 10 x64. In the work environment Win 7 x32 test target, I have been struggling for days.

The only way I have been able to get it installed is to build the export driver as a static library and link it. When there is only one sys file to install (inx adjusted accordingly) it does install OK. This at least suggests that the certificates are properly in place on both development and target machines.

When built as a DLL however, the driver’s inf gets stamped, both driver and dll build, and a cat file is created, Driver and dll are both driver signed. The tools don’t give warnings, but the installer has a lower opinion of the resulting package. It objects that the driver may be corrupt, and doesn’t want to play.

I’ve been carefully round the loop enough times now to know that I’m doing what I’m intending - having carefully read & reread the protocols, but I’m obviously missing something critical, as I always get back to the same problem.

I’ve got two projects in the solution. The driver references and has dependencies on the DLL. One project builds to driver the other export driver. Only the driver has an inx file (dll inf2cat is skipped) both driver and dll specify the test cert.

It installs when the dll is repackaged and statically linked, so I guess that the problem is with setting up the cat, or signing for the DLL. [or setting up the driver project so that the cat is built properly with a dll present].

Does this sound familiar to anyone? I’d really appreciate it if somebody could cut through to the essence here, or point me at the build process description I need to focus on.

Many thanks

Jack

Sent from Mailhttps: for Windows 10</https:>

> When there is only one sys file to install (inx adjusted accordingly) it does install OK.

This at least suggests that the certificates are properly in place on both development
and target machines.

Rather than relying on the above behaviour, can you check the details to endure that when there are 2 .sys files, they are still similarly signed ? Also, it would be good to check that the following is installed in case your test certificate is SHA256 :
https://technet.microsoft.com/en-us/library/security/2949927.aspx