Windows System Software -- Consulting, Training, Development -- Unique Expertise, Guaranteed Results
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/
Hello.
Tell me, for what reasons can the driver be restarted?
There is an OS filter driver that is periodically run twice (not on all computers). The previous driver works, when new instance start. I added logs, I see that the "wmiprvse.exe" process starts it. The computer does not enter sleep mode, and external media is not mounted or unmounted.
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 | 2 August 2021 | Live, Online |
Kernel Debugging | 27 Sept 2021 | Live, Online |
Comments
A filter writer is at complete liberty to write an application to start and stop their filter.
A quick google says that WMI is exactly the sort of filter that would come and go.
But are we not gluing wings on the pig? What's the problem you are having?
The problem is that more than one instance of the driver is running. For example: OS is starting -> driver is loaded -> OS working (driver not unloaded it is running) -> sometimes new instance is loaded again. I don't expect this behavior. If it is correct good. But I want to have a chance to prevent loading driver if it was run earlier. How to achieve it?