FAQ

Questions

If your system and work environment is English, you can ignore this encoding issue.

WARNING

This is actually a rendering issue in Windows Terminal, and other terminals like vscode terminal, Tabby, Hyper, wave works fine.

If you use [console]::OutputEncoding to modify the output encoding of PowerShell, it may cause menu rendering problems.
If you must use it, please ensure that [console]::OutputEncoding is added after Import-Module PSCompletions.
It is also possible that there are other PowerShell modules that have modified the coding internally, which can also cause rendering problems.
If you run into rendering problems, you should first try putting Import-Module PSCompletions in front of it.
If you still have problems, you should empty your $Profile configuration file and try only import PSCompletions by running Import-Module PSCompletions.

Note

If for some special reasons you must enable the Beta option in Regional Settings in the Control Panel, you can consider the following solutions.

If you don’t need command tips.
- Just run the command psc menu config enable_tip 0
If you need command tips.
- Use the command psc config language en-US to change the language configuration to English, because there's no rendering problem with English characters, and the English command tips can be rendered normally.
- Use other terminal shells.
  - Currently, the known terminals in vscode, Tabby, Hyper, wave can be used normally after enabling this option.

Don't check the Beta option in Regional Settings in the Control Panel, as shown below.
Checking it will also cause menu rendering problems.

控制面板-区域设置-Beta