[BUG] Wrong support for unicode with winget in user folder with non ascii characters

[msimic]

Please confirm these before moving forward

• [X] I have searched for my issue and have not found a work-in-progress/duplicate/resolved issue.
• [X] I have tested that this issue has not been fixed in the latest (beta or stable) release.
• [X] I have checked the FAQ section for solutions.
• [X] This issue is about a bug (if it is not, please use the correct template).

UniGetUI Version

3.1.0

Windows version, edition, and architecture

Windows 11 Pro

Describe your issue

UniGetUI somehow deduces that winget should be located in the following path on my computer:

C:\Users\MRS\AppData\Local\Microsoft\WindowsApps\winget.exe

But this is not correct, it somehow replaced the Š with a S. The correct path is:

C:\Users\MRŠ\AppData\Local\Microsoft\WindowsApps\winget.exe

The end result is that UniGetUI cannot find winget and does not work with it (no packages found). It seems it somehow converted the characterset from Windows-1250 to Windows-1252 or something alike to get an S from a Š. But this obviously should not happen and file paths should be treated as unicode.

Steps to reproduce the issue

Have your user named MRŠ Try to use UnigetUI with winget It cannot find winget

UniGetUI Log

N/A

Package Managers Logs

N/A

Relevant information

No response

Screenshots and videos

[marticliment]

Duplicate of #2239.

Please downgrade to 3.0.2 until I can fix this issue

[marticliment]

Hello,

To all users facing issues with version 3.1.0, please try the new 3.1.1 beta, which aims to fix this issues.

UniGetUI 3.1.1-beta0 release: https://github.com/marticliment/UniGetUI/releases/tag/3.1.1-beta0 Direct installer URL: https://github.com/marticliment/UniGetUI/releases/download/3.1.1-beta0/UniGetUI.Installer.exe

Excuse me for the inconveniences.