You should have already noticed by now (after we discussed and explained it here: https://hashcat.net/forum/thread-6908.html and also by looking at the example hashes here: https://hashcat.net/wiki/example_hashes) that some hash types expect binary data (like veracrypt, truecrypt etc) and some other hash types expect hex data (or base64 encoded data etc).
From the screenshot (see the notepad++ screenshot) above it is very clear to me that your data is not in binary format for the veracrypt "hash". Just compare it with the example hashes.
The hash formats are normally very intuitive: MD5 hashes are normally hex encoded and therefore hashcat expects the input to be hexadecimal encoded (0-9a-f, 32 hex chars to contain all 16 binary bytes or 128 binary bits)... other hashes might have some signatures like md5crypt $1$ etc...
on the other hand, some encrypted data ... like it is the case for VeraCrypt/TrueCrypt... doesn't need to be hex encoded/converted.... it is just used as is (with the correct offsets as mentioned here: https://hashcat.net/faq#how_do_i_extract...pt_volumes , depending on the type of VeraCrypt/TrueCrypt "volume")...
This means, that you just copy the data AS-IS (with the correct offset)... for linux/windows you can just use dd (or dd.exe)... but if it is just a VeraCrypt encrypted file the offset is 0 anyway and therefore you do not need to remove any bytes at the beginning.
You just edited your post.... my guess is that you just did something wrong with your conversion... the first 512 bytes should suffice...
the problem is that you used hex encoded data... not the raw data (which is the only correct input)
From the screenshot (see the notepad++ screenshot) above it is very clear to me that your data is not in binary format for the veracrypt "hash". Just compare it with the example hashes.
The hash formats are normally very intuitive: MD5 hashes are normally hex encoded and therefore hashcat expects the input to be hexadecimal encoded (0-9a-f, 32 hex chars to contain all 16 binary bytes or 128 binary bits)... other hashes might have some signatures like md5crypt $1$ etc...
on the other hand, some encrypted data ... like it is the case for VeraCrypt/TrueCrypt... doesn't need to be hex encoded/converted.... it is just used as is (with the correct offsets as mentioned here: https://hashcat.net/faq#how_do_i_extract...pt_volumes , depending on the type of VeraCrypt/TrueCrypt "volume")...
This means, that you just copy the data AS-IS (with the correct offset)... for linux/windows you can just use dd (or dd.exe)... but if it is just a VeraCrypt encrypted file the offset is 0 anyway and therefore you do not need to remove any bytes at the beginning.
You just edited your post.... my guess is that you just did something wrong with your conversion... the first 512 bytes should suffice...
the problem is that you used hex encoded data... not the raw data (which is the only correct input)