your other posts imply that you already solved this problem:
https://hashcat.net/forum/thread-8715-po...l#pid46305
you wouldn't be able to get that specific error message without being able to run hashcat.
btw: another common error of windows users is that they corrupt the binaries by for instance incorrectly copy-pasting some commands like "> hashcat64.exe -m"
this of course overrides the binary file (executable) and corrupts the whole hashcat installation or downloaded folder.
"> " is commonly used as a command prompt, but if you copy-paste and run it, it will act like a file redirector (write to the file to the right, in this case the file hashcat64.exe)
the only solution here is to re-download hashcat from https://hashcat.net and avoid doing mistakes like this (not overriding important files)
https://hashcat.net/forum/thread-8715-po...l#pid46305
you wouldn't be able to get that specific error message without being able to run hashcat.
btw: another common error of windows users is that they corrupt the binaries by for instance incorrectly copy-pasting some commands like "> hashcat64.exe -m"
this of course overrides the binary file (executable) and corrupts the whole hashcat installation or downloaded folder.
"> " is commonly used as a command prompt, but if you copy-paste and run it, it will act like a file redirector (write to the file to the right, in this case the file hashcat64.exe)
the only solution here is to re-download hashcat from https://hashcat.net and avoid doing mistakes like this (not overriding important files)