MO2 will not start after update to 2.5.2

[A-F-rog]

The problem:

ModOrganizer 2 will not open after update

To Reproduce:

Steps to reproduce the behavior:

1. Go to - Desktop Shortcut (created during install) or ModOrganizer.exe
2. Click on - Double click or right-click and Run as Administrator
3. No notice in Task Manager, but three .DMP files are generated, all with same file name and -1, -2 extensions.

Environment:

• Mod Organizer Version that exhibits the issue: 2.5.2
• Last Mod Organizer Version that did not exhibit the issue (if applicable): 2.2.2.1
• Desktop OS/version used to run Mod Organizer: Windows 10 Home Version 22H2

Details:

I've been using MO2 for years, the last version I had installed was 2.2.2.1 and it worked without issue yesterday managing separate instances for TESV, Fallout4, Fallout3, and FalloutNV. I noted the "upgrade available" for Version 2.5.2, so authorized the update through MO2 interface. Now MO2 will not start. It does not show up in Task Manager at all, but produces three DMP files in the MO2 installation directory (where the .exe is). I've conducted searches for the ModOrganizer.ini file (based on other troubleshooting steps found on-line), but I cannot find this file on the installation drive. I also cannot find logs for either USVFS or mo_interface, but feel that since 2.2.2.1 was working, I should have those files somewhere. My installation is on my G:/ drive, perhaps logs are located elsewhere.

Adding to everything above, I have also attempted a download and fresh install directly from Nexus after experiencing issues with the auto-update feature in MO2. There were no significant changes as detailed above. I have also located the log files and linked them below.

Link to Mod Organizer logs:

Right click on the log window at the bottom of MO2, set log level to debug, restart Mo2 and reproduce the problem.
To access the log files you can press the Open folder icon over the modlist and select "Open MO2 Logs folder".

USVFS:

<script src="https://gist.github.com/A-F-rog/7ac9d44c9f8cfa2750f45c47549f9cdd.js"></script>

MO Interface:

<script src="https://gist.github.com/A-F-rog/03b9f95ecc74fd7b57646eaee72a5ab5.js"></script>

[Swerner1975]

Maybe you must download and install Microsoft Visual C++ Redistributable 14.40.33810.0.

see: https://github.com/ModOrganizer2/modorganizer/releases

I had the same problem, but it was solved after install this package.

[A-F-rog]

This was the issue. After installing 14.40.33810, everything worked as expected. Thank you!

[Ubiquin96]

Maybe you must download and install Microsoft Visual C++ Redistributable 14.40.33810.0.

see: https://github.com/ModOrganizer2/modorganizer/releases

I had the same problem, but it was solved after install this package.

Thanks you. This worked for me once I repaired my version

[edwardcc83]

Having this same problem...

Performed a new install after formatting my laptop, wasn't running until I installed the Microsoft Visual C++ Redistributable. Worked fine last night as I was able to play Fallout for a bit. This morning, it stopped working again. Tried installing all the C++ redistributable, re-downloaded ModOrganizer, and still no luck.

[merovign]

MO upgraded itself to 2.5.2 today and could not start game (no error visible, something flashed momentarily but wasn't readable). Game was Starfield. Already on VCC+ 14.40.33810.0 (reinstalled and restarted PC for good measure, no improvement). Worked as expected up until today (last run I think on Sunday or Monday). No other system updates, game not updated during that time (run via SFSE). Didn't crash so no crash logs, did not see anything that looked like an error in log;

usvfs-2024-10-04_04-00-15.log

[DavidNRG1]

MO upgraded itself to 2.5.2 today and could not start game (no error visible, something flashed momentarily but wasn't readable). Game was Starfield. Already on VCC+ 14.40.33810.0 (reinstalled and restarted PC for good measure, no improvement). Worked as expected up until today (last run I think on Sunday or Monday). No other system updates, game not updated during that time (run via SFSE). Didn't crash so no crash logs, did not see anything that looked like an error in log;

usvfs-2024-10-04_04-00-15.log

I have the same issue... MO 2.5.2 crash loading Starfield. Any solution?