`Bcdedit.exe -set TESTSIGNING ON` so this shouldn't be a signing issue. The Select Network protocol dialog finally recognizes "This driver has an Authenticode(tm) signature", but I now get the error "Could not add the requested feature. I add CatalogFile entries to muxp.inf and mux_mp.inf and add a Package project to the solution. I still get the "The driver is not digitally signed!" warning and 0圎000022F error. I digitally sign the driver with a SHA256 cert and Microsoft at the root of the trust chain `signtool verify /kp mux.sys` reports successfully verified. The Select Network Protocol dialog warns "Windows reports The driver is not digitally signed!" When I install anyway, I get the error "Could not add the requested feature: The error is 0圎000022F" I compiled the Release|圆4 configuration andįollowed the installation instructions per While investigating why my intermediate driver is no longer working on Windows 10, I first tried getting the network\ndis\mux to work (from
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |