Opening largish checksum file in an empty directory never shows results

[VsevolodGolovanov]

... or at least not for a long time.
This is on Windows 11.
Unzip cygwin64_checksums.zip, put it into empty directory, and try to open it - see how it spawns a rundll32 process that goes on to eat CPU for a long time, and no OpenHashTab window shows up. I waited 10 minutes with this file. Another checksum file (with 31K entries) I left running for hours - still no results.

[ViperCode7]

I can reproduce the issue... it's particularly annoying as I was hoping to retire hashcheck and stick just with OpenHashTab but this one seems to have too many bugs.

The issue isn't OS dependent... I'm on Win10 and it still happens.

The issue isn't related to the size of the checksum file... my test file is 50KB in size.

The issue is the way it reads the 1st entry... if the file is missing it fails to display any window.
I add an entry for an existing file to the top of the list and it works... kinda, not as I was hoping for. Instead of showing me the files that are and check their hashes as well as mark the files that cannot be found with the missing message, like hashcheck does, it just tells me that files are missing while completely skipping the files that are present, e.g. that 1st entry I've added.

The checksum file format is that of hashcheck... HASH *FILE_PATH

Right now it's... completely unusable, unfortunately. Back to using 100 tools for one job...