Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Windows Server 2022 translation problem #8243

Closed
2 tasks done
wsy opened this issue Apr 7, 2022 · 8 comments
Closed
2 tasks done

Windows Server 2022 translation problem #8243

wsy opened this issue Apr 7, 2022 · 8 comments

Comments

@wsy
Copy link

wsy commented Apr 7, 2022

Version

Microsoft Windows [Version 10.0.20348.473]

WSL Version

  • WSL 2
  • WSL 1

Kernel Version

5.10.16

Distro Version

No response

Other Software

No response

Repro Steps

Fresh install Windows Server 2022 with language Simplified Chinese(zh-cn).
Enable Hyper-V/WSL.
Install WSL2 Kernel.
Run command wsl --set-default-version 2

Expected Behavior

WSL is configured to use WSL2 by default.

Actual Behavior

WSL does not recognize parameter --set-default-version because it has been localized to --设置-默认-版本.
Also, I tried to run wsl --设置-默认-版本 2. However, WSL still does not recognize.
Currently there's no way that I can configure WSL to WSL2.

Diagnostic Logs

I tried to run wsl --help, and in help message, I see a lot of command line options got translated into Simplified Chinese.
I also tried to run wsl --set-version Ubuntu 2 and wsl --设置-版本 2. Both commands are not recognized.
By the way, I tried Simplified Chinese version of Windows 11, this bug does not exist.

@wsy
Copy link
Author

wsy commented Apr 7, 2022

This is a screenshot from Windows Server 2022.
By the way, the --install option got translated as --安装 and the --distribution option got translated as --分发

ScreenshotFromWindowsServer2022

@wsy
Copy link
Author

wsy commented Apr 8, 2022

Hi @benhillis ,
Although this issue is caused by localization. However, its impact is more than localization.
Currently there's no way I can configure my WSL to WSL2. Do you know any workaround that I can configuration my WSL installation as WSL2?

@DesktopECHO
Copy link

Windows Server 2019/2022 does not support WSL2. For a brief time It was in beta builds up to 20298.

What throws people off is that the WSL utilities still reference WSL2, leading to hours of fruitless troubleshooting until they find this is the expected behavior.

@wsy
Copy link
Author

wsy commented Apr 8, 2022

Well, thanks for your answer.
This is quite frustrating to know this after hours of troubleshooting. (I guess WSL2 wasn't stable enough to get into LTSC?)
So, this issue, have two parts.
About the 'cannot switch to WSL2' part, it's 'by design'.
About the 'help message' part, it's indeed purely localization problem.

By the way, I see a lot of localization problems with Windows Server 2019/2022 Server Core installation.
I wonder where I can report them?

@DesktopECHO
Copy link

Unfortunately it's just a 'limitation' based on product differentiation. At this time MS does not want WSL2 in its server OS offerings(1). There has been some discussion about this limitation being lifted, but I won't hold my breath.

The other unfortunate thing to note is that with builds newer than 19044 (Which means Server 2022 and Windows 11) WSL1 has been broken to the point of being unusable, going on 7 months and counting. This was fixed in recent Beta/Insider builds and should show up in the next generally-available release.

Regarding localization, I suggest reporting your issues here.

(1) Recent Non-LTSC versions of Windows Server (feature-stripped, no GUI) can use WSL2, but my understanding is these SAC builds of Windows Server are going away.

@wsy
Copy link
Author

wsy commented Apr 9, 2022

Thanks a lot!

@wsy wsy closed this as not planned Won't fix, can't repro, duplicate, stale Sep 4, 2022
@wsy wsy reopened this Sep 27, 2023
@wsy
Copy link
Author

wsy commented Sep 27, 2023

@DesktopECHO Hi, as Windows Server 2022 now supports WSL2, this problem have become something that Microsoft needs to fix.

@wsy
Copy link
Author

wsy commented Sep 27, 2023

OK. After searching, I found this is duplicate of #8857

@wsy wsy closed this as completed Sep 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants