07-05-2016, 09:54 AM
We highly recommend that you DO NOT copy any haschat (include) files to a system folder or that you use similar stupid workarounds like this.
The problem with such a "fix" is that after you do that, you don't only have a broken driver (which you already had otherwise the problem with the failed includes wouldn't be there at all), but also have a very broken hashcat installation.
Any updates to hashcat would mean that you need to keep the folder within %APPDATA% also up-to-date and by not doing this carefully enough it only leads to very strange and difficult to troubleshoot problems.
Fix your driver installation already. Instead of breaking your system w/ those "fixes".
See here for a reference, how "similar"/"identical" some systems are, but still have this problem if the drivers were not installed correctly:
https://hashcat.net/forum/thread-5566-po...l#pid29947
https://hashcat.net/forum/thread-5566-po...l#pid29952
The problem with such a "fix" is that after you do that, you don't only have a broken driver (which you already had otherwise the problem with the failed includes wouldn't be there at all), but also have a very broken hashcat installation.
Any updates to hashcat would mean that you need to keep the folder within %APPDATA% also up-to-date and by not doing this carefully enough it only leads to very strange and difficult to troubleshoot problems.
Fix your driver installation already. Instead of breaking your system w/ those "fixes".
See here for a reference, how "similar"/"identical" some systems are, but still have this problem if the drivers were not installed correctly:
https://hashcat.net/forum/thread-5566-po...l#pid29947
https://hashcat.net/forum/thread-5566-po...l#pid29952