innoextract icon indicating copy to clipboard operation
innoextract copied to clipboard

Warning: Unexpected data while converting from Windows-1252 to UTF-8.

Open Martinx24 opened this issue 3 years ago • 3 comments

What is this warning?

I get this warning while unpacking Graphic driver created in Inno Setup.

Martinx24 avatar Apr 28 '21 14:04 Martinx24

It means that something that innoextract thought should be text in the Windows-1252 encoding had contained bytes that are invalid in that encoding. This can happen:

  • when innoextract does not understand the Inno Setup data version (or has a bug) and tries to decode something as a string that is not one
  • when the installer uses a different encoding. innoextract should detect the correct encoding based on the installer language (and stored codepage number depending on version) but you can override the encoding using the --codepage option.
  • when the setup is damaged (unlikely unless you also got checksum errors) or was build with corrupt string data.

Which driver do you see this with? Can you provide a link?

dscharrer avatar Apr 28 '21 17:04 dscharrer

Thank you. I would like to know what file is not decoded. This is the driver link: https://dlcdnets.asus.com/pub/ASUS/GamingNB/DriverforWin10/VGA/Graphic_ROG_NVIDIA_B_V27.21.14.5167_19594.exe

But it seems like this warning appears in every driver from asus. I also tried audio driver with same warning.

Martinx24 avatar Apr 28 '21 20:04 Martinx24

It means that something that innoextract thought should be text in the Windows-1252 encoding had contained bytes that are invalid in that encoding. This can happen:

  • when innoextract does not understand the Inno Setup data version (or has a bug) and tries to decode something as a string that is not one
  • when the installer uses a different encoding. innoextract should detect the correct encoding based on the installer language (and stored codepage number depending on version) but you can override the encoding using the --codepage option.
  • when the setup is damaged (unlikely unless you also got checksum errors) or was build with corrupt string data.

Which driver do you see this with? Can you provide a link?

Hello. Any updates? Is there a way to check out which file is not decoded?

I tried another inno unpacker with no warning at all.

Martinx24 avatar May 03 '21 15:05 Martinx24