cmder: It is not work properly in windows 11

Clink v1.2.42 should fix the issue with non-ASCII account names even when the system code page is not UTF8.

It might be anti virus blocking Clink from running.

See #2546 for troubleshooting.

Overview: download the latest clink ZIP file from here, and extra the contents into Cmder’s vendor\clink sub-directory. Then start Cmder, and share the config\clink.log file here (under Cmder’s root directory).

Who have the same problem, just active “Beta: UTF8”, download de Clink below and replace all on the cmder/vendor/clink

Clink v1.2.42 should fix the issue with non-ASCII account names even when the system code page is not UTF8.

I think you must have set UTF8 as the system code page on Win10, but didn’t set that up yet on Win11.

Clink is accidentally passing a UTF8 string to the system API that expects a string using the system code page. The only way that could be working on Win10 is if you set the system code page to be UTF8, which is not the default. And the Win11 computers must be using the default still, instead, thus it’s not working on them.

Anyway, the next update of Clink will fix that.

Or you can set the Win11 computers to use UTF8, and that would also make it work without updating Clink.

Now everything is normal

Thank you for your patience to help me solve the problem.

I think you must have set UTF8 as the system code page on Win10, but didn’t set that up yet on Win11.

Clink is accidentally passing a UTF8 string to the system API that expects a string using the system code page. The only way that could be working on Win10 is if you set the system code page to be UTF8, which is not the default. And the Win11 computers must be using the default still, instead, thus it’s not working on them.

Anyway, the next update of Clink will fix that.

Or you can set the Win11 computers to use UTF8, and that would also make it work without updating Clink.

You are right ! I set it ,and it works now!