This guide covers Windows 11 and Windows 10. Allow about 15 minutes, plus time for restarts. You’ll need administrator permission, and you should test carefully: these settings affect the whole PC, not just one app.
Why system locale matters
Some older apps rely on a Windows code page rather than Unicode to interpret text. The system locale determines the default code pages and certain font support used by non-Unicode programs. If the app expects Japanese text but Windows is using a different legacy code page, readable characters may become garbage.
The system locale is not the same as your Windows display language, keyboard layout, or regional format for dates and numbers. Changing those other settings is not a substitute for this fix.
In short: Start by identifying the language the app or its data expects—not necessarily the language you use for Windows.
Before changing anything
- Close the affected app and save your work.
- Back up important files or databases the app uses. During testing, open a copy where practical and avoid saving over original data.
- Identify the app’s intended language. For example, a legacy Japanese application may expect Japanese (Japan).
- Make a note of the current system locale and whether the UTF-8 checkbox is selected. You’ll need both details if you want to reverse the changes.
- If this is a managed work PC, check with your IT administrator before changing a system-wide setting.
Find the system locale and UTF-8 setting
On either Windows 11 or Windows 10:
- Open Control Panel. You can search for it from Start.
- If Control Panel is in category view, switch View by to Large icons or Small icons.
- Select Region.
- Open the Administrative tab.
- Under Language for non-Unicode programs, select Change system locale.
- Record the Current system locale and the state of Beta: Use Unicode UTF-8 for worldwide language support.
Windows may ask for administrator credentials or confirmation. Don’t change both settings at once if you can avoid it: testing one change at a time makes it easier to identify what helped.
Test the UTF-8 setting
The UTF-8 checkbox is not a universal “fix text” switch. Some apps work better with it enabled; others expect an older code page and can malfunction when it is enabled. Microsoft has documented cases involving legacy C runtime libraries where clearing the checkbox was part of the workaround.
If UTF-8 is currently enabled
- Clear Beta: Use Unicode UTF-8 for worldwide language support.
- Leave the system locale unchanged for this first test.
- Select OK, confirm any prompts, and restart the PC.
- Open the app and check the same menus, labels, or sample file that previously looked wrong.
If the text is now readable, test any other important legacy apps before calling the job done.
If UTF-8 is currently disabled
Leave it disabled initially and try the locale adjustment below. That is often the more targeted test for an app designed around a particular legacy language.
Success looks like: The affected text displays as the expected words or characters, not merely different-looking symbols.
Test the app’s expected system locale
If turning off UTF-8 did not solve the problem—or it was already off—try matching the system locale to the language expected by the app:
- Return to Control Panel > Region > Administrative > Change system locale.
- With the UTF-8 checkbox cleared, choose the appropriate language under Current system locale. For a legacy Japanese app, for example, try Japanese (Japan).
- Select OK, confirm any prompts, and restart the PC.
- Reopen the app and test the same text and a copy of the affected data.
- Check other important legacy apps for unexpected changes.
Changing the locale can affect other non-Unicode programs, so a fix for one app can be a regression for another. Microsoft’s documentation also notes that locale changes require administrator permission and take effect after a restart.
Try UTF-8 if the legacy locale did not help
If the app or its documentation indicates that it expects UTF-8, testing the checkbox may be worthwhile:
- Return to Change system locale.
- Select Beta: Use Unicode UTF-8 for worldwide language support.
- Select OK and restart.
- Reopen the app and test the same content. Also test other programs that rely on older text encodings.
If the app becomes less reliable or other programs start displaying garbled text, reverse the change. UTF-8 can represent a wide range of characters, but an older app may still assume a different encoding.
If text is still garbled
A system locale change cannot fix every text problem. Check these possibilities before making more changes:
- Only one imported file is affected: The file may use a different encoding from the one the app expects. Look for an encoding choice in the app’s import or open options, if it offers one. Test with a copy.
- Boxes appear instead of characters: The required font or language support may be missing. That is a different symptom from characters being interpreted using the wrong code page.
- The app overrides Windows’ default: Some applications specify their own code page or encoding, so changing the system-wide setting may not affect them. Microsoft documents per-process code-page settings for applications that support them.
- The app has broader compatibility problems: Check for an update from its publisher. Microsoft also recommends the Program Compatibility Troubleshooter for older apps, though it is not specifically a text-encoding repair tool.
Restore the original settings
If the change does not help, or another program breaks:
- Open Control Panel > Region > Administrative > Change system locale.
- Restore the system locale you recorded.
- Restore the UTF-8 checkbox to its original state.
- Select OK and restart the PC.
- Recheck the affected programs.
Restoring the settings reverses the configuration change; it may not repair data that an application already saved incorrectly. That is why testing with copies matters.