How does windows encodes non English path?

Solution 1:

Both. It would appear that the tool you’re using does not use Unicode-capable Windows APIs. The path that does work is the 8.3 path. It is created for compatibility with DOS applications that do not support long file names.

You can see it using dir /x:

05.01.2022  19:51    <DIR>          0F04~1       א

(Note that א displays as an box with a question mark in it in Command Prompt.)

Whether 8.3 name creation is enabled is a per-volume property. It is enabled by default on the system volume.

Because backslash is the path separator in Windows, it is not an escape character and does not need to be duplicated like you did. This applies to both Command Prompt and PowerShell.