11-15-2018, 12:57 PM
I am also facing this issue under windows, if I call hashcat from a different location than its own folder. This issue is still present in 5.0.0, but did not occur in 4.0.1.
It is somewhat annoying if you included hashcat in your path environment variable to be flexible with the calling location, but blocks it you from doing so. Seems that something about the location of hashcat.hctune changed from 4.0.1 to 4.1.0.
It is somewhat annoying if you included hashcat in your path environment variable to be flexible with the calling location, but blocks it you from doing so. Seems that something about the location of hashcat.hctune changed from 4.0.1 to 4.1.0.