Receiving Error 87 when attempting to launch LOOT, and only LOOT, via MO2.

TheMerricat commented 3 years ago

The problem:

Launching LOOT via MO2 produces the following error:

Error 87 ERROR_INVALID_PARAMETER: The parameter is incorrect. (0x57)
 . binary: 'C:\LOOT\LOOT.exe'
 . owner: BUILTIN\Administrators
 . rights: (normal rights)
 . arguments: '--game="Skyrim Special Edition"'
 . cwd: 'C:\LOOT'
 . stdout: no, stderr: no, hooked: yes
 . MO elevated: no
 . usvfs x86:ok x64:ok proxy_x86:ok proxy_x64:ok

all other executables, such as Wrye Bash, Bodyslide, SEEdit, zEdit, and etc. launch without issue.

To Reproduce:

Steps to reproduce the behavior:

Launch MO2 - Select LOOT from the executables list, click run.

Environment:

Mod Organizer Version that exhibits the issue: 2.3.2
Last Mod Organizer Version that did not exhibit the issue (if applicable): NA
Desktop OS/version used to run Mod Organizer: Windows 10 - Version 2004(OS Build 19041.746)

Extra Details:

Before coming here I googled for the issue and went to the discord and looked for the issue. I have tried every thing listed that I could see.

LOOT launches on it's own without issue.
I have repaired the Visual C++ redist linked on the Nexus page and rebooted afterwards.
I have deleted the LOOT files in AppData/Local/LOOT, and run it again outside of MO2. Then tried in MO2 again.
I have reinstalled MO2 on top of itself.
I have added LOOT & the MO2 install folders to the Defender exclusion lists.
I have added usvfs_proxy_x64.exe, usvfs_proxy_x86.exe, and ModOrganizer.exe as process exclusions to Windows Defender.
I have disabled Windows Defender. (AFIAK, and I've looked very very hard, there are no other AV/protection type software running on this PC.)
I have run MO2 with elevated privileges and without.
I have installed LOOT in a folder outside of the Program Folders directories

I have been able to create a new install of MO2 with nothing added to it and launch LOOT via that, and this install was made at the same time as I overwrote the original 'broken' install, while Defender was disabled.

The 'working' install with nothing in it is also a portable install and is installed in a 'sibling' folder next to the one I'm actually working on.

I would prefer to identify what the issue in the broken install is rather than attempting to move my profile over to the working install because I'm currently tracking the broken install via SVN and it would be a huge effort for me (i.e. several days for the 250gig of mods) to swap folders and not completely screw up the tracking. This is a portable install created via Wabbajack initially (the Living Skyrim 2 mod list) and I've been slowly editing it myself to my own liking. Unfortunately this was the first time I attempted to launch LOOT via it so I don't know if the issue was always there or not.

Are there any other things I should be trying before tossing in that towel?

Link to Mod Organizer logs:

Both the MO Interface log and the USVFS log from a failed run are listed in this gist. I saw no other log files but those.

USVFS:

See above.

MO Interface:

See above.

Neverdusk commented 3 years ago

I'm receiving the same error when trying to run LOOT, but it also happens with Wrye Bash, Mator Smash. However, this issue only started for me upon updating to 2.4.

Edit: I solved the issue by manually downloading the archive version and placing usvfs_proxy_x86 in the Mod Organizer 2 folder. Apparently MO2 had updated incorrectly and didn't install this specific file.

SpectreSpecter commented 3 years ago

Getting this bug as well, except I am using a linux version of MO2 by Rockerbacon and a verion of LOOT directly from the AUR that can run on Linux. This is the post I made about it on rockerbacon's version of MO2: https://github.com/rockerbacon/lutris-skyrimse-installers/issues/236

ModOrganizer2 / modorganizer