TCPView
Identify which Windows processes own TCP and UDP endpoints with TCPView. Understand connection states, display colors, saved snapshots, and investigation limits.
- Purpose
- Network connection inspection
- Vendor
- Microsoft Sysinternals
- License model
- free
- Platforms
- Windows
- Testing status
- Editorially researched
Documentation research is not a measure of detection or cleanup effectiveness.
TCPView is a Microsoft Sysinternals utility that associates Windows network endpoints with their owning processes. It helps answer which application is connected, what addresses are involved, and how a TCP connection’s state changes while you watch.
Use it to investigate a concrete network question, such as activity that continues after a known application’s window closes. It is not a firewall, packet-content analyzer, or malware-removal scanner. A remote address in a list is an observation, not a verdict about the program that contacted it.
Documented version and endpoint view
The official TCPView page, checked on 6 October 2026, lists version 4.19, published on 11 April 2023. It documents TCP and UDP endpoint listings, owning processes, local and remote addresses, and TCP connection states. Tcpvcon is the companion command-line utility, with CSV output among its options.
The published requirements list Windows 8.1 or newer and Windows Server 2012 or newer. That older compatibility statement does not establish that the operating system still receives security updates. Microsoft’s Windows 10 lifecycle notice is a separate support consideration. Use a supported, maintained Windows installation.
Obtain the utility through Microsoft and check the current help before using controls. This article reports the published requirements and feature description; it does not claim a fresh test on every listed release.
Read addresses and colors in context
Microsoft documents a regularly refreshed list, address-name resolution that can be toggled, and colors for new, changed, or removed endpoints. Those colors describe changes between refreshes, not a threat score. Red does not mean a connection was malicious, and green does not certify safety.
| Observation | Useful interpretation | Unsupported conclusion |
|---|---|---|
| Owning process | A candidate application to investigate | Its name proves it is legitimate |
| Remote address or resolved name | The endpoint shown at that time | Every connection to it has the same purpose |
| Listening endpoint | A local endpoint awaiting traffic | Someone has successfully accessed the computer |
| Established TCP connection | A connection currently in that state | Its contents are safe or malicious |
| Endpoint disappears | It left the refreshed view | The underlying application was removed |
Compare resolved names with numeric addresses when recording a finding. A name can help orient the investigation, but hosting services and shared infrastructure make a destination alone insufficient to explain intent. Keep the owning application, time, and action you were performing in the same note.
A bounded network investigation
Begin with a known application and expected action. Observe the endpoint list before opening the application, during the action, and after closing it normally. Keep changes separate from interpretation: activity may belong to a helper, updater, or background component even when the main window is gone.
Select the relevant process rather than treating the entire list as suspicious. Use Process Explorer to investigate the running program’s resources, and Autoruns if the question becomes why it starts at sign-in. Similar names and rapidly changing instances can confuse ownership, so reconfirm the current instance before taking action.
Do not open a suspicious attachment or visit an unsafe site to make a connection appear. If you already have strong evidence of compromise, follow the diagnostic guide and prioritize appropriate containment and supported scanning. Live observation should not prolong an incident simply to collect more rows.
Closing a connection and saving a snapshot
Microsoft documents closing established TCP connections and saving the displayed output. Closing a connection can interrupt a download, call, application session, or remote administration. Establish who owns it and what will be affected first; on a managed computer, use the administrator’s process.
An application may reconnect after a connection is closed. This action does not create a persistent firewall rule, remove the process, or eliminate startup entries. If the goal is changing an application’s network access, use the supported application or firewall configuration rather than repeatedly closing its sessions.
Treat a saved output file as a snapshot of the view, not a full history or packet capture. Include the time and reproduction note. An endpoint absent from the snapshot may have existed before or between observations. Network details can reveal private services or infrastructure, so inspect records before sharing them through a support channel.
Keep protection and diagnosis separate
For an actual security alert, inspect the relevant antivirus history and follow its remediation workflow. Microsoft’s Windows Security settings guide explains the separate provider view. TCPView’s moving list is not evidence that antivirus protection is enabled.
Use Process Monitor for a different question about file or Registry activity. This TCPView profile is documentation research checked on 6 October 2026. No packet experiment, malware diagnosis, detection-rate measurement, or independent performance test was performed. See the methodology for the research criteria.
Reasons to consider it
- Associates current endpoints with owning processes
- Local snapshots and a command-line companion support investigation
Limitations to understand
- Endpoint listings do not reveal packet contents or establish malicious intent
- Closing a connection is temporary and can interrupt legitimate work
Sources & documentation
Sources checked on 6 Oct 2026. Documentation research does not establish independent testing.
No affiliate links are included in this build. Read our disclosure.