The free OSR Learning Library has more than 50 articles on a wide variety of topics about writing and debugging device drivers and Minifilters. From introductory level to advanced. All the articles have been recently reviewed and updated, and are written using the clear and definitive style you've come to expect from OSR over the years.
Check out The OSR Learning Library at: https://www.osr.com/osr-learning-library/
KB4579311 lists the following known issues:
When installing a third-party driver, you might receive the error, “Windows can’t verify the publisher of this driver software”. You might also see the error, “No signature was present in the subject” when attempting to view the signature properties using Windows Explorer. This issue occurs when one or more of the following is present in a driver package:
- An improperly formatted catalog file is identified during validation by Windows. Starting with this release, Windows will require the validity of DER encoded PKCS#7 content in catalog files. Catalogs files must be signed per section 11.6 of describing DER-encoding for SET OF members in X.690.
- A driver catalog file extension is not one of supported extensions.
I'm not worried about the second, assuming that I'm correct that this means having something other than ".cat" as your catalog file extension. As a driver developer, however, the first has me baffled from an actions-to-take standpoint. Is this caused by using an older version of inf2cat or signtool? Is this caused by improperly using those tools? Is there some way I can verify that a large number of drivers will or will not be impacted by this without just going and installing all of them on a system on which this KB has been installed?
|Upcoming OSR Seminars|
|OSR has suspended in-person seminars due to the Covid-19 outbreak. But, don't miss your training! Attend via the internet instead!|
|Writing WDF Drivers||7 Dec 2020||LIVE ONLINE|
|Internals & Software Drivers||25 Jan 2021||LIVE ONLINE|
|Developing Minifilters||8 March 2021||LIVE ONLINE|