The reason the counts reappearred as noted in the previous post is because the steps mentioned in the link in the previous post includes automatically restoring files that shouldn't have disappeared.like fastprox.dll. This manual covers the PMEUCM TCPOPEN custom application and installation procedures. So, at least in my case, the lack of byte/packet counts under TCPView was caused by the renaming of fastprox.dll. Threats include any threat of suicide, violence, or harm to another. This was tested multiple times back and forth. Harassment is any behavior intended to disturb or upset a person or group of people. When I 'fixed' Portal 2 by renaming fastprox.dll, TCPView broke. Today I did after thinking about this weirdness and it broke. When I made the previous post noting I was getting byte/packet counts again after months with tcpview, I hadn't tried out Portal 2 again. This works great for game playing and is what I did months ago.īut that might (apparently) breaks some WMI functionality. The tcpview.exe is an executable file on your computers hard drive. As such, the fix for the Steam game(s) is to rename the 'fastprox.dll' file to something else (that is, remove the file essentially). If this file exists then at least SOME Steam games cease to work with a shaderapidx9.dll error - in particular in my case, the Portal 2 game ceases to work.

Okay, I found the problem with byte and packet counts not appearing under TCPview. Subject: TCPView is not showing Sent/Received bytes

Tcpview exe application error