Knowledge base

1000 FAQs, 500 tutorials and instructional videos. Here, there are only solutions!

Check the integrity of the kDrive installer (Checksum)

Update 03/02/2026

This guide explains how to verify the integrity and authenticity of the kDrive installer by comparing its digital fingerprint (checksum) with the one provided on the download page.

 

Preamble

  • When you download the kDrive application for Desktop (Windows, macOS, or Linux), you can verify that the file has not been corrupted or altered during the transfer using a "checksum" of the SHA256 type.
  • The digital signature (SHA256 fingerprint) of each installer is available on the download page.

 

Verify the checksum of your file

On Windows

You do not need to install third-party software; use the built-in utility certutil via the command prompt:

  1. Open the Start menu and type cmd to open the command prompt.
  2. Navigate to the folder where the installer is located (e.g., cd Downloads).
  3. Enter the following command (replace kDrive.exe with the actual name of the downloaded file):

certutil -hashfile kDrive.exe SHA256

On macOS

Use the terminal built into macOS:

  1. Open the Terminal (via Spotlight or in Applications > Utilities).
  2. Enter the following command followed by a space, then drag and drop the downloaded file into the terminal window:

shasum -a 256

Example result: shasum -a 256 kDrive.dmg

On Linux

Most Linux distributions include the sha256sum tool:

  1. Open your terminal.
  2. Run the following command:

sha256sum kDrive.deb (or .rpm / .AppImage)

 

Interpret the result

A sequence of characters (letters and numbers) is displayed once the command is executed. Compare this sequence with the one displayed on Infomaniak:

  • The codes are identical : the file is authentic and complete; you can proceed with the installation safely.
  • The codes are different : the file is probably corrupted or has been modified; it is recommended to delete the file and restart the download from your Infomaniak interface.

For Linux users using the official repositories (.deb), the verification is usually handled automatically by your package manager via the repository signature.


Has this FAQ been helpful?