Simply put, my issue is every time I launch a multiplayer game (specifically multiplayer) the game will crash to the main menu upon reaching the end of the loading text.. "and all of that is me... Auriga." This problem has only occurred since installing Inferno. I'd also add that when I disable Inferno in steam I still have the issue.

My status never makes it past "loading" to "ready" and the game promptly kicks me out to the main menu. For the other players connecting to my game, it tells them I, the host, have "disconnected" from the game. 

I do not receive any specific errors. I am just removed from the game loading screen and kicked back to the main menu.

The possible solutions I have tried include, updating drivers (most recent update 8/02/18), disabling UAC, disabling windows firewall (I do not use a 3rd party anti-virus), enabling administrator mode for Endless Legends.exe, verifying the game cache (was verified 100%), and reinstalling the game. 

EDIT: I just tried many of the suggested fixes on the Common Issues and Fixes Post. I tried the 32-bit version, each command line option, and made documents no longer read-only.

Nothing has helped with my issue, every attempted fix still resulted in the game kicking me to the main menu when hosting. 

System Specs: 

Windows 10

Resolution: 2560 x 1440

Game Version: V1.6.2 S3 (64-Bit)

output_log.txt

Diagnostics.zip

Registry.xml

EDIT: While I don't know what it means, I did notice this error in the diagnostics: 

15:09:47:215STACKAn error has occurred while loading the new technique. Sharing violation on path C:\Users\John\OneDrive\Documents\Endless Legend\Temporary Files\a3d2e843-0142-4aa7-a6ed-25ce0d758025\Default_V1.geo at System.IO.FileStream..ctor (System.String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, Boolean anonymous, FileOptions options) [0x00000] in :0 at System.IO.FileStream..ctor (System.String path, FileMode mode, FileAccess access, FileShare share) [0x00000] in :0 at (wrapper remoting-invoke-with-check) System.IO.FileStream:.ctor (string,System.IO.FileMode,System.IO.FileAccess,System.IO.FileShare) at System.IO.File.Open (System.String path, FileMode mode, FileAccess access) [0x00000] in :0 at Amplitude.IO.Archive.Open (System.String filePath, ArchiveMode archiveMode) [0x00000] in :0 at DefaultWorldViewTechnique+c__Iterator6C7.MoveNext () [0x00000] in :0 at Amplitude.Coroutine.Run () [0x00000] in :0 at Amplitude.Coroutine+c__IteratorA2.MoveNext () [0x00000] in :0 

I was able to fix this issue by changing permissions in windows regarding libraries. Was difficult to find the solution as it was really an issue with how windows handles libraries/one drive.

Apparently, there is a distinction between "documents" and the "documents" found inside libraries... NJ Microsoft.