I shared the following question several users have asked in other portions of Windows Support: In Windows 10, how does one calculate the checksum values of files? As most users know, matching the checksum value of a file on your computer against hash values specified by the source of the file, for example, is an important security feature to ensure the integrity of the files you use.
The answer to this question is simple enough, but I didn't find it in any Microsoft documentation or websites. Those explain options limited to prior versions of Windows and do not work for Windows 10.
Windows 10 does offer two straightforward ways to find the hash values of files, at least using Windows 10 Home x64 as I did. I don't know if they work on other versions, but I would expect they do. Microsoft just makes it difficult to discover the tools needed to perform this routine task.
One method uses the command certutil in the command prompt window. For example:
certutil -hashfile c:\Users\JDoe\Desktop\abc.exe SHA512
This command returns the SHA512 hash of file abc.exe located at the specified file path. You may use other values after SHA, such as 1 or 256, to produce the corresponding hash, and you may substitute MD5 or other supported parameters.
Another method is to use Windows PowerShell (version 5.1 for me) with the command Get-FileHash:
Get-FileHash -Path c:\Users\JDoe\Desktop\abc.exe -Algorithm SHA512
Like certutil after a command prompt, this command in PowerShell returns the SHA512 hash of file abc.exe at the location specified on the C: drive, and you may substitute other parameters to find their corresponding hash values.
As for the same question posted elsewhere on these forums, few answers have been posted. They suggest limited solutions, some of which work for certain users and others that do not. Some reference an FCIV command, which apparently works automatically in
prior versions of Windows. For Windows 10, at least one user sets forth somewhat elaborate steps for installation and use of FCIV in Windows 10, and that may work for some. You may find it in this thread:
In any event, in Windows 10 as it is configured, neither the command prompt nor Windows PowerShell recognizes FCIV as a command. Presumably, Microsoft does not expect it to be used, probably because there are alternatives. Microsoft just makes it difficult for anyone to discover them, at least in the experience of some of us.
Free third-party checksum programs are available for download and installation. I have not tried any of them. Because Windows 10 apparently has simple commands to check the values as explained above, I don't see any reason to use them.
Microsoft also makes it difficult for users to post anything in its forums. For instance, I could not reply to any of the existing questions but am limited to discussing the topic in this "community" section. For users who, like me, had a hard time discovering this information, I hope this post turns up in search results and offers some help.