This is a limitation of hashcat's UTF16-based kernels. See https://github.com/hashcat/hashcat/issues/2121
In the case of NTLM you can work around it by using the MD4 kernel with forced UTF-16LE encoding. See --encoding-to and --encoding-from options.
In the case of NTLM you can work around it by using the MD4 kernel with forced UTF-16LE encoding. See --encoding-to and --encoding-from options.