ID 496376 - Usernames with non-ASCII characters that are being used in conjunction with an OS that has a non-Unicode based language causes Nuke 13 from being unable to startup

Follow

Problem summary
Usernames with non-ASCII characters that are being used in conjunction with an OS that has a non-Unicode based language causes Nuke 13 from being unable to startup

Customer reported version
nuke.13.1v1

Customer reported platform
windows10

Steps to reproduce

1) Create a user with non-ASCII characters like "भारत" and login to your new account

2) Open the Settings Panel

3) Select the Time & Language option

4) Select the Region option on the left-hand side

5) Click Additional date, time, & regional settings under the heading Related settings in the top right of the window

6) Click on Region

7)Select the Administrative tab

8) Click Change system locale...

9) Click the drop-down menu and change the language to Russian (Russia) and restart your PC

10) Login to your non-ASCII account and try running Nuke 13


Expected behaviour
For Nuke to be able to start up correctly

Actual behaviour
Nuke tries loading _pathsetup.py and encounters an error

Loading C:/Program Files/Nuke13.1v1/plugins/arriSDKLoader.dll
Loading C:/Program Files/Nuke13.1v1/plugins/_pathsetup.py
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xcf in position 9: invalid continuation byte


Workaround
1. Enabling UTF-8 on Windows helps to resolve the issue.
For Windows 10:
  1. Open the Settings Panel
  2. Select the Time & Language option
  3. Select the Region option on the left-hand side
  4. Click Additional date, time, & regional settings under the heading Related settings in the top right of the window
  5. Click on Region
  6. Select the Administrative tab
  7. Click Change system locale...
  8. Tick on Beta: Use Unicode UTF-8 for worldwide language support and click OK (If you are asked to restart please restart Windows to complete the change)

2. Alternatively you can change or create a new username without non-ASCII characters.


Reproduced by support
This bug has been reproduced in:
Nuke 13.1v1 - Windows 10
Nuke 13.0v5 - Windows 10
Nuke 13.0v1 - Windows 10 - Regression

Unable to reproduce bug in:
Nuke 12.2v9 - Windows 10

Earliest version tested
Nuke 12.2v9 - This issue doesn't appear in this version and has regressed


    We're sorry to hear that

    Please tell us why