rockerbacon / modorganizer2-linux-installer

An easy-to-use Mod Organizer 2 installer for Linux
GNU General Public License v3.0
992 stars 79 forks source link

couldn't load in-process dll L"C:\\windows\\system32\\msxml3.dll -> vc_redist.x86.exe /q returned status 5 #247

Closed Banacizo closed 2 years ago

Banacizo commented 3 years ago

Installation would always fail with sha256sum failure regardless of what vc_redists I tried, so I grabbed both the latest exes from microsoft.com and added --force to the .yml. Now it fails a bit later and I got absolutely no idea what to try:

warning: Running /usr/bin/wineserver -w. This will hang until all wine processes in prefix=/home/banacizo/.local/share/Steam/steamapps/compatdata/377160/pfx terminate
------------------------------------------------------
Executing cd /home/banacizo/.cache/winetricks/vcrun2019
Executing wine vc_redist.x86.exe /q
0014:err:module:map_image Could not map section .reloc, file probably truncated
0014:err:ntoskrnl:ZwLoadDriver failed to create driver L"\\Registry\\Machine\\System\\CurrentControlSet\\Services\\MountMgr": c0000142
001a:err:module:map_image Could not map section .rsrc, file probably truncated
001a:err:ntoskrnl:ZwLoadDriver failed to create driver L"\\Registry\\Machine\\System\\CurrentControlSet\\Services\\wineusb": c0000142
0030:err:module:map_image Could not map section .reloc, file probably truncated
0030:err:ntoskrnl:ZwLoadDriver failed to create driver L"\\Registry\\Machine\\System\\CurrentControlSet\\Services\\nsiproxy": c0000142
0036:err:ntoskrnl:ZwLoadDriver failed to create driver L"\\Registry\\Machine\\System\\CurrentControlSet\\Services\\NDIS": 00000001
0039:err:module:map_image Could not map section .rsrc, file probably truncated
0009:err:module:map_image Could not map section .rsrc, file probably truncated
0009:err:ole:COMPOBJ_DllList_Add couldn't load in-process dll L"C:\\windows\\system32\\msxml3.dll"
0009:err:ole:CoGetClassObject no class object {f6d90f11-9c73-11d3-b32e-00c04f990bb4} could be created for context 0x1
------------------------------------------------------
warning: Note: command wine vc_redist.x86.exe /q returned status 5. Aborting.
------------------------------------------------------
Monitored process exited.
Initial process has exited (return code: 256)
All processes have quit
Exit with return code 256

A basic google search suggests its something to do with 32bit support? I am pretty new to this, what am I missing?

Banacizo commented 3 years ago

Further developments: I have downloaded both vc_redists from links in #215, then used sha256sum and patched the values directly into winetricks script, and the 256 error no longer appears even without using --force. wine vc_redist.x86.exe /q returned status 5, however, persists. I have found this a couple of paragraphs above in the log: warning: ucrtbase.dll is no longer included in vcrun2019. For details see: https://github.com/Winetricks/winetricks/issues/1770 So I presumed something was missing from the newer vcrun that was necessary to use the command, but internet search indicates that "status 5" was a thing as far back as 2016, and lack of ucrtbase should return "status 53". Judging from the log, wine seems to work around this successfully so this is not the problem.

Banacizo commented 3 years ago

Also probably worth mentioning: Every attempt at installing I replace return with exit in the find-library-for-appid.sh, otherwise it fails saying it couldnt find my Fallout 4. I have also double checked that the Proton Version is set to 5.0-10 in both Steam play settings and Game compatibility properties. Sadly, it fails to launch with this setting with no error message given, but if I set Proton back to 6-18-GE-2, it runs just fine. I do not know if game's preferred proton version is important at this stage, since im yet to install MO successfully.

Banacizo commented 3 years ago

I understand that this has something to do with mxml3.dll but I have no idea how to add it to the installation.

Banacizo commented 2 years ago

FIXED! By wiping compatdata in the appropriate library and re-generating it with proton 5.0.10. Warning: If after generating compatdata with Proton 5 you switch it to another version, the game will not launch until you re-generate compatdata again! You will also have to reinstall your MO.