Hang when performing SHA256 Hash of large ISO

/Hang when performing SHA256 Hash of large ISO

Hang when performing SHA256 Hash of large ISO

Using 64-Bit version of QuickHash, performing an SHA256 hash of 7.36GB ISO to compare against known hash. QuickHash reads 600MB to 700MB of file and then appears to hang, QuickHash does not update progress bar, spinning circle appears and if QuickHash is clicked the QuickHash title bar says \”Not responding\”.

If QuickHash is left to run the hash process does complete.

OS is Windows 8.1 Enterprise x64, PC has 8GB RAM, i5-6300 CPU

By | 2017-07-21T15:04:38+00:00 July 14th, 2017|3 Comments

About the Author:


  1. Ted 27/07/2017 at 09:54 - Reply

    OK, fair point. I’ll see if I can improve that tab in particular and try to implement in the up and coming v2.8.3 release.

  2. San 23/07/2017 at 14:47 - Reply

    Reading about the awesome speed of xxHash, I tried to create xxHash64 of a 200 GB file using 64 bit version of QuickHash (Windows 7 64-bit, 4 GB RAM laptop). As mentioned by other users, the software appeared frozen (Not Responding) for a long time although I’m sure it was working in background. However, since the job was urgent, I needed some sort of progress indicator. So I had to interrupt the process and had to do the job with Exact File (with adler32 algorithm which is the fastest it provides). Its speed may be slower than xxHash but it always shows the progress in percentage – so I’m sure that the program is working.and get some estimate as to how long it will be before I’ll get the result even through it does not show ETA. It is the only hashing program for Windows that I know (not counting shell extension programs, which always need to be in memory) that shows progress of hashing for large files.

    It is therefore suggested that some sort of progress indicator be incorporated into QuickHash. Even though it may cost some hashing speed, it is sometimes essential to know the progress in case of very large files. For computing hashes of smaller files, the program is awesome.

  3. Ted 21/07/2017 at 15:04 - Reply

    Thanks for the bug report. I agree it is a bit of an issue but, strictly speaking, this is just an interface lag. Because Quickhash is not multi-threaded, there is a delicate trade off between refreshing the interface too often to the detriment of the hashing speed. It’s one reason why a command line hashing tool will typically always be much faster. GUI’s slow things down! But prior to this version, users used to complain that the interface did not respond AT ALL and people kept saying “it hash crashed when hashing a large file because it says not responding”. Well that does not mean it has crashed. It just means it is ignoring you while it does it’s thing.

    In this version, I changed it a little so that it did report on progress if left alone, but, as you state, once you try and interact with the interface it does appear as though it has frozen. But it has not, as you have also identified.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.