• File Path: C:\windows\system32\PATHPING.EXE
  • Description: TCP/IP PathPing Command


Type Hash
MD5 B021ED3CF7518BE1145ABB6392919972
SHA1 7AC412718562964E9C7AC7DE97F3E6BD52B06330
SHA256 B922E594876E9B9C5B0B54487A3453FF26EB18B42013711A10713F21496FCD16
SHA384 056E859BC473D5F554EE11D7D68DC967508D0D8805603A53640FB8BD08A0B8059E57F2EE4194B59F7F3ADA216B9119EA
SHA512 B039307C670EF2E5A64CA476F0E8510ECC8463FE7CE79D7F09EC5D9DEBA1CFDCCFA9D47ADB9A28CAA1579AE0F77DF889D10B433C3D33592D4C7B1781FB3137F1
SSDEEP 384:eZeQ0pPAUeZ7yfJfcpuME6CNDWA0322W3AW:ugpPGyJfcpoNH03W


  • Status: The file C:\windows\system32\PATHPING.EXE is not digitally signed. You cannot run this script on the current system. For more information about running scripts and setting execution policy, see about_Execution_Policies at
  • Serial: ``
  • Thumbprint: ``
  • Issuer:
  • Subject:

File Metadata

  • Original Filename: pathping.exe.mui
  • Product Name: Microsoft Windows Operating System
  • Company Name: Microsoft Corporation
  • File Version: 6.3.9600.16384 (winblue_rtm.130821-1623)
  • Product Version: 6.3.9600.16384
  • Language: English (United States)
  • Legal Copyright: Microsoft Corporation. All rights reserved.

Additional Info*

*The information below is copied from MicrosoftDocs, which is maintained by Microsoft. Available under CC BY 4.0 license.


Applies to: Windows Server (Semi-Annual Channel), Windows Server 2019, Windows Server 2016, Windows Server 2012 R2, Windows Server 2012

Provides information about network latency and network loss at intermediate hops between a source and destination. This command sends multiple echo Request messages to each router between a source and destination, over a period of time, and then computes results based on the packets returned from each router. Because this command displays the degree of packet loss at any given router or link, you can determine which routers or subnets might be having network problems. Used without parameters, this command displays help.

[!NOTE] This command is available only if the Internet Protocol (TCP/IP) protocol is installed as a component in the properties of a network adapter in Network Connections.

Additionally, this command identifies which routers are on the path, same as using the tracert command. Howevever, this command also sends pings periodically to all of the routers over a specified time period and computes statistics based on the number returned from each.


pathping [/n] [/h <maximumhops>] [/g <hostlist>] [/p <Period>] [/q <numqueries> [/w <timeout>] [/i <IPaddress>] [/4 <IPv4>] [/6 <IPv6>][<targetname>]


Parameter Description
/n Prevents pathping from attempting to resolve the IP addresses of intermediate routers to their names. This might expedite the display of pathping results.
/h <maximumhops> Specifies the maximum number of hops in the path to search for the target (destination). The default is 30 hops.
/g <hostlist> Specifies that the echo Request messages use the Loose Source Route option in the IP header with the set of intermediate destinations specified in hostlist. With loose source routing, successive intermediate destinations can be separated by one or multiple routers. The maximum number of addresses or names in the host list is 9. The hostlist is a series of IP addresses (in dotted decimal notation) separated by spaces.
/p <period> Specifies the number of milliseconds to wait between consecutive pings. The default is 250 milliseconds (1/4 second). This parameter sends individual pings to each intermediate hop. Because of this, the interval between two pings sent to the same hop is period multiplied by the number of hops.
/q <numqueries> Specifies the number of echo Request messages sent to each router in the path. The default is 100 queries.
/w <timeout> Specifies the number of milliseconds to wait for each reply. The default is 3000 milliseconds (3 seconds). This parameter sends multiple pings in parallel. Because of this, the amount of time specified in the timeout parameter isn’t bounded by the amount of time specified in the period parameter for waiting between pings.
/i <IPaddress> Specifies the source address.
/4 <IPv4> Specifies that pathping uses IPv4 only.
/6 <IPv6> Specifies that pathping uses IPv6 only.
<targetname> Specifies the destination, which is identified either by IP address or host name.
/? Displays help at the command prompt.
  • All parameters are case-sensitive.

  • To avoid network congestion and to minimize the effects of burst losses, pings should be sent at a sufficiently slow pace.

Example of the pathping command output

D:\>pathping /n contoso1
Tracing route to contoso1 []
over a maximum of 30 hops:
computing statistics for 125 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  address
                                0/ 100 =  0%   |
  1   41ms     0/ 100 =  0%     0/ 100 =  0%
                               13/ 100 = 13%   |
  2   22ms    16/ 100 = 16%     3/ 100 =  3%
                                0/ 100 =  0%   |
  3   24ms    13/ 100 = 13%     0/ 100 =  0%
                                0/ 100 =  0%   |
  4   21ms    14/ 100 = 14%     1/ 100 =  1%
                                0/ 100 =  0%   |
  5   24ms    13/ 100 = 13%     0/ 100 =  0%
Trace complete.

When pathping is run, the first results list the path. Next, a busy message is displayed for approximately 90 seconds (the time varies by hop count). During this time, information is gathered from all routers previously listed and from the links between them. At the end of this period, the test results are displayed.

In the above sample report, the This Node/Link, Lost/Sent = Pct and address columns show that the link between and is dropping 13% of the packets. The routers at hops 2 and 4 are also dropping packets addressed to them, but this loss doesn’t affect their ability to forward traffic that isn’t addressed to them.

The loss rates displayed for the links, identified as a vertical bar (** ) in the **address column, indicate link congestion that is causing the loss of packets that are being forwarded on the path. The loss rates displayed for routers (identified by their IP addresses) indicate that these routers might be overloaded.

Additional References

MIT License. Copyright (c) 2020-2021 Strontic.