English
Continue in the app
Be The First To Get Support Updates
Want to know about the latest technical content and software updates?

How To: Verify an Esri download using the checksum

Summary

What is a checksum?

A checksum is a string of numbers and letters used to uniquely identify a file. Checksum is most commonly used to verify if a copy of a file is identical to an original, such as downloaded copies of ArcGIS product installation or patch files.

How does checksum work?

A file is pushed through an algorithm, which outputs a unique alphanumeric string called a checksum, also known as a "hash". Different files, even those with minute differences, produce different checksum values.

There are multiple algorithms that can be used to produce a checksum value. The checksum shown in MyEsri for older products uses the MD5 algorithm. Since the Fall 2021 product releases, SHA-256 checksums are displayed in MyEsri. However one can still use the 'Get-FileHash -Algorithm MD5' command described below to return the MD5 checksum for older products.

Image of the process to verify the checksum of a file.
 

What circumstances would warrant verifying a checksum value?

Files may be changed during download, transmission, or storage. For example, if there is an issue with network connectivity at the time of download, the file may not download correctly. Issues with hard drive storage could also lead to file alteration.

Note:
Checksum can be used to verify any type of file. The steps provided in this article are specific to installers and executable files.

Procedure

How to verify the checksum of a file (Windows)

Note:
This procedure uses Windows PowerShell, included in Windows versions since Windows 7 and Windows Server 2008 R2. Versions of PowerShell for Windows XP, Windows Server 2003, Windows Vista and Windows Server 2008 are available for download for both 32-bit and 64-bit platforms.
  1. Open Windows PowerShell from the Windows Search menu.
Image of Windows Powershell
  1. At the prompt, type Get-FileHash, followed by a space, and drag-and-drop the file to be verified from the local download folder into the PowerShell window.
    If the file is stored on a network drive, open the file directory either via a UNC path or a mapped letter drive in Windows File Explorer, then drag-and-drop the file into the PowerShell window as shown below. In the following image, the ArcGIS Pro 2.9 executable file was used. The full command at the prompt is:
Get-FileHash C:\Users\<username>\Downloads\ArcGISPro_29_179927.exe
Get-FileHash command for ArcGIS Pro 2.9
  1. Press Enter, and the SHA-256 checksum is displayed, as shown in the following image.
KB20408b.jpg
  1. Compare the output checksum value to the checksum values provided by Esri. Product downloads can be verified with the Downloads page of My Esri:
    1. Go to My Esri.
    2. Click My Organizations.
    3. Click Downloads.
    4. Select View Downloads for the appropriate product and version.
    5. In the Download Components tab, expand Product Components, and locate the appropriate product.
    6. Click Additional Information to display the listed checksum.
  2. The Hash displayed in PowerShell can now be compared with the Checksum shown in MyEsri to verify the download, as seen in the following image.

KB20408c.jpg

Comparing the MD5 checksum
For older versions of Esri products, the MD5 hash is what is seen in MyEsri. So to verify downloads, the following PowerShell procedure can be used to compare the MD5 checksum of the downloaded file with MyEsri.

  1. Drag and drop the file to be verified from the local directory into the PowerShell window. If the file is stored on a network drive, open the file directory either via a UNC path or a mapped letter drive in Windows File Explorer, then drag and drop the file into the PowerShell window as shown below. In this example, the ArcGIS Pro 2.3 executable file is used.
Image of dragging and dropping the file from Windows File Explorer
  1. After the filename, press the spacebar and enter -Algorithm MD5 to ensure the MD5 algorithm is used. An example of the final command is displayed below, where <filepath> is the full path of the file. In this example, the path is 'C:\arcgis\ArcGISPro_23_167023.exe'.
Get-FileHash <filepath> -Algorithm MD5
  1. Press Enter. The output is the checksum value using the MD5 algorithm.
Image of the Windows Powershell Administrator pane showing the output checksum value
 
  1. Compare the output checksum value to the checksum values provided by Esri. Product downloads can be verified with the Downloads page of My Esri:
Image of My Esri Downloads

How to calculate the Checksum of a file (Linux)

  1. Change the directory to the location of the file.
  2. Type sha256sum then a space, followed by the full name of the file.
sha256sum log4shellmitigation.linux.zip
  1. Press Enter to execute the command. The output is the checksum value using the SHA-256 algorithm followed by the filename.
DDB01B31CF7B91270DF4410F502B17D42DC21232661400982D500E79C577897B log4shellmitigation.linux.zip
SHA256-linux.jpg
  1. Compare the output checksum value to the checksum values provided by Esri. Product downloads can be verified with the Downloads page of My Esri:
    1. Go to My Esri.
    2. Click My Organizations.
    3. Click Downloads.
    4. Select View Downloads for the appropriate product and version.
    5. In the Download Components tab, expand Product Components to locate the appropriate product.
    6. Click Additional Information to display the listed checksum.
Image of My Esri Downloads

Related Information

Last Published: 1/4/2022

Article ID: 000020408

Software: ArcGIS Data Store 10.9.1, 10.9, 10.8.1, 10.8, 10.7.1, 10.7, 10.6.1, 10.6, 10.5.1, 10.5, 10.4.1, 10.4, 10.3.1, 10.3 ArcGIS Server 10.9.1, 10.9, 10.8.1, 10.8, 10.7.1, 10.7, 10.6.1, 10.6, 10.5.1, 10.5, 10.4.1, 10.4, 10.3.1, 10.3, 10.2.2, 10.2.1, 10.2, 10.1, 10 Portal for ArcGIS 10.9.1, 10.9, 10.8.1, 10.8, 10.7.1, 10.7, 10.6.1, 10.6, 10.5.1, 10.5, 10.4.1, 10.4, 10.3.1, 10.3, 10.2.2, 10.2.1, 10.2 ArcGIS Pro 2.9, 2.8.4, 2.8.3, 2.8.2, 2.8.1, 2.8, 2.7.4, 2.7.3, 2.7.2, 2.7.1, 2.7, 2.6.8, 2.6.7, 2.6.6, 2.6.5, 2.6.4, 2.6.3, 2.6.2, 2.6.1, 2.6, 2.5.2, 2.5.1, 2.5, 2.4.3, 2.4.2, 2.4.1, 2.4, 2.3.3, 2.3.2, 2.3.1, 2.3, 2.2.4, 2.2.3, 2.2.2, 2.2.1, 2.2, 2.1.3, 2.1.2, 2.1.1, 2.1, 2.0.1, 2.0, 1.4.1, 1.4, 1.3.1, 1.3, 1.2