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/
Our QA were testing the driver under development and when a long stress test failed for a different reason they suddenly found tested driver was replaced by older version from WU. This one is WHQLed of course and tested driver was only signed by company certificate.
I'm checking WU and Setup API logs and can't find a reason why it happened. It is clear WU agent did it but why? I admit I can be missing something in WU log as it is almost unreadable, installation package is serialized and deserialized many times and the log has almost 60k lines in two days. So maybe there is a reason logged and I just can't see it. Seems to me like standard WU, package was downloaded and installed later.
Well, maybe it is supposed to work this way but it looks crazy to me. Any idea?
To be exact, this is what happened:
I'm under impression this should not happen and there was some event which led to it. But I'm really unsure as WU is so screwed in Win10 I can't exclude intention.
|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!|
|Developing Minifilters||24 May 2021||Live, Online|
|Writing WDF Drivers||14 June 2021||Live, Online|
|Internals & Software Drivers||27 September 2021||Live, Online|
|Kernel Debugging||15 November 2021||Live, Online|