Tourniquet

Hey there, my partner and I are having this exact problem. She has an ASUS ROG gaming laptop and every server she joins crashes before her character spawns in. The log messages are identical to what has already been shared here (with the exception of the player name/ID) so I won't bother repeating that. This evening we've tried testing the problem. I've hosted a game on my machine and she's joined using her laptop - my game crashes completely and her game gives a message about the server being unavailable. We then tried having me log in to Steam on her laptop and her on mine and if she hosts a game on my PC and I join via her laptop the game on my PC once again crashes. Her laptop can happily host games which others can join with no problem, but as soon as she tries to join a game using her laptop the host crashes. I've just checked the Event Viewer and there is something which is common to all the times a crash occurs - an RPC warning: Application ("C:\Program Files\WindowsApps\Microsoft.XboxGamingOverlay_5.621.4142.0_x64__8wekyb3d8bbwe\GameBarFTServer.exe" -Embedding) (PID: 26592) has failed to complete a COM/RPC call because of an invalid message from server. User Action Try the operation again. If the problem persists, contact your system administrator. I'm not sure what XboxGamingOverlay is but it's the only Event Viewer log and it the warning gets logged within 1 second of the crash happening every single time. We found a not massively useful workaround: if the host has the in-game terminal window open the crash does not happen (and for clarity the above XboxGamingOverlay warning does not trigger). This is all well and good when playing with someone who you know is about to join, but considering the game on my partner's laptop is able to crash any game it joins it's not useful for the wider public. Edit: Disabling Xbox Game Bar fixes the problem! With this disabled my partner's laptop can happily join other people's games without them crashing. I guess this is something the dev team will need to fix in the game itself though, but for now everything appears to be running as expected with that disabled.