nolvus skyrim onmodorganiser wont start after windows 11 update

[tnljba2]

The problem:

Briefly describe the issue you are experiencing. Tell us what you were trying to do and what happened instead. Remember, this is not a place to ask questions. For that, go to our Discord server.

novus skyrim doesnt start or initialise after update on windows 11

To Reproduce:

Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'

Environment:

• Mod Organizer Version that exhibits the issue:2.5.2
• Last Mod Organizer Version that did not exhibit the issue (if applicable):
• Desktop OS/version used to run Mod Organizer: Windows 11, version 24H2

Details:

If necessary, describe the problem you have been experiencing with more details and pictures.

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".
[2024-11-15 16:03:20.670 D] timing: MOApplication() 3 ms
[2024-11-15 16:03:20.672 D] timing: main() multiprocess 496 ms
[2024-11-15 16:03:20.674 D] command line: '"C:\Nolvus\Instances\Nolvus Ascension\MO2\ModOrganizer.exe" '
[2024-11-15 16:03:20.675 I] starting Mod Organizer version 2.5.2 revision 9c130cb in C:/Nolvus/Instances/Nolvus Ascension/MO2, usvfs: 0.5.6.1
[2024-11-15 16:03:20.675 I] data path: C:/Nolvus/Instances/Nolvus Ascension/MO2
[2024-11-15 16:03:20.675 I] working directory: C:/Nolvus/Instances/Nolvus Ascension/MO2
[2024-11-15 16:03:20.675 D] timing: MOApplication setup() 2 ms

USVFS:

Create a GIST which is a paste of your latest USVFS log, and link them here.
Do NOT paste your full USVFS logs here, as it will make this issue very long and hard to read!
If you are reporting a bug, always include the USVFS logs!

MO Interface:

Create a GIST which is a paste of your mo_interface logs, and link them here.
Do NOT paste your full mo_interface logs here, as it will make this issue very long and hard to read!
If you are reporting a bug, always include the mo_interface logs!

[JamesWClark]

Meanwhile, a workaround from Reddit (https://www.reddit.com/r/Nolvus/comments/1gq4ohi/crash_log_help/)

This is what got it working for me after the 24H2 update. Depends on your hardware... mine matched the below.

If you selected DLAA and have the Windows 24H2 update, then you have a new issue my analyzer hasn’t been updated for yet:

update is causing the Skyrim Upscaler to break (even the non-paid one from purdark). Crash logs will have a KERNELBASE.dll+C83EA header, and will show SkyrimUpscaler.dll in the probable callstack section.

Affected users: Those who selected DLAA and have Windows 24H2.*

Recommendation(s) for affected users:

Follow the instructions for the PDPerfPlugin crash listed on the Nolvus site, which involves disabling Upscaler Base Plugin and Skyrim Upscaler until either another windows update is pushed or PureDark addresses the issue.