[SOLVED] Crash at start-up on Windows when UTF-8 for worlwide language support is disabled

MixKey
1

Every time I open it this is what appears and the only way to close it is through the Task Manager.

image
image1239×697 39.1 KB

Edit: When I opened it as an administrator everything worked fine.

2

Hi @Studio_Bit

Thank you very much for your feedback.

Sorry to hear that you’re encountering a crash on start up with MixKey. Could you send me your crash as a PM? I will investigate right away.

Cheers

3

The folder is empty and there are no crash files related to it.
I checked on my laptop and it works without any issues.

4

I am seeing that the path is corrupted in the alert dialog. I will report several problems here, thank you that’s very useful!

5

The path is correct My computer is in Hebrew, so it appears as gibberish in the dialog…:wink:

6

Did you install it as Administrator?

In that case it is probably a permission problem when you try to run as standard user, because you can’t read and write to some locations.

Try to reinstall as standard user.

7

If it appears gibberish in the dialog it might be that MixKey is also trying to save it based on a gibberish path. This would be a cascading effect where MixKey does not even save the crashlog on your computer. I have reported the bugs. They will be discussed in the near future with the rest of the team.

Sorry about that and thank you very much again for your invaluable help!

9

No…

10

I found the problem it’s supposed to be enabled:

image
image1426×706 38.6 KB

I have no idea what it is one time it solved a different problem for me.

2 Likes
11

Interesting. So with this option on you are now able to run MixKey in non-admin mode without any crash at start-up?

Which exact version of Windows are you using presently?

12

Yes When the option is enabled, there’s no need to run as administrator.
I’m on Windows 11 25H2.
I’m not using the Insider build.

1 Like
13

@Studio_Bit your finding has probably spared us several hours of nightmarish debugging just to reproduce this crash. Thank you very much.

I have updated the bug report in our bug tracking system. We will still investigate why this disabled option leads to such an unpredictable behavior in MixKey.

2 Likes