This is a static archive of our old Q&A Site. Please post any new questions and answers at ask.wireshark.org.

# Wireshark fails to start on Windows 10

 0 The dumpcap process is the user mode application that is started by Wireshark (or tshark) to discover and capture from the network interfaces on your machine, usually via the WinPcap driver.Unfortunately for you (@NRGfxIT), and a very small number of other folks, there appears to be some issue in your environment that causes the call into WinPcap to hang, which then blocks the dumpcap process. I suspect something in the network stack on your machine, possible VPN or Endpoint protection software causes this. Unfortunately debugging this remotely is near impossible.You may want to try replacing WinPcap with the likely replacement for it, npcap as npcap has moved to a more modern driver mechanism within Windows, so may not suffer the issue you have.To install npcap, uninstall WinPcap, reboot, and then install npcap in WinPcap compatibility mode. You can then install Wireshark again, which should behappy to use the newly installed version of npcap.answered 02 Mar '16, 03:37grahamb ♦ 19.8k●3●30●206 accept rate: 22%I'm having the same problem now after upgrading wireshark to the latest version yesterday. It was working before that, and as part of the upgrade process I didn't upgrade WinPCAP (already had the latest version). I think there's something else going on here.(21 Apr '16, 04:11) robert_Can you ensure no dumpcap processes are running, terminate then if there are, and then let us know what happens when running path\to\dumpcap.exe -D from a command prompt?(21 Apr '16, 05:16) grahamb ♦One day later (with no intervention other than a reboot) and it's working again. Glad I didn't go through the rigmarole of installing ncap :-) By the way, output of dumpcap was 1. \Device\NPF_{4799958E-76F0-491A-9229-12E9ABCD8B4F} (Ethernet)(22 Apr '16, 00:58) robert_