Windows non-ASCII username breaks Python path handling
Cluster 124526 · apps/bootstrap-installer. Data as of
1 open item. Fix merged in #132430 on 4 Oct 2026. Check it covers your case.
The short answer
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #132430. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #132430. That is separate from the fix event. - Still open
- 0 issues and 1 PR.
These items concern a bug where non-ASCII characters in Windows usernames or profile paths cause failures in Python path resolution during installation. A proposed fix involves enforcing UTF-8 console decoding to preserve Unicode paths.
Open issues0
Open PRs1
- PR#124633fix(install): force UTF-8 console decode so non-ASCII profile paths survive
Fixes on record
-
#132430 fix(install): preserve Unicode Python paths on Windows [risk 1.00]
files:
scripts/desktop-update/runtime.ps1,scripts/install.ps1,scripts/tests/test-install-ps1-store-guard.ps1,scripts/tests/test-install-ps1-utf8.ps1,setup-hermes.ps1,tests/scripts/desktop_update/test_desktop_update_runtime_unicode.py
Closed issues · 1
- Closed#124526Windows: non-ASCII character in username breaks `uv` Python path resolution during `python-deps` stage (also affects Desktop app installer)
How this cluster was grouped
-
Link evidence (
structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference. -
Pairwise link density
0.67: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the LabAt a glance
- Subsystem
- apps/bootstrap-installer
- Merged PRs
- #132430
- Closed issues
- 1
- Attempts
- 0 PRs closed without merging
- Fix link checked
- 4 Oct 2026