If it doesn't respond to a status check immediately then it's obvious. I may not have communicated the issue clearly.
When I press "s" for a status update it doesn't respond until (maybe?) the set is exhausted. So, when I start a crack running and I press "s" and nothing happens then it's obvious that it is still not fixed.
A restart only takes 30 sec. and I'm not going to wait for the set to exhaust. The last set took 1.5 hrs. and I don't need to wait that long.
I just uninstalled CUDA (forgot it was installed) and I can get a status update 2x before hashcat stops responding. This is slightly different behavior than before in that I can get 2 status updates before it stops responding. It is still cracking at a very degraded level.
When I press "s" for a status update it doesn't respond until (maybe?) the set is exhausted. So, when I start a crack running and I press "s" and nothing happens then it's obvious that it is still not fixed.
A restart only takes 30 sec. and I'm not going to wait for the set to exhaust. The last set took 1.5 hrs. and I don't need to wait that long.
I just uninstalled CUDA (forgot it was installed) and I can get a status update 2x before hashcat stops responding. This is slightly different behavior than before in that I can get 2 status updates before it stops responding. It is still cracking at a very degraded level.