Wireshark Not Responding

edit

Note that you really, really, really shouldn't run Wireshark with elevated privileges. Doing so allows full access to your machine from the hundreds of thousands of lines of code in Wireshark, driven by whatever packets are captured or read from possibly unsafe files.

Having to run Wireshark as Administrator is an indicator that something is broken in your installation.

Not enough "really"s here: really really really!

If you are not scared enough, read this waking up presentation. The essence is that dissectors are rarely written with security in mind, so they do not check packet data validity thoroughly enough. So if you feed one with some data it is not prepared to handle, you can trick it into executing a code inside these data, or merely dissect the contents of some packets differently from what they really contain. While you cannot prevent the attacker from hiding some packet contents from you by not running Wireshark as administrator, you can prevent him from installing malware on your system.

Got it. Dropped back to normal user mode when I got the firts warning, and I'm monitoring a local network, but thanks for you feedback.