Unable to launch Loot, WryBash, through Mod Organizer 2

[Simian_Jyhad]

This is a completely Fresh Install of Skyrim SE. all previous files were deleted after uninstall then the game was reinstalled fresh. This is a Steam installation of Skyrim SE. also its a legal copy not a pirated one.

 

So far The error I have gotten most commonly is "Failed to spawn Loot.exe"  Failed to start process (the Parameter is incorrect [87])

 

However I have gotten a similar error only with the number 85.

 

I have completely uninstalled Loot, Wrybash and Mod Organizer 2. Deleted any left over files then reinstalled them.

I have Installed them to the C:\Games folder that I know is not under UAC control. The Install folder name is as short as possible and still be meaningful. Mod Organizer for example is installed to C:\Games\Mo2

I have created exceptions for the install locations and the executables in my anti virus

I have updated/reinstalled Visual C ++ /x86 and /64

 

I have spent the last 4 hours googling and trying various "fixes" to this issue and so far no luck.

SKSE runs fine as do most of the mods though I cant be sure of any mod conflicts without loot/wrybash.

Perkus Maximus seems to run properly as Does FNIS.

 

I verified that the Mod Organizer links for both Loot and Wrybash are pointed at the right executables.

 

I really want to be able to use Mod Organizer instead of NMM due to it keeping my game folder a lot cleaner and uninstalling mods is cleaner. I am stumped as to what could be causing this.

 

 

[Freso]

What version of Mod Organizer 2? (The latest build on GitHub is 2.1.3, there's a newer and more stable version available in the Discord.)

It might also be helpful if you'd provide the logs from a run that gives the error you're seeing.

[Simian_Jyhad]

I am using Mod Organizer 2 build 2.1.3 , I was unaware of a newer version being available in discord. do you happen to know how to get that version? here is a copy/paste of the latest log file

 

 

05:26:10.527 usvfs dll 0.4.0.0 initialized in process 6900

05:26:10.527 [D] remove from process 6900

05:26:10.527 create config in 6900

05:26:10.527 0 processes - 1

05:26:10.527 mod_organizer_instance_1 created in process 6900

05:26:10.527 attached to mod_organizer_instance_1 with 1 nodes, size 65536

05:26:10.527 inv_mod_organizer_instance_1 created in process 6900

05:26:10.527 attached to inv_mod_organizer_instance_1 with 1 nodes, size 65536

05:26:10.527 [D] context current shm: mod_organizer_instance (now 2 connections)

05:27:48.278 mod_organizer_instance_2 created in process 6900

05:27:48.278 tree mod_organizer_instance_2 size now 131072 bytes

05:27:48.283 mod_organizer_instance_3 created in process 6900

05:27:48.283 tree mod_organizer_instance_3 size now 262144 bytes

05:27:48.290 mod_organizer_instance_4 created in process 6900

05:27:48.292 tree mod_organizer_instance_4 size now 524288 bytes

05:27:48.315 mod_organizer_instance_5 created in process 6900

05:27:48.318 tree mod_organizer_instance_5 size now 1048576 bytes

05:27:48.359 mod_organizer_instance_6 created in process 6900

05:27:48.364 tree mod_organizer_instance_6 size now 2097152 bytes

05:27:48.802 mod_organizer_instance_7 created in process 6900

05:27:48.812 tree mod_organizer_instance_7 size now 4194304 bytes

05:27:48.942 mod_organizer_instance_8 created in process 6900

05:27:48.962 tree mod_organizer_instance_8 size now 8388608 bytes

05:27:49.267 mod_organizer_instance_9 created in process 6900

05:27:49.306 tree mod_organizer_instance_9 size now 16777216 bytes

05:27:54.731 injecting to process 8212 with different bitness

05:27:54.731 using usvfs proxy: C:\games\MO2\usvfs_proxy_x86.exe

05:28:04.735 [D] proxy timeout

05:28:04.735 [E] failed to inject: e:\mo2-release\build\usvfs\src\usvfs_helper\inject.cpp(163): Throw in function void __cdecl usvfs::injectProcess(const class std::basic_string,class std::allocator > &,const struct USVFSParameters &,void *,void *)

Dynamic exception type: class boost::exception_detail::clone_impl

[struct tag_message * __ptr64] = proxy didn't complete in time

05:28:04.735 [E] proxy didn't complete in time

15:22:01.683 injecting to process 8848 with different bitness

15:22:01.684 using usvfs proxy: C:\games\MO2\usvfs_proxy_x86.exe

15:22:11.687 [D] proxy timeout

15:22:11.687 [E] failed to inject: e:\mo2-release\build\usvfs\src\usvfs_helper\inject.cpp(163): Throw in function void __cdecl usvfs::injectProcess(const class std::basic_string,class std::allocator > &,const struct USVFSParameters &,void *,void *)

Dynamic exception type: class boost::exception_detail::clone_impl

[struct tag_message * __ptr64] = proxy didn't complete in time

15:22:11.687 [E] proxy didn't complete in time

 

 

[Greg]

It looks as if something is killing the hooking process. If you are on Windows 10, run Windows Explorer, right click on ModOrganizer.exe, and click Properties. If you see a block button or checkbox, click it and click OK to unblock it. You might also do this for LOOT.exe. This may not really be the issue though because it seems Windows 10 blocks the hooking method for everything if ModOrganizer.exe is blocked. It's a bit strange that this is only happening with LOOT. Have you tried running LOOT by itself from say Windows Explorer instead of Mod Organizer?

[Simian_Jyhad]

Turns out that Bit Defender was causing the Hooking process to time out even though there were exceptions set in for it to ignore all of Mod Organizer. Uninstalling Bit Defender fixed the issue thanks for your advice