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

Home› NTDEV

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: https://www.osr.com/osr-learning-library/


Why does NDIS driver require reboot on installation?

Shane_CorbinShane_Corbin Member Posts: 284
in NTDEV

I've got an installer that installs a collection of drivers. When a new NDIS driver is included the installer requires a restart. It's an annoyance I've "dealt with" for some time, but never truly understood. Could anyone suggest some pointed areas for troubleshooting (or eliminating) the need to restart?

· Share on Facebook

Comments

  • Doron_HolanDoron_Holan Member - All Emails Posts: 10,706

    what does setupapi.dev.log say about the install and the reboot? there are typically clues there as to which driver failed to unload or vetoed the operation.

    d
    · Share on Facebook
  • Shane_CorbinShane_Corbin Member Posts: 284

    I can't be certain, but this looks like a potential indication:
    "Device pending start: Device has problem: 0x38 (CM_PROB_NEED_CLASS_CONFIG), problem status: 0x00000000."

    I found this information regarding that particular problem:
    https://docs.microsoft.com/en-us/windows-hardware/drivers/install/cm-prob-need-class-config

    It's possible this issue could be resolved with some .inf modifications?

    · Share on Facebook
  • Doron_HolanDoron_Holan Member - All Emails Posts: 10,706
    Most likely NOT the reason for the reboot. As you see in the docs, it is a transient error state which essentially means pnp has finished the declarative part of the install, started the device and is now triggering a service to perform runtime setup of the device. Look for case insensitive “reboot” in the log.
    d
    · Share on Facebook
Sign In or Register to comment.

Howdy, Stranger!

It looks like you're new here. Sign in or register to get started.

Sign In Register
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!
Internals & Software Drivers 7 February 2022 Live, Online
Kernel Debugging 21 March 2022 Live, Online
Developing Minifilters 23 May 2022 Live, Online
Writing WDF Drivers 12 September 2022 Live, Online

Categories