Skip to content

Conversation

@Sp3EdeR
Copy link

@Sp3EdeR Sp3EdeR commented Dec 1, 2025

The Windows batchs script is built from UTF-8 paths, but the launched CMD instance is using a locale-specific codepage. Forcing it to use UTF-8.

This change addresses item #4623

This changes visible behavior

The following changes are proposed:

  • Explicitly change the cmd codepage to UTF-8 to match the script's default file encoding in writeFile

Closes #4623 4623

The Windows batchs script is built from UTF-8 paths, but the launched CMD instance is using a locale-specific codepage. Forcing it to use UTF-8.
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

Successfully merging this pull request may close these issues.

[Bug] Scan for Kits fails when VS is installed into a non-ASCII path

1 participant