Hashcat says its starting and then nothing happens
#1
I am trying this for the first time and following a very out of date tutorial (on version 3.6.0), but anytime i run the command it says to run, the output is as follows.  I have tried other variations of this command, but nothing is starting when it says it is.

Specs

intel i5-6600k
GTX 960 on driver 418.81 released on 2/3
Windows 10 pro version 1809


Attached Files
.png   hashcat.PNG (Size: 14.68 KB / Downloads: 12)
Reply
#2
By default, cracks will be written to hashcat.potfile - you don't need -o. If you use -o, hashcat assumes that you're semi-automating something and a lot of the output is suppressed.
~
Reply
#3
Please follow this guide: https://hashcat.net/faq/wrongdriver)

also always mention what your GPUs / CPUs / operating system / drivers are.


if you want to start a mask attack, you should also always specify a mask (otherwise the default mask is used which is probably not what you wanted in each and every situation), see https://hashcat.net/wiki/?id=mask_attack
Reply
#4
knew i was forgetting something:

intel i5-6600k
GTX 960 on driver 418.81 released on 2/3
Windows 10 pro version 1809

I've tried rebooting, following the mask and incorrect driver issues, with no improvement
Reply
#5
hmm, did you try installing an older driver version ? e.g. the ones recommended on https://hashcat.net/hashcat

I'm pretty sure this is not a hashcat issue... but it could of course be that Nvidia changed something with the latest version... it seems we are getting more of this issues lately e.g. https://hashcat.net/forum/thread-8139.html
Reply
#6
(02-10-2019, 08:33 AM)royce Wrote: By default, cracks will be written to hashcat.potfile - you don't need -o. If you use -o, hashcat assumes that you're semi-automating something and a lot of the output is suppressed.

I tried removing that and nothing changed unfortunately
Reply
#7
did you try running these commands:

Code:
hashcat -I

and


Code:
hashcat -b


if not, please try with the above hashcat test/benchmark/troubleshooting commands.
Reply
#8
did you try without using powershell, but cmd instead ?


update: whoops, I just realized I had the "wrong" screenshot open from this issue (https://hashcat.net/forum/thread-8141-po...l#pid43675)... I think you are not using powershell at all, or?
Reply
#9
(02-10-2019, 09:27 AM)philsmd Wrote: did you try without using powershell, but cmd instead ?


update: whoops, I just realized I had the "wrong" screenshot open from this issue (https://hashcat.net/forum/thread-8141-po...l#pid43675)... I think you are not using powershell at all, or?

so, it seems like i have something wrong at the OS level with this build, i installed it on a different system and it worked like a charm. Thanks
Reply
#10
did you try to follow the wrongdriver guide ?

Do you have any other OpenCL runtime/driver installed ? maybe the one for your CPU etc ?

For the system that isn't working yet, did you have any (working) drivers installed in the past ? or did you for instance change hardware from AMD to Nvidia etc . Is this a fresh install or an older system ? ... in most of the cases the DDU (Display driver uninstaller) or Driver Fusion software is able to fix most of the driver related problems by uninstalling the drivers and by doing some final clean up steps (even though sometimes some OpenCL.dll etc are still left and you need to remove them manually, as the guide already emphasizes).
Reply