Investigate PnP notifications for device removal to improve Npcap upgrades
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 3.6k
- Forks
- 592
- PR merge metrics
- No merged PRs in 30d
Description
Right now, we rely on killing processes that have open handles to the Npcap driver's device before we try to stop the driver service, since the driver won't actually unload until all the handles are closed. We may be able to leverage Windows PnP infrastructure to either force these handles to close or allow us to update the driver at the next reboot. Ref: https://docs.microsoft.com/en-us/windows-hardware/drivers/kernel/pnp-notification-overview
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the Npcap upgrade path that kills processes holding driver-device handles, then read the linked Windows PnP notification overview. Determine whether PnP can close the handles or defer the driver update until reboot, and define a validated upgrade behavior before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100