Windows System Software -- Consulting, Training, Development -- Unique Expertise, Guaranteed Results

Before Posting...
Please check out the Community Guidelines in the Announcements and Administration Category.

More Info on Driver Writing and Debugging

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:

Restrict driver to non-Windows 10

jfbjfb Member Posts: 1


I have a USB serial (CDC) driver I've written and used for some time. I no longer need it for Windows 10 users, as the built-in driver works fine.
How do I mark it such that, on an upgrade, Windows will use its own driver instead of my driver? Right now, as I am signing it for earlier versions, they get issues with attestation signing.




  • Peter_Viscarola_(OSR)Peter_Viscarola_(OSR) Administrator Posts: 7,887

    Hmmmmm... I’m not aware of any way you can make the driver not install for a newer version of the OS if a user explicitly tries to install it.

    You can, of course, check the OS version in DriverEntry, log an entry in the event log, and fail. That doesn’t seem like a great option.

    If what you really care about is people using Windows Update (aka WU) and you want to automatically have that “do the right thing” that is certainly part of the process. You can set what are called “floor” and “ceiling” versions of Windows to which your driver applies.

    But in terms of a normal INF, I’m not aware of any way it can refuse to install based on specific version limits.


    Peter Viscarola

  • Andy_MoretonAndy_Moreton Member Posts: 11

    How to do this is documented twowards the end of

    If you want an INF to explicitly exclude a specific operating system version, product type, or suite, create an empty INF Models section. For example, an empty section named [FooMfg.NTx86.6.0] prohibits installation on x86-based operating system versions 6.0 and higher.

  • Peter_Viscarola_(OSR)Peter_Viscarola_(OSR) Administrator Posts: 7,887

    Thank you, Mr. Moreton!

    I (obviously) had no clue this type of functionality was possible using section decorations in an INF.

    Easy awesomeness.

    Peter Viscarola

  • MBond2MBond2 Member Posts: 139

    Cool, but probably unhelpful for the OP though. if he had to develop a driver in the past, but now an in box one does the job, there will be an existing INF that does not have this section deployed into the wild. likely no easy way to go back in time and add that to the already released versions

  • Eric_WittmayerEric_Wittmayer Member Posts: 49

    Could you release a new INF only driver for Win10 using Windows update that had the blank section?

Sign In or Register to comment.

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

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