Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Script could fail for various reasons. Like completelly missing the regional pack in some version of windows or insufficient rights which you might not notice.
It affected more games, this worked for all of them, others were just promptly patched. Can you screen the settings? Just to check it's the right one?
The PowerShell script does, in fact, work - as long as you're ok with shutting down Steam, then running the script, then shutting down steam again to get your Culture back.
The problem, as far as I've understood, is that Start-Process won't wait (-Wait) for the right process if steam is already running, so it just switches the Culture back immediately.
A more manual, but less error-prone, fix would be to
A more PS fluent person than me could probably bodge something up with
It was failing if I was trying to start the process from disk (the exe file) directly instead of steam:// since the game restarts itself in that case and the new instance has wrong culture again.
But if that is the case (another game with the same problem, fixed within few days tho, used a launcher that screwed the -Wait as well) I used a simple 20secs delay before reseting the culture back with