You can see the command’s output in the figure below.Īs well as this technique works, the basic techniques that I have shown you are kind of impractical. If you wanted to create an MD5 hash, for example, you would use a command similar to this one: The supported algorithms include SHA1, SHA256, SHA384, SHA512, and MD5. To specify a different hashing algorithm, just add the -Algorithm parameter to the end of the command shown above, followed by the name of the algorithm that you wish to use.
By appending the Algorithm parameter, it is possible to create a different type of hash (such as MD5). However, this is not the only type of hash that is supported. If you look at the command’s output in the figure below, you can see that PowerShell created a SHA256 hash of the file. If I wanted to hash that file, I would use this command: For example, I have a file on my hard disk named Nano.vhd. To use the cmdlet, simply append the name of the path for which you wish to create a hash. There is actually a native PowerShell cmdlet that can be used to create a file hash. Using PowerShell to create a file hash is a surprisingly simple process.
As such, I wanted to take the opportunity to demonstrate how file hashing works in PowerShell. Ever since I posted that advice, it has bothered me that I didn’t come up with something more helpful. Not having time to look it up at that moment, I suggested that they search the Internet for a script. However, I had never attempted to create a file hash in PowerShell and wasn’t quite sure what was involved. I found the source of their problem and explained why they were receiving the error. A few days ago, someone commented on the article that they were receiving this particular error while trying to calculate an MD5 hash. A while back I wrote an article on this site in which I discussed a PowerShell error indicating that a term is not recognized as a cmdlet.
0 kommentar(er)
