Check the language options in the installed version before adding external files. The project also documents translation DLL locations for builds that use them. Match any language resource to the program and keep a known-working configuration.
What to do
- Note the installed Open-Shell version and inspect the settings language options with Show all settings enabled when necessary. Distinguish the menu language from Windows display language.
- Read the project translation guidance for the resource you intend to use. Avoid DLLs from unrelated download pages or a different application.
- When the documented method requires a language DLL, use the project-listed installation or Languages location and preserve the original resource. Review file provenance before loading any DLL.
- Reopen the settings dialog or sign in again as directed by the project guidance. Test labels, keyboard navigation, and a normal search query in the chosen language.
Check the result
Confirm that the desired labels changed and that long translations do not overlap or hide controls. Keep the original language available for troubleshooting.
Limits & precautions
A language resource is executable-format content, not merely a text document. Menu translation also does not change the language of every application or Windows system screen.
Questions & answers
Does changing Open-Shell language change Windows language?
No. They are separate settings.
Can I use any file named language.dll?
No. Use resources and locations described by the project and check compatibility and provenance.
Sources & scope
Documentation checked October 30, 2026. These instructions are documentation-led, not a claim of hands-on testing on your Windows build.