HashCheck icon indicating copy to clipboard operation
HashCheck copied to clipboard

Add support for long paths

Open superbonaci opened this issue 5 years ago • 3 comments

Does not generate or verify hashes when path is longer than 260 characters. Is possible to add the feature without breaking backwards compatibility?

superbonaci avatar Apr 21 '20 09:04 superbonaci

It's a windows limitation. most programs stop working correctly past that point for the same reason. there is a setting that extends the limit but breaks back compat, but I don't remember what it's called

Masamune3210 avatar Apr 21 '20 13:04 Masamune3210

P.S. also see: https://github.com/gurnec/HashCheck/issues/30

R-Adrian avatar Apr 25 '20 18:04 R-Adrian

The setting you mean probably is HKLM:\SYSTEM\CurrentControlSet\Control\FileSystem DWORD "LongPathsEnabled" Value: 1

however this does not work for HashCheck. Maybe this is a limitation for extensions of the Explorer Properties. The basic issue is that HashCheck does silently fail, either failing at rading the file and ending with "a of b files hashed" where a < b or even ignoring the existence of a file (b < real number of files n).

I think:

a< b happens, if the path to a file is too long, but the folder path is not (hence HashCheck can read the contents of the folder but not access the files within)

b<n happens when the path of the folder is too long and HashCheck cannot determine the number of files. THIS is a real problem, as you would not notice it in a real world case.

even worse: This silent fail also happens, if a file is locked (Try to hash pagefile.sys for example)

JustMyGithub avatar Jul 11 '20 09:07 JustMyGithub