On Windows XP systems, TCPView shows the name of the process that owns each endpoint. TCPView updates every second by default, but you can use the Options|Refresh Rate menu item to change the rate. Endpoints that change state from one update to the next are highlighted in yellow those deleted are shown in red, and new endpoints are shown in green. You can close established TCP/IP connections (those labeled with a state of ESTABLISHED) by selecting File|Close Connections or right-clicking on a connection and choosing Close Connections from the resulting context menu. I would drop using it altogether, but I find the filtering and UX a lot better/more friendly in TCPView so I'd like to be able to keep using it somehow.You can save TCPView's output window to a file using the Save menu item. Moreover, when using a similar app like CurrPorts, that one shows the addresses just fine - so i suppose it's not something wrong with my system, but with TCPView specifically. I've tried purging every entry of TCPView from the registry (it doesn't install so I can't uninstall it), redownloading, I've tried using an older version (4.0), and the problem is still there - I simply can't get it working again.Īs added info, after a PC reboot it does show the addresses immediately after I first open it for about 3-4 seconds, then it defaults back to showing :: or ::1.

Running as administrator or not makes no difference, issue still happens in either case. I've searched online but resources on people with this same problem are sparse and with no resolution. Up until a few days ago it worked fine, but all of a sudden it simply stopped showing addresses, and instead showing either :: or ::1. I'm using TCPView 4.16 for Windows 10 (downloaded from ).

Tcp view download