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/
We have a driver with a minor modification we're trying to run through attestation. We haven't made changes to the .inf for a very long time. The last time we attestation signed was last Feb (2022). Now the validation process of attestation fails with an error indicating "Found legacy AddReg operation defining co-installers (CoInstallers32)".
Has this enforcement changed since last Feb?
What's the preferred path forward for a device that requires this coinstaller?
I was under the impression this was only an issue when the Target Platform is Universal. Our target platform is "Desktop".
If you must know, the need for the coinstaller is because this particular device has multiple serial ports. The enumeration happens in an arbitrary order, but for our closed system I'd like to ensure COM numbers are associated with their corresponding physical location. My coinstaller cycles through the claimed com ports, releases them, then claims them in the appropriate order for each device.
|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||13-17 May 2024||Live, Online|
|Developing Minifilters||1-5 Apr 2024||Live, Online|
|Internals & Software Drivers||11-15 Mar 2024||Live, Online|
|Writing WDF Drivers||26 Feb - 1 Mar 2024||Live, Online|