Failed to convert UTF-16LE string to multibyte string!

Comments, questions, bug reports, etc.
Post Reply
deployer
Posts: 11
Joined: Fri Nov 20, 2015 1:57 am

Failed to convert UTF-16LE string to multibyte string!

Post by deployer »

When attempting to capture Windows 10 build 1703 the following error occurs.

Code: Select all

[ERROR] Failed to convert UTF-16LE string to multibyte string!
 
[ERROR] This may be because the UTF-16LE string could not be represented
in your locale's character encoding.
ERROR: Exiting with error code 66:
A Unicode string could not be represented in the current locale's encoding.
Additional Info:
Error occurs while capturing and NTFS block device from Linux
wimlib version: 1.12.0
libntfs version: 2017.3.23

Let me know if I need to test anything for you. Thanks
synchronicity
Site Admin
Posts: 474
Joined: Sun Aug 02, 2015 10:31 pm

Re: Failed to convert UTF-16LE string to multibyte string!

Post by synchronicity »

The way strings are converted between different encodings was improved in wimlib v1.10.0, but you're using an older version. Can you please try the latest version? You are definitely *not* using v1.12.0, because the error message quoted does not exist anymore.
deployer
Posts: 11
Joined: Fri Nov 20, 2015 1:57 am

Re: Failed to convert UTF-16LE string to multibyte string!

Post by deployer »

Somehow the symlink was still linked to an old version of the library. So the binary said version 1.12.0 but it wasn't really accurate. I updated the link and all is well now. Thanks for pointing me in the right direction.
synchronicity
Site Admin
Posts: 474
Joined: Sun Aug 02, 2015 10:31 pm

Re: Failed to convert UTF-16LE string to multibyte string!

Post by synchronicity »

Ah, I should probably make wimlib-imagex print the version of wimlib it is using, in case it's not the same as the version of wimlib-imagex.

(FYI: using a version of wimlib that is older than wimlib-imagex may work, but is not guaranteed to. Using a *newer* library with an older wimlib-imagex is definitely supported though, at least with v1.7.0 and later.)
Post Reply