7.12 crash about npcap HOT 7 CLOSED

@techtonik Did you perhaps not have WinPcap installed? We recently fixed some issues with Nmap on Windows related to --unprivileged and WinPcap/Npcap. One of them, 2c6666cb34, fixed a problem that could lead to a crash in a scan just like you used, but only if WinPcap was not installed.

Please try our latest Beta release, Nmap 7.25BETA2, which contains this fix. Let us know if this solves your problem or if you still have trouble. Full output with -d3 would be helpful in that case.

from npcap.

@dmiller-nmap yes, I was using npcap 0.09-r3 installed without reboot. Let me try this again with newer Nmap version.

from npcap.

Seems to work. At least doesn't crash now.

WARNING: Could not import all necessary Npcap functions.  You may need to upgrade to version 0.07 or higher from http://www.npcap.org.  Resorting to connect() mode -- Nmap may not fu
nction completely

Starting Nmap 7.25BETA2 ( https://nmap.org ) at 2016-09-08 09:44 E. Africa Standard Time
Initiating Parallel DNS resolution of 256 hosts. at 09:44

from npcap.

Please try Npcap 0.09 r4 here: https://github.com/nmap/npcap/releases

from npcap.

Since there's no feedback, I will close it for temporarily for now.

from npcap.

I'd say that NpcapHelper.exe asks for administrative permission too much - 4 times when Wireshark loads and once more during capture. Otherwise 0.09 r5 seems to work fine.

from npcap.

This issue has already been discussed here: https://github.com/nmap/nmap/issues/435. It's a low priority issue but already in our TODO list. For now, I will just recommend not to choose the Restrict Npcap driver's access to Administrators only option in installer if you are using Npcap with Wireshark.

from npcap.