 | 1 | initial version |
This is probably an issue with Npcap, as a result of it installing its own driver into the Windows networking stack (which is a requirement for packet capture).
It's been reported on the Nmap issues list (Nmap, not Npcap, as Npcap is part of the Nmap project and, although it has its own repository, it doesn't have its own issues list).
File your report there, unless you find a report that's close enough that it's probably the same issue - in which case you should probably still give your details, so the Npcap developers have as much information as possible to try to diagnose this.
| | 2 | No.2 Revision |
This is probably an issue with Npcap, as a result of it installing its own driver into the Windows networking stack (which is a requirement for packet capture).
It's been reported on the Npcap issues list and perhaps also on the Nmap issues list (Nmap, not Npcap, as Npcap is part of the Nmap project and, although it has its own repository, it doesn't have (Npcap only recently got its own issues list; the Nmap list was used before that, but new Npcap issues should be reported on the Npcap list, not on the Nmap list).
File your report there, unless you find a report that's close enough that it's probably the same issue - in which case you should probably still give your details, so the Npcap developers have as much information as possible to try to diagnose this.
