how to fix wireshark no interfaces found

HOW TO FIX WIRESHARK NO INTERFACES FOUND INSTALL
HOW TO FIX WIRESHARK NO INTERFACES FOUND UPDATE
HOW TO FIX WIRESHARK NO INTERFACES FOUND DRIVER

Pcap_findalldevs_ex is what you call to find all the WinPcap compatible interfaces on the system. I know exactly which function call returned that message: pcap_findalldevs_ex Pressing the Refresh Interfaces button did not fix it. I fired up Wireshark and got the message 'No interface can be used for capturing in this system with the current configuration.'. Everything installed fine and WinPcap installed normally. On March 23 I upgraded 9926 to 10041 and then installed Wireshark 圆4 v1.12.4 from. Physical network adapter in the Shuttle is Generic Marvell Yukon 88E8056 based Ethernet controller. Network Adapter in the VM is in Bridged mode. Even the last version 9926 worked OK, but now we have a problem - a big problem.Ībout the test machine: Shuttle xpc, quad core cpu, 8GB RAM. Host OS is Windows 7 圆4. Windows 10 圆4 Enterprise 10041 is a guest OS running inside VirtualBox 4.3.26 r98988. Up until release 10041 all Windows 10 Tech Preview versions have appeared to run WinPcap 4.1.3 without a problem.

HOW TO FIX WIRESHARK NO INTERFACES FOUND UPDATE

Update 3-26-15: This has been confirmed by others and a thread has been started here: Update 3-27-15: Do you want to use Wireshark on Windows 10? Tweet about this problem! do a post about this issue.

HOW TO FIX WIRESHARK NO INTERFACES FOUND DRIVER

Another issue is driver signing: in Windows 10 圆4 that really will be changing, so it will be important for WinPcap to be updated before the RTM release - more about this here. Work has been done on this at NMAP and has been shared, so it would be great if could expand on that work and release WinPcap fully compatible with NDIS6.

But we still need to encourage Riverbed to update WinPcap from NDIS5 to NDIS6. Hopefully, this trend continues - but I wouldn't count on it. Update May 13, 2015: WinPcap 4.1.3 began to work again in Windows 10 preview 10061 and continues to operate in 10074. Hopefully, if someone else is experiencing this same pain with their previously working WireShark, these steps will help.Update June 5, 2015: WinPcap 4.1.3 works on build 10130. This may work with other versions of Windows (Windows 10, for example) but I have not personally tried it out.

HOW TO FIX WIRESHARK NO INTERFACES FOUND INSTALL

The install completed successfully and I was able to run WireShark and capture packets again. Then I downloaded the latest version of WireShark (version 2.2.2). When I installed WireShark, I made sure NOT to select the installation of WinPcap 4.1.3. First, I uninstalled WireShark (and WinPcap 4.1.3, the latest at the time of this writing) and rebooted. Feel free to modify these steps if you wish. I will list exactly what I did but there may be steps that are unnecessary for you. Enough about the failures, here’s to success! I tried running WireShark in compatibility modes for previous version of Windows – to no avail. I then tried going ever further back into the archives of old versions of WireShark.

My first attempts involved uninstalling and reinstalling, with reboots before and after. Let me share what I did to restore functionality and my sanity. When I checked Task Manager, a process called dumpcap.exe was not responding and like in the movies, hard to kill. I recently upgraded my instructor workstation and WireShark stopped working. I am a long time user of WireShark and I frequently use it for demonstrations in my networking classes.

How to fix wireshark no interfaces found