Slow/no status response in Windows 10
#3
I understand it's 2 different OS. The purpose is to troubleshoot. Again, I used --status to troubleshoot, to see if there was any difference.

No emulator. I'll try the reg patch.

Thanks for the quick response!

(06-02-2017, 08:09 AM)philsmd Wrote: Well, that's a comparison of 2 completely different (operating) systems. I'm not sure if that is a good comparison. Furthermore, the 2 system also have different hardware (so everything changes). A better comparison would be either: different hardware, but same operating system OR the same hardware, but different operating system (not changing everything and then compare apples and oranges).

I also do not understand why you use --status (normally you would not use it, except for pipes - where it is enabled by default - or if you use hashcat together with some wrappers etc).

What is very important here is the question if you are using any particular shell/terminal emulator. Do you use mingw/cygwin/powershell etc ? If so, please test with cmd.exe

Also you might need to read the output of hashcat carefully (eventually there are some warnings like the one about the timeout patch etc https://hashcat.net/wiki/timeout_patch )


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