Revision history [back]

I'm running Windows 7 Home Premium, Wireshark 3.6.2 and NPCap 1.55. I used to be able to capture traffic on my Ethernet adaptor, but recently (having made no change that I know of other than updating from 3.6.1 to 3.6.2) Wireshark no longer displays the one-line summary pf packets as it is capturing, and the "Packets <n>" counter in the footer remains at zero.

I have confirmed that a .pcapng file is created in c:\users\<username>\appdata\temp, which seems to be normal behaviour, comparing with a Win10 PC that runs Wireshark fine. If stop capturing and open this file, it seems to display sensible traffic.

I have tried uninstalling Wireshark and then NPCap, deleting any remaining contents of c:\program files\wireshark, rebooting, and installing both NPCap and Wireshark from the Wireshark-win64-3.6.2.exe installation file, with NPCap using the default flags of

Restrict NPCap drivers access to Admins=unchecked Support raw 802.11 traffic for wireless adapters= unchecked Install NPcap in Winpcap API-compaible mode=unchecked

I have chosen not to install USBcap.

When I start to capture, Wireshark often displays "not responding" in the window title, and will not then respond to the red-square stop capture button or the X button in the top right of the window: I have to kill the process from Task Manager.

I've tried reinstalling 3.6.1, but that doesn't help. Something about the upgrade from 3.6.1 to 3.6.2 seems to have prevented me even being able to solve the problem by rolling back to an earlier version.

I'm running Windows 7 Home Premium, Wireshark 3.6.2 and NPCap 1.55. I used to be able to capture traffic on my Ethernet adaptor, but recently (having made no change that I know of other than updating from 3.6.1 to 3.6.2) Wireshark no longer displays the one-line summary pf packets as it is capturing, and the "Packets <n>" counter in the footer remains at zero.

I have confirmed that a .pcapng file is created in c:\users\<username>\appdata\temp, which seems to be normal behaviour, comparing with a Win10 PC that runs Wireshark fine. If I stop capturing and open this file, it seems to display sensible traffic.

I have tried uninstalling Wireshark and then NPCap, deleting any remaining contents of c:\program files\wireshark, rebooting, and installing both NPCap and Wireshark from the Wireshark-win64-3.6.2.exe installation file, with NPCap using the default flags of

Restrict NPCap drivers access to Admins=unchecked Support raw 802.11 traffic for wireless adapters= unchecked Install NPcap in Winpcap API-compaible mode=unchecked

I have chosen not to install USBcap.

When I start to capture, Wireshark often displays "not responding" in the window title, and will not then respond to the red-square stop capture button or the X button in the top right of the window: I have to kill the process from Task Manager.Manager. Even though the window becomes unresponsive, the .pcapng file still captures packets until I kill off the process.

I've tried reinstalling 3.6.1, but that doesn't help. Something about the upgrade from 3.6.1 to 3.6.2 seems to have prevented me even being able to solve the problem by rolling back to an earlier version. version.

I'm running Windows 7 Home Premium, Wireshark 3.6.2 and NPCap 1.55. I used to be able to capture traffic on my Ethernet adaptor, but recently (having made no change that I know of other than updating from 3.6.1 to 3.6.2) Wireshark no longer displays the one-line summary pf packets as it is capturing, and the "Packets <n>" counter in the footer status bar at the bottom of the window remains at zero.

I have confirmed that a .pcapng file is created in c:\users\<username>\appdata\temp, which seems to be normal behaviour, comparing with a Win10 PC that runs Wireshark fine. If I stop capturing and open this file, it seems to display sensible traffic.

I have tried uninstalling Wireshark and then NPCap, deleting any remaining contents of c:\program files\wireshark, rebooting, and installing both NPCap and Wireshark from the Wireshark-win64-3.6.2.exe installation file, with NPCap using the default flags of

Restrict NPCap drivers access to Admins=unchecked Support raw 802.11 traffic for wireless adapters= unchecked Install NPcap in Winpcap API-compaible mode=unchecked

I have chosen not to install USBcap.

When I start to capture, Wireshark often displays "not responding" in the window title, and will not then respond to the red-square stop capture button or the X button in the top right of the window: I have to kill the process from Task Manager. Even though the window becomes unresponsive, the .pcapng file still captures packets until I kill off the process.

I've tried reinstalling 3.6.1, but that doesn't help. Something about the upgrade from 3.6.1 to 3.6.2 seems to have prevented me even being able to solve the problem by rolling back to an earlier version.