I’ve a pure KMDF control device driver, no hardware behind.
It is installed in Device Manager as “Legacy” hardware.
Problem: when I update the driver in DM, always a reboot is needed.
After “Driver update” in DM, I see that EvtDriverUnload is called,
and according to the windbg module list, the driver is indeed unloaded.
What else could require a reboot ?
Don’t use device manager to manage a non pnp driver. Use sc.exe
Bent from my phone
From: xxxxx@lists.osr.com on behalf of xxxxx@t-online.de
Sent: Monday, February 13, 2017 7:38:21 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] Device Manager Driver update - driver unloaded but reboot needed
I’ve a pure KMDF control device driver, no hardware behind.
It is installed in Device Manager as “Legacy” hardware.
Problem: when I update the driver in DM, always a reboot is needed.
After “Driver update” in DM, I see that EvtDriverUnload is called,
and according to the windbg module list, the driver is indeed unloaded.
What else could require a reboot ?
—
NTDEV is sponsored by OSR
Visit the list online at: http:
MONTHLY seminars on crash dump analysis, WDF, Windows internals and software drivers!
Details at http:
To unsubscribe, visit the List Server section of OSR Online at http:</http:></http:></http:>