Jiwa

I've confirmed the PC is running Windows 10

Error:

System Locale could be wrong. Here's where to check:

https://www.top-password.com/blog/2-way ... e%20effect.

It should be set to "English (Australia)".

Scott.Pearce wrote:System Locale could be wrong. Here's where to check:

https://www.top-password.com/blog/2-way ... e%20effect.

It should be set to "English (Australia)".

This or anything which changes the default character set to a double-byte could cause the issue.

The library we use is old, and is a wrapper around an old Win32API. The wrapper library looks like when it prepares a "buffer" to receive the data in the API call, it's just creating a string of what it has calculated the required length to be - with no consideration for double byte character sets.

I'll log an issue for us to look at better supporting such environments. Version 8 longer uses such archaic libraries and does not suffer this problem. Don't ask when that's going to be released.

SBarnes wrote:

3a437ee2a4cd9e8b214c5310b43b466e.jpg

lol

I can repro the issue on a Windows 10 Environment after changing the system locale to Yi (China), rebooting and then changing the region format to also be Yi (China). Other languages would be affected also (anything double-byte).

EDIT: Logged as DEV-9862

System Locale could be wrong

First thing I checked. I thought that the keystrokes were getting the wrong char set so immediately checked the region settings.
All set to English (aus).

DannyC wrote:First thing I checked. I thought that the keystrokes were getting the wrong char set so immediately checked the region settings.
All set to English (aus).

Be careful - it's somewhat misleading. Make sure the system locale is set as well as the Format.

Sorted!!


The Beta setting was ticked to use UTF-8.

Unticked, rebooted, and login successful!

Really appreciate that effort.

Can you also check what versions of TLS are enabled?

https://techpress.net/disable-tls-1-0-a ... indows-10/