I do not have enough "karma" to upload files, so no screenshots, sorry.... I was running wireshark fine with NPCAP just a week ago. This morning starting it as administrator it shows no interfaces to be selected for capture. I Uninstalled it. Made sure every program data/program files forlder where removed, rebooted, reinstalled ( it detected npcap during install), rebooted, started as administrator... Same problem. If I use rawcap I can see these interfaces:
I'm using windows 8.1 64 bits and wireshark 2.0.2 for win64. Any idea, so far i'm simply using rawcap to save to a file I open with wireshark, but it is annoying. Trying to build on the first answer. I uninstalled NPCAP, then removed the driver service as follows:
I had to remove two of them oem12.inf and oem16.inf from Insecure.Com LLC. Then I rebooted, ran iterativelly CCLeaner just to get rid of some registry keys in any case then reinstalled the latest version of NPCAP as admin. ===> It “fails to install driver service”… asked 11 Mar ‘16, 01:05 rapha edited 11 Mar ‘16, 04:55 |
2 Answers:
The enumeration of interfaces isn't handled by Wireshark at all, rather the capture mechanism, which in your case is npcap or WinPcap, so reinstalling Wireshark isn't likely to help. Presumably you're using npcap as you wish to capture on the loopback interface. If not, you might better off using WinPcap at the moment. Which version of npcap are you using? Try uninstalling npcap, reboot, check for traces, e.g. %WINDIR%\System32\Drivers\npcap.sys or npf,sys, and then reinstall. answered 11 Mar '16, 02:27 grahamb ♦ |
Hi. Please try the latest Npcap 0.06 R10 here: https://github.com/nmap/npcap/releases Don't change options if you don't know what they mean. Let me know if there're any issues. answered 18 Mar '16, 18:02 Yang Luo |
Thanks, I'm indeed debugging a client server program locally this is why I need the loopback. I edited my question.
There have been some ongoing issues for some when installing npcap which haven't yet been resolved. A more appropriate forum for npcap issues would be the nmap dev mailing list.
thanks, I'll check there. So far, I have my workaround with rawcap.