I'm using TCPView 4.16 for Windows 10 (downloaded from ). 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. Here's how it looks like:
I've searched online but resources on people with this same problem are sparse and with no resolution. Running as administrator or not makes no difference, issue still happens in either case. 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.
As 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 . 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 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. Has this happened to anyone else, and/or does anyone know what i could try to fix this?
71 Answer
TCP View and other networking tools use Windows built in networking.
When that fails to work for all applications, the best and usually fastest / easiest correction is a Windows Repair Install.
For Windows 10:
Go to the Media Creation Link:
Windows 10 is running, so click on the Download button (not Upgrade Button) and select Run.
This will launch the Repair and proceed normally.
Begin with the first option to Keep Everything. There are more aggressive options if that fails. It should work however.
In this case, as in many, a Repair Install is a good, sturdy repair that leaves your system as it was when you started the Repair.
2
