WeMod crashes with Japanese system locale

[manic egret]

Hi, I encountered a critical crash when launching WeMod on Windows 11 using Japanese system locale (ja-JP).

The application crashes during startup, and the error trace suggests a .NET resource lookup recursion issue.
When I switch my Windows display language and system locale to English (en-US), WeMod works perfectly.
Switching back to Japanese reproduces the crash every time.

This issue appears related to this known .NET runtime bug:
https://github.com/dotnet/runtime/issues/36715

Is this a known issue with WeMod? Are there plans to handle regional locale failures more gracefully?

Happy to provide logs, screenshots, and environment details.

[neat wind]

Hey @manic egret, I'm locking this feedback ticket #1361493139520487565 message as it’s related to your current support ticket. I also noticed you're on a old version of WeMod (9.14, from 2024). Have you tried fully uninstalling WeMod, removing all residual files, and then reinstalling it while using the Japanese version?

[manic egret]

Apologies if I caused any confusion by posting in multiple channels earlier.

Regarding the version—thank you for pointing out that I'm on an older one (9.14).
I downloaded WeMod using the official website's download button, which gave me Setup.exe.
Is there a different place where I can get the latest version, or a way to ensure I'm installing the most up-to-date release?

I'd appreciate any guidance. Thanks again!

[neat wind]

https://api.wemod.com/client/download

Please make sure your Windows is up to date too. If the problem still occurs, I'll forward this to the team and have a support member reach out when available.

[manic egret]

Thanks for your continued support.

Unfortunately, even after fully updating Windows and completely removing all WeMod-related files (AppData folders and relevant registry entries), the issue still persists.

I'm currently on Windows 11 Home, Version 24H2, Build 26100.3775 — fully up to date via Windows Update.

Upon launching WeMod with Japanese system locale, the exact same crash occurs (attached screenshot).

Let me know if I can provide further logs or environment details to help isolate the issue.

[neat wind]

Thanks for providing this! What version of .NET are you on?

[manic egret]

Thanks for your reply.
Here are my current .NET versions — please let me know if everything looks okay.

OS Name: Windows
OS Version: 10.0.26100
OS Platform: Windows
RID: win10-x64
Base Path: C:\Program Files\dotnet\sdk\7.0.410\

Host:
Version: 7.0.20
Architecture: x64
Commit: 0fb6ac59fb

.NET SDKs installed:
6.0.428 [C:\Program Files\dotnet\sdk]
7.0.410 [C:\Program Files\dotnet\sdk]

.NET runtimes installed:
Microsoft.AspNetCore.App 6.0.36 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 7.0.20 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.NETCore.App 6.0.36 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 7.0.20 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.WindowsDesktop.App 6.0.36 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 7.0.20 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]

[neat wind]

Try running this repair tool https://learn.microsoft.com/en-us/dotnet/framework/install/repair , If it doesn't change anything i'll wait for a response from the team.

[manic egret]

Sorry for the delay — I was caught up with work!

I’ve run the .NET Framework Repair Tool and restarted my PC as instructed, but unfortunately the same error is still occurring (screenshot attached).

Let me know if there’s anything else I can try, and thanks again for your support!

Just to summarize where we’re at — I’ve followed all the instructions (clean reinstall, .NET repair, full Windows update), and the crash persists only when the system locale is set to Japanese (ja-JP).

Even if WeMod is installed under English and then switched back to Japanese, Update.exe fails with the known mscorlib recursive resource lookup bug caused by Arg_BadImageFormatException.

This strongly suggests that the crash is due to .NET’s ResourceManager failing to resolve Japanese resources and entering an infinite loop — a known behavior unless proper culture fallback (e.g., to en-US) is implemented.

The issue is very likely fixable on the WeMod side by adjusting how Update.exe handles resource fallback or exception handling.

Let me know if I can help further or test a build with improved culture handling.