If you use the release version from https://hashcat.net/ you just need to know that this is a known issue and was already fixed: https://github.com/hashcat/hashcat/issues/1178
You can use https://hashcat.net/beta/ to double-check that this display error is fixed (otherwise you need to wait for the next release version).
No, there shouldn't be any invalid results. As said, for the user it should only be a cosmetic difference.
This question was already answered a couple of times, lately.
You can use https://hashcat.net/beta/ to double-check that this display error is fixed (otherwise you need to wait for the next release version).
No, there shouldn't be any invalid results. As said, for the user it should only be a cosmetic difference.
This question was already answered a couple of times, lately.