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/
I am new to the USB driver development/analysis, I have extracted the etl logs and below are the TraceView logs
00000152 vmusb 4 772 0 0 02\07\2019-06:49:46:231 Set instance ID: 858508856766, unique: 1
00000153 vmusb 4 772 0 0 02\07\2019-06:49:46:231 Set text description, language: 0x409, device: XYZ_Android, location: Port_#0001.Hub_#0025
00000154 vmusb 4 772 0 0 02\07\2019-06:49:46:231 Registered IO internal control preprocessor for manual rejection, PlugNo: 5
00000155 vmusb 4 772 0 0 02\07\2019-06:49:46:231 WdfDeviceAddQueryInterface succeed, status: 0x0
00000156 vmusb 4 772 0 0 02\07\2019-06:49:46:231 Using a power managed queue, PlugNo: 5
00000157 vmusb 4 772 0 0 02\07\2019-06:49:46:231 Unknown( 24): GUID=51526c19-3dac-91c5-c442-f657fec1726a (No Format Information found).
00000158 vmusb 4 772 0 0 02\07\2019-06:49:46:231 Unsupported interface type (passing onto framework), GUID: b8e992ec-a797-4dc4-884684d041707446, version: 1
To my understanding it looks like, windows driver (from system process ID 4) is giving the call to my driver, however it seems like the interface is not implemented in our driver.
Could someone please provide more info on this.
Any help would be much appreciable.
|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!||Kernel Debugging||30 Mar 2020||OSR Seminar Space|
|Developing Minifilters||15 Jun 2020||LIVE ONLINE|
|Writing WDF Drivers||22 June 2020||LIVE ONLINE|
|Internals & Software Drivers||28 Sept 2020||Dulles, VA|