https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14101
--- Comment #11 from Christopher Maynard <christopher.mayn...@igt.com> ---
(In reply to LorenAmelang from comment #10)
> Happened to notice this today:
> https://github.com/nmap/nmap/issues/757
> "It means that you didn't uninstall WinPcap 4.1.3 thoroughly last time. And
> its DLLs (wpcap.dll, Packet.dll) still remain in C:\WINDOWS\System32 (and
> also C:\WINDOWS\SysWOW64 for 32-bit apps)."
>
> I have C:\Windows\SysWOW64, but none of the WinPcap files in it. Guess that
> wasn't the source of the errors.
Thanks for this reminder to check in C:\Windows\SysWOW64\ for WinPcap remnants
too. My system didn't have any WinPcap leftovers there, but others might.
> Looks like the reinstall worked in ways the error install didn't, even
> though Wireshark could capture despite the errors. Looking back at the
> install logs, I suspect the errors reported during the first install
> prevented the WlanHelper from working. There was no "System error 2" today.
>
> Guess my card just isn't monitor compatible.
It seems that only a very limited number of cards are supported (mine isn't
either) or due to "These features are part of the "Native 802.11 WLAN"
interface, which is deprecated in Windows 10." (See:
https://secwiki.org/w/Npcap/WiFi_adapters) With so few cards supported on
Windows 10, I can't help but wonder why Riverbed decided to stop
producing/supporting their AirPcap adapters. It seems like there'd still be a
market for them.
All this discussion aside, I'm still not sure what the status of the bug should
be. My feeling is that there's nothing Wireshark can do here, so I don't see a
good reason to keep this bug open.
(In reply to Guy Harris from comment #5)
> And for Npcap issues, the right place to report *them* is
>
> https://github.com/nmap/nmap/issues
For me, it would seem to make more sense to close this bug as NOTOURBUG and
then for someone to open an issue with nmap for any behavioral changes or fixes
they'd like to see with npcap.
--
You are receiving this mail because:
You are watching all bug changes.
___________________________________________________________________________
Sent via: Wireshark-bugs mailing list <wireshark-bugs@wireshark.org>
Archives: https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe
