Slow/no status response in Windows 10
#5
Wait, how did you test this that quickly? (you had to reboot your system and wait until the whole dictionary exhausted, shouldn't that take at least several minutes/hours?)

How much time does it take to exhaust ? Are we speaking about several hours or just some seconds?

If hashcat doesn't react to key presses in its initialization phase, that is perfectly normal. On the other hand, it should react whenever you press a key after you see this line "[s]tatus [p]ause [r]esume [b]ypass [c]heckpoint [q]uit". Do you see this prompt?

It might also make sense to test with a different set of input, e.g. a command like this (MD5 hash type):
Code:
hashcat -a 3 00000000000000000000000000000000 ?a?a?a?a?a?a?a?a


Messages In This Thread
RE: Slow/no status response in Windows 10 - by philsmd - 06-02-2017, 08:50 AM