MO2 won't start Skyrim SE in W11

[vabatta]

Hi everyone,

I have a portable installation of MO2 on a different drive than the OS, same drive where Skyrim is installed, and since I updated to Windows 11 I can't start Skyrim through MO2 either with or without all mods, SKSE. If I start it from outside of MO2 in any way, it works fine (with SKSE too). What could be the issue?

Logs

01:35:59.283 usvfs dll 0.5.6.0 initialized in process 18156
01:35:59.284 [D] remove from process 18156
01:35:59.284 create config in 18156
01:35:59.284 0 processes
01:35:59.284 mod_organizer_instance_1 created in process 18156
01:35:59.284 attached to mod_organizer_instance_1 with 1 nodes, size 4,194,304 B
01:35:59.284 inv_mod_organizer_instance_1 created in process 18156
01:35:59.284 attached to inv_mod_organizer_instance_1 with 1 nodes, size 131,072 B
01:35:59.284 [D] context current shm: mod_organizer_instance (now 2 connections)
01:35:59.284 [D] clearing blacklist
01:35:59.284 [D] blacklisting 'Chrome.exe'
01:35:59.284 [D] blacklisting 'Firefox.exe'
01:35:59.284 [D] blacklisting 'TSVNCache.exe'
01:35:59.284 [D] blacklisting 'TGitCache.exe'
01:35:59.284 [D] blacklisting 'Steam.exe'
01:35:59.284 [D] blacklisting 'GameOverlayUI.exe'
01:35:59.284 [D] blacklisting 'Discord.exe'
01:35:59.284 [D] blacklisting 'GalaxyClient.exe'
01:35:59.284 [D] blacklisting 'Spotify.exe'
01:35:59.284 [D] clearing forced libraries
01:36:02.417 ran out of memory in tree mod_organizer_instance_1, will create another one
01:36:02.417 creating mod_organizer_instance_2
01:36:02.417 mod_organizer_instance_2 created, activating
01:36:02.428 will destroy mod_organizer_instance_1
01:36:02.428 tree mod_organizer_instance_2 size now 8,388,608 B
01:36:02.428 destroying mod_organizer_instance_1
01:36:02.475 ran out of memory in tree mod_organizer_instance_2, will create another one
01:36:02.475 creating mod_organizer_instance_3
01:36:02.475 mod_organizer_instance_3 created, activating
01:36:02.498 will destroy mod_organizer_instance_2
01:36:02.498 tree mod_organizer_instance_3 size now 16,777,216 B
01:36:02.498 destroying mod_organizer_instance_2
01:36:02.642 ran out of memory in tree inv_mod_organizer_instance_1, will create another one
01:36:02.642 creating inv_mod_organizer_instance_2
01:36:02.642 inv_mod_organizer_instance_2 created, activating
01:36:02.642 will destroy inv_mod_organizer_instance_1
01:36:02.642 tree inv_mod_organizer_instance_2 size now 262,144 B
01:36:02.642 destroying inv_mod_organizer_instance_1
01:36:02.675 ran out of memory in tree mod_organizer_instance_3, will create another one
01:36:02.675 creating mod_organizer_instance_4
01:36:02.675 mod_organizer_instance_4 created, activating
01:36:02.719 will destroy mod_organizer_instance_3
01:36:02.719 tree mod_organizer_instance_4 size now 33,554,432 B
01:36:02.719 destroying mod_organizer_instance_3
01:36:02.964 ran out of memory in tree mod_organizer_instance_4, will create another one
01:36:02.964 creating mod_organizer_instance_5
01:36:02.964 mod_organizer_instance_5 created, activating
01:36:03.054 will destroy mod_organizer_instance_4
01:36:03.054 tree mod_organizer_instance_5 size now 67,108,864 B
01:36:03.054 destroying mod_organizer_instance_4
01:36:03.268 [D] clearing forced libraries
01:36:03.278 injecting to process 21840 with same bitness
01:36:03.278 dll path: S:\Modding\MO2\usvfs_x64.dll
01:36:03.278 injection to same bitness process 21840 successful
01:36:03.318 usvfs dll 0.5.6.0 initialized in process 21840
01:36:03.390 usvfs dll 0.5.6.0 initialized in process 23612
01:40:38.689 updating parameters:
 . debugMode: false
 . log level: error
 . dump type: full
 . dump path: S:/Modding/MO2/crashDumps
 . delay process: 0ms
01:41:10.436 usvfs dll 0.5.6.0 initialized in process 7436
01:41:10.561 usvfs dll 0.5.6.0 initialized in process 14940

Edited July 5, 2022 by vabatta

[vabatta]

Apparently, copying over the default INIs plus reinstalling scrumbled bugs and sse engines fixes actually fixed the issue. Thanks!

[GSDFan]

Try creating a new profile with default game INI settings and no mods enabled. Then from the "Pick a program to run" drop down select the fallout launcher and start the game and see what happens.