During our installation process, we noticed if the existing KMDF coinstaller version on the system is older than the newer one(our driver coinstaller in CD), the OS installs the newer version but never starts our KMDF driver until next reboot. This causes some issues in our installation process, because there are other driver components that rely on this KMDF driver to be loaded and started before they get installed. Basically our installation process is failing. After reboot, the KMDF driver started loading but missing with other drivers. One more installation solves the problem after reboot. But we wouldn?t want our end customer to run the installation process twice. We need your feedback and advise.
Is it possible to start our KMDF driver without rebooting the system in first phase?
Can we upgrade the KMDF coinstallers separately, like through MSI etc.
Hi,
The reason that you see the reboot is indeed that the version of KMDF that your driver needs is not installed in the system. The only way to install KMDF without a reboot is to unload all KMDF drivers, install the framework and then pray that everything will come back up. So, to answer your questions:
No
You can take a look at the nonpnp sample in the WDK. Basically in the sample you need an application that will load the coinstaller as a dll and will call some export functions that install the framework. The export function’s return value will tell you, if a reboot is required or not, but you are handling the reboot yourself. However, even in this scenario, if a reboot is required, then your driver will not load unless you reboot (i.e. you can suppress the reboot for as long as you want, but your driver will not load unless you do so).
I also have 1 question:
What does it mean that “the KMDF driver started loading but missing with other drivers”? If there are dependencies between your KMDF driver and with other drivers, then your KMDF driver needs to be in a loadgroup that loads before the rest of your drivers. If you do so, I suspect that this will solve your problem.
Ilias
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@yahoo.com
Sent: Thursday, February 18, 2010 1:44 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] KMDF driver installation requires a reboot (Version mismatch).
Hi
During our installation process, we noticed if the existing KMDF coinstaller version on the system is older than the newer one(our driver coinstaller in CD), the OS installs the newer version but never starts our KMDF driver until next reboot. This causes some issues in our installation process, because there are other driver components that rely on this KMDF driver to be loaded and started before they get installed. Basically our installation process is failing. After reboot, the KMDF driver started loading but missing with other drivers. One more installation solves the problem after reboot. But we wouldn?t want our end customer to run the installation process twice. We need your feedback and advise.
Is it possible to start our KMDF driver without rebooting the system in first phase?
Can we upgrade the KMDF coinstallers separately, like through MSI etc.
> “What does it mean that “the KMDF driver started loading but missing with other
> drivers”?”
Yes the other drivers have dependency with KMDF driver.
Currently we are thinking of displaying a message saying reinstallation required after a reboot (only when the current system version < CD version). Needs to look and investigate your option…
wrote in message news:xxxxx@ntdev… > Hi > > During our installation process, we noticed if the existing KMDF coinstaller version on the system is older than the newer one(our driver coinstaller in CD), the OS installs the newer version but never starts our KMDF driver until next reboot. This causes some issues in our installation process, because there are other driver components that rely on this KMDF driver to be loaded and started before they get installed. Basically our installation process is failing. After reboot, the KMDF driver started loading but missing with other drivers. One more installation solves the problem after reboot. But we wouldn?t want our end customer to run the installation process twice. We need your feedback and advise. > > 1) Is it possible to start our KMDF driver without rebooting the system in first phase? > 2) Can we upgrade the KMDF coinstallers separately, like through MSI etc. > > > thanks > >
Of course this requires modifying the build templates for KMDF drivers
as those push you to link against the current (for that WDK) KMDF
version.
Mark Roddy
On Mon, Feb 22, 2010 at 9:57 AM, wrote: >
> > EXACTLY what I was going to say. ?Then… problem solved. ?Sort of. > > Peter > OSR > > > > — > NTDEV is sponsored by OSR > > For our schedule of WDF, WDM, debugging and other seminars visit: > http://www.osr.com/seminars > > To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer >
wrote in message news:xxxxx@ntdev… > Hi > > During our installation process, we noticed if the existing KMDF > coinstaller version on the system is older than the newer one(our driver > coinstaller in CD), the OS installs the newer version but never starts our > KMDF driver until next reboot. This causes some issues in our installation > process, because there are other driver components that rely on this KMDF > driver to be loaded and started before they get installed. Basically our > installation process is failing. After reboot, the KMDF driver started > loading but missing with other drivers. One more installation solves the > problem after reboot. But we wouldn?t want our end customer to run the > installation process twice. We need your feedback and advise. > > 1) Is it possible to start our KMDF driver without rebooting the system in > first phase? > 2) Can we upgrade the KMDF coinstallers separately, like through MSI etc. > > > thanks > >