Recently i've seen that soon after beginning a capture, wireshark stops responding and I can't use any of the functions. I've installed the most recent stable version (2.2.7) 64-bit for Windows 10 and re-installed WinPCAP, but this didn't fix the problem. Any ideas? asked 15 Jun '17, 12:21  jkoelker |
One Answer:
I would probably reinstall the whole thing (such as follow the uninstall manual) and reinstall. answered 17 Jun '17, 12:33  shr00msz Thanks - I've tried doing that a couple of times but it hasn't resolved the problem. I even downloaded and installed an older version thinking that might help, but it didn't. Having run wireshark on another computer without issue, I have to conclude that this is likely a problem with my particular machine - maybe some sort of registry setting that's got a bit flipped. Not a huge deal - I'll be replacing this laptop in the near future anyway. Thanks. (19 Jun '17, 05:20) jkoelker Alright, If your later laptop doesn't work, it might be wireshark's end, or maybe some compatibility issue. (19 Jun '17, 19:00) shr00msz |
Do you have a rough idea of what amount of traffic is passing through the interface at which you capture? What happens if you capture with a highly restrictive capture filter such as
icmp, and then you ping some address so that at least something is captured?Incidentally, there is also an answer to another question which may be an answer to yours as well.