+- hashcat Forum (https://hashcat.net/forum)
+-- Forum: Support (https://hashcat.net/forum/forum-3.html)
+--- Forum: hashcat (https://hashcat.net/forum/forum-45.html)
+--- Thread: hashcat-4.1.0 can't run (/thread-7953.html)
hashcat-4.1.0 can't run - jonnynguyen1123 - 11-15-2018
Hi
When I can't run hashcat-4.1.0, there is a warning "./hashcat.hctune : No such file or directory". Anyone know how to fix it? Thanks
RE: hashcat-4.1.0 can't run - Mem5 - 11-15-2018
Forst, get latest version (5.0.0).
Second, change you directory to hashcat. You must call hashcat from the diectroy where it has been unzipped.
RE: hashcat-4.1.0 can't run - DanielG - 11-15-2018
This is not a lot of info. Is it windows? linux? mac? what is your command you are running? can you see that file in your file browser?
My guess: You installed hashcat (extracted the zip) with user1 and are trying to run hashcat while logged in as user2. User2 doesn't have the rights to write files in the directory you are running hashcat in.
RE: hashcat-4.1.0 can't run - NoReply - 11-15-2018
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.
RE: hashcat-4.1.0 can't run - NoReply - 11-19-2018
Seems like this issue will remain as it is: https://github.com/hashcat/hashcat/issues/1539
RE: hashcat-4.1.0 can't run - Mem5 - 11-19-2018
It's not an issue.
Just change the directory: use "cd" under windows and linux.
RE: hashcat-4.1.0 can't run - NoReply - 02-01-2019
@OscarAkaElvis created a workaround on Github for users like me, who like to run Hashcat from arbitrary locations on Windows.
See: https://github.com/hashcat/hashcat/issues/1539#issuecomment-458033314
RE: hashcat-4.1.0 can't run - atom - 02-05-2019
It's exactly what Mem5 told. The workaround is using cd to the installation folder.