Windows 11 includes Pktmon (Packet Monitor), a built-in command-line network diagnostic utility that allows you to capture, monitor, and troubleshoot network traffic without installing third-party software. It is particularly useful for diagnosing connectivity problems, identifying communication failures, investigating DNS issues, and examining traffic between a computer and a specific server or network device. Pktmon can capture packets directly from network interfaces, apply filters to limit the traffic being recorded, and save captures for later analysis in Wireshark. All examples in this article use the Windows 11 Administrator Command Prompt.
1. Verify Pktmon and prepare for a capture
Open Command Prompt as Administrator and verify that Pktmon is installed by running pktmon help. You can also locate the executable using where pktmon. Before starting a capture, it is useful to identify the network adapters installed on the computer using pktmon comp list or ipconfig /all. Pktmon supports capture filters that allow you to narrow down the traffic being recorded, helping reduce the size of capture files and making troubleshooting easier. To see the available commands and options for your particular Windows 11 build, run pktmon start help, pktmon filter help, and pktmon stop help.
2. Capture traffic for a specific IP address or hostname
One of the most useful features of Pktmon is the ability to capture traffic associated with a particular IP address. For example, if you want to investigate communication between your computer and a server at 192.168.1.50, first remove any existing filters and create a new IP filter using pktmon filter remove followed by pktmon filter add -i 192.168.1.50. You can verify the filter using pktmon filter list. The IP filter captures packets to or from that address, regardless of direction. Pktmon does not support hostname-based capture filters directly. However, you can resolve a hostname to its IP address using nslookup server.example.com and then use that IP address in your Pktmon filter. For example, pktmon filter add -i 192.168.1.50 -t tcp captures TCP traffic associated with that server. You can also filter by port, such as pktmon filter add -p 443 to capture HTTPS traffic.
3. Capture traffic using a fixed file size
Pktmon supports a configurable maximum capture file size using the --file-size parameter. This is particularly useful when troubleshooting network problems that generate large amounts of traffic. For example, the following commands create a capture with a maximum file size of 100 MB:
mkdir C:\Captures
pktmon filter remove
pktmon filter add -i 192.168.1.50
pktmon start --capture --file-name C:\Captures\Server.etl --file-size 100 --log-mode circular --pkt-size 0
In this example, Pktmon captures complete packets (--pkt-size 0) and writes them to a file with a maximum configured size of 100 MB. The circular logging mode means that once the file reaches its maximum size, older captured traffic is overwritten by newer traffic. This is useful when you want to leave a capture running for an extended period while retaining the most recent network activity.
Microsoft Learn+1
4. Create multiple fixed-size capture files automatically
For longer troubleshooting sessions, Pktmon also supports multi-file logging. Instead of overwriting previously captured packets when the file reaches its configured size, Pktmon automatically creates another capture file. For example, the following command creates sequential capture files, each with a maximum configured size of 100 MB:
pktmon filter remove
pktmon filter add -i 192.168.1.50
pktmon start --capture --file-name C:\Captures\Traffic.etl --file-size 100 --log-mode multi-file --pkt-size 0
As the capture continues, Pktmon creates additional numbered ETL files when the size limit is reached. This allows you to preserve the entire troubleshooting session rather than losing older traffic. The multi-file option is especially useful when investigating intermittent connectivity problems, devices that periodically disconnect, or network issues that occur only after several hours. Keep in mind that multi-file logging can consume considerable disk space, so monitor available storage when running extended captures.
5. Stop, convert and analyze the captured traffic
When you have collected enough traffic, stop the capture by running pktmon stop. Pktmon saves its capture in ETL format, which can be converted into PCAPNG format for examination using Wireshark. For example, run
pktmon etl2pcap C:\Captures\Server.etl --out C:\Captures\Server.pcapng. You can then open the resulting PCAPNG file in Wireshark and use its familiar display filters to investigate DNS requests, TCP connection failures, retransmissions, DHCP traffic, and other network problems. For multi-file captures, convert each ETL file separately. You can also convert captures into readable text using pktmon etl2txt. This makes Pktmon a useful alternative to installing additional capture software on Windows 11 computers, particularly when you need to collect network evidence remotely or troubleshoot a problem using only built-in Windows utilities.
pktmon etl2pcap C:\Captures\Server.etl --out C:\Captures\Server.pcapng. You can then open the resulting PCAPNG file in Wireshark and use its familiar display filters to investigate DNS requests, TCP connection failures, retransmissions, DHCP traffic, and other network problems. For multi-file captures, convert each ETL file separately. You can also convert captures into readable text using pktmon etl2txt. This makes Pktmon a useful alternative to installing additional capture software on Windows 11 computers, particularly when you need to collect network evidence remotely or troubleshoot a problem using only built-in Windows utilities.

