Full Support for Non-English Windows (Any Language Pack)
in progress
D
Daniel Rivera
We're making the AutoElevate agent fully reliable on any Windows language pack. Today, UAC detection can misbehave on non-English systems — we're replacing text-based matching with locale-proof identification, so elevation works identically whether your endpoints run Windows in English, Spanish, Chinese, or anything else. We're also adding full Unicode support to custom dialog boxes, so your customized agent messages display correctly in any language or character set. This is in active development, with dialog localization improvements being explored as a follow-on. If you manage international fleets, tell us in the comments which languages you support.
L
Lars Andreas Nilsen
dialog localization improvements should absolutely be a part of this, in my opinion. It's very unhelpful to have all messages default to English when we're based in Norway. We also support multi-language customers, so dialogue-boxes based on the actual device language would be pretty critical. The workaround we have today, is we customize all messages through the settings in AutoElevate. This works ok, but defaults everyone to norwegian, regardless if they use norwegian, english or some other language on their device.
D
Daniel Rivera
Lars Andreas Nilsen: Thanks for the detail, that's useful.
You've identified the limitation correctly: message customization today is a single override, so it can serve one language but not a mixed-language user base. Dialogs following the end user's device language is a separate capability from the work described here, so I've opened a dedicated post for it — "Agent Dialog Localization" on this board — where it can collect votes on its own. Worth adding yours there.
The work in progress on this post is the foundation for it: locale-proof UAC detection so elevation behaves the same regardless of Windows language, plus Unicode support so customized messages render correctly in any character set.
Your case is captured with the request internally. It's in discovery, so no timeline yet.
D
Daniel Rivera
updated the status to
in progress