Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
Martinx24 opened this issue Apr 28, 2021 · 3 comments
Open

Comments

@Martinx24
Copy link

What is this warning?

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

@dscharrer
Copy link
Owner

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?

@Martinx24
Copy link
Author

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
Copy link
Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants