Обсуждение: BUG #19052: failing to install on Windows if user path contains Chineese/Korean characters

The following bug has been logged on the website:

Bug reference:      19052
Logged by:          Nick Zemlyanskiy
Email address:      zemlyanskiy@nanocad.com
PostgreSQL version: 17.5
Operating system:   OS: Windows 10/11 x64 (local admin)
Description:

Error running C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe
-ExecutionPolicy Bypass -Command
"[System.Globalization.CultureInfo]::GetCultures([System.Globalization.CultureTypes]::AllCultures)
| Where-Object { $_.LCID -ne 127 }  | Sort-Object EnglishName |
ForEach-Object { $_.Name + '=' + $_.EnglishName } | Out-File -FilePath
\"C:\Users\ㅂㅂ\AppData\Local\Temp/postgresql_installer_06853c8c76/locales.txt\"
-Encoding UTF8": Out-File : Cannot perform operation because the wildcard
path C:\Users\??\AppData\Local\Temp/postgresql_installer_06853
c8c76/locales.txt did not resolve to a file.
At line:1 char:215
+ ... ishName } | Out-File -FilePath "C:\Users\??\AppData\Local\Temp/postgr
...

Request

Please confirm whether this is a known issue with Unicode paths in the
Windows installer.

Provide an official fix/patch or documented installer parameters to force an
ASCII-only temp/output path for locales.txt without changing the Windows
account.

If an updated build is available, we’d be happy to test it.

Best regads,
Nick

On Mon, Sep 15, 2025 at 11:33 PM PG Bug reporting form
<noreply@postgresql.org> wrote:
> Please confirm whether this is a known issue with Unicode paths in the
> Windows installer.

Hi,

Sometimes EDB installer help arrives here, but it's not managed by the
core PostgreSQL project and the best place is probably:

https://github.com/EnterpriseDB/edb-installers/issues

You should probably also check recently closed issues, as there were
changes to the way it deals with locale names in recent releases.