search

idrassi / HashCheck

HashCheck Shell Extension for Windows with added SHA2, SHA3, and multithreading; originally from code.kliu.org
Other
257 stars 12 forks source link

Verifier bug: 260 character path limit. Affects Verifier, but does not affect Create Checksum File. #22

Open a-raccoon opened 6 months ago

a-raccoon commented 6 months ago

If you are running a version of Windows that exhibits the 260 character MAXPATH limit, eg, Windows 7, 8 or 10, you can use HashCheck's shell extension to Create Checksum File and it will work flawlessly even on files in paths greater than 260 characters. However, if you double-click the digest file just created, you will encounter an UNREADABLE error on files exceeding the 260 total path character limit.

This is a limit that has been overcome in Windows a long time ago, by utilizing "Unicode" APIs when handling file operations. The Create Checksum function is doing this correctly. The Verify Checksum function is doing this incorrectly. A simple unification of file access behavior should be in order.

Rings4 commented 5 months ago

Thanks for posting, I'm looking to upgrade my 2014 version of Gurnec's HashCheck because I need long path support. Really hope that feature can be added to this.

a-raccoon commented 5 months ago

@Rings4: also take a look at RapidCRC

NintendoManiac64 commented 2 months ago

This is also particularly an issue with anything Linux related such as Ext file systems or even just using the verifier directly on Linux via wine (because there has been a major lack of GUI-based options on Linux that support recursive directories).