nmap / nmap/npcap

Npcap Bug Report

Open
#693 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
3.6k
Forks
592
PR merge metrics
No merged PRs in 30d

Description

https://pacificlegalfoundation-my.sharepoint.com/:u:/g/personal/rbrown_pacificlegal_org/EeJQzeqtvbREiX5wnXaQOCYBHgfD-tpzSz2T16atGvrcXA?e=UZ7qjO

I have a user who is experiencing BSOD. I've also tried to update to the newest version after I unistalled current version, but I onyl see 1.60 on her computer.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Begin with the linked SharePoint report and the Npcap version information in the issue; confirm what BSOD and update symptoms are documented there. Done requires a reproducible failure or sufficient diagnostic details to identify whether the report concerns the BSOD, the version update, or both.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
networking, operating-systems
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.