by michel » Fri Jun 30, 2017 11:47 am
Me too I don't understand and as I always install the last madCodeHook available build, sign my drivers (and applications) with the same batch file and use the same signtool since my first usage of the library, I first suspected the missing of some certificates in clean Windows 10 versus Windows7 updated to Windows 10; but adding some certificates of my dev machine didn't solve the issue.
I confirm (I just verified and tested this) that build (done with the madCodeHook available at this date):
- in May 2016: loads the drivers on any versions of Windows
- in January 2017: doesn't load the drivers in clean Windows 10
- in June 2017 (with double signing and an updated signtool as the previous one doesn't support double signing): doesn't load the drivers in clean Windows 10
This issue is reported by a lot of users of our product, is reproduced in our main office and also on one of my computers.
I tested your distributed PrintMonitor on different machines:
- on my Win10 dev machine and some other ones it loads the drivers (no error message)
- on my clean Win10 machine the drivers are not loaded (pop up "error...", "loading driver failed") and, when the PrintMonitor is closed, are, as expected, not stopped ("error...", "stopping driver failed")
So your PrintMonitor driver behaves exactly as my drivers. They can't be loaded in clean windows 10!