Closed Flerov closed 1 year ago
Im completly stuck. Since the newest version apparently get loaded I was checking also with WinDbg (of course with the debug masks set) but no messages. With WinObj though I could validate that the device name was registered, still I can not create a Handle to the driver.
I'm trying to load the driver with OSM on my win10 Build19041 VM in testsigning mode. This is the first driver I encounter where this Error-Message is being presented. I used the 2.0 Release. Think is when I use the newest 3.0 Release or the older one. The driver will be "loaded" but I can neither interact to it nor do I see any Messages in DbgView...
I already tried to compile the driver myself. I changed some things like TargetVersion, and the signing certificate (to TestSign, and removed the preset value) nothing helps.
Any tips appreciated