Error: no hashes load about hashcat.launcher HOT 25 CLOSED

Hi
have you checked the pot file?

from hashcat.launcher.

How can i do that?

from hashcat.launcher.

in hashcat folder there will be a file hashcat.potfile
open that file in a text editor and see if you can find your hash there

from hashcat.launcher.

I just check it and there is no such file in the directory. And there is a bunch of .outfiles folder but all are empty. I think that's maybe link to the error "no hashes load".

from hashcat.launcher.

can you send a screenshot

from hashcat.launcher.

Yes, here you have:

Forget to say i'm in Windows 10.

from hashcat.launcher.

sorry i meant a screenshot where you see the error (in hashcat.launcher to go tasks and go to the task's journal)

from hashcat.launcher.

Here:

from hashcat.launcher.

possibly you are using the wrong hash mode

from hashcat.launcher.

I think about that, but it was working before with the same hashtype (and also as i had created the file myself before i know what type i use), so i don't understand.

Also if i accidently delete some usefull files when i search the password, it should have been repair when i suppress everything and redownload, right?

from hashcat.launcher.

i don't know what went wrong exactly, but you can try again and make sure to select an output file so you know where you'd fine the password

from hashcat.launcher.

When it was working, i always select a output file, but there was no password on it anyway, i don't understand why and according to you that's not normal.

from hashcat.launcher.

Can you try with a pre known hash value, just to make sure things are working as expected

from hashcat.launcher.

I think i understand the problem. In my opinion, it keeps saying me that because i already hack the password, even if i don't find where it's written.

I try to make a copy of the encrypted file and to hack on this copy. I have no longer the no hash error but the "no such files or directory" one.

from hashcat.launcher.

even if you make a copy you won't see the hash if it's already cracked, first go to settings and in the Extra Args field add: --potfile-disable

as for your the new error, it's because the hash file cannot be accessed.
perhaps C:\Users\basti\Desktop\Privedoes not exists?

from hashcat.launcher.

Yes, here you have:

Forget to say i'm in Windows 10.

Where did you place hashcat.launcher? Maybe it's bugged and added the pot-file in the folder where you have hashcat.launcher extracted. And this is the reason you can't crack it again.

from hashcat.launcher.

"even if you make a copy you won't see the hash if it's already cracked, first go to settings and in the Extra Args field add: --potfile-disable"

I try this, now i have the "no such files or directory" message.

"as for your the new error, it's because the hash file cannot be accessed.
perhaps C:\Users\basti\Desktop\Privedoes not exists?"

It exists, i even point where this it to the software, i don't understand how he can't find it! But if that's a copy and it doesn't work with a copy, that's maybe the point.

I put hashcat folder on the desktop and hashcat laucher is on the desktop too (not in hashcat folder if that's the question).

from hashcat.launcher.

I may have find the problem: the files is title "Privé" with an accent but in hashcat journal it appears as "Prive" without accent. But it's titled correctly in Target and the path is correct too. Seems there is a bug here.

from hashcat.launcher.

can you change the files name? use a clear alphanumeric name and try again

from hashcat.launcher.

It seems to work and to have found the password, where i go next to recover it?

from hashcat.launcher.

you should find the password in the output file that you selected

from hashcat.launcher.

There is only this in output file:

E:\Sauvegarde\Documents\Prive:$HEX[627238383c47377e357b286a6147586344553a36]

I see no password there.

from hashcat.launcher.

the password is in hex format, just decode it
that should be the password you are looking for: br88<G7~5{(jaGXcDU:6

from hashcat.launcher.

That's exactly that, thank you for the help.

from hashcat.launcher.

You are welcome, i think we can close this case now.
(for easy to read) I have opened a new issue regarding special characters in filenames

from hashcat.launcher.