zertul

I did some further digging into it. In the Windows Event log I found an entry that complained about missing files for "GameServices". Upon a bit of googling I found a tool from Microsoft that was supposed to fix this issue: GamingRepair.exe So, turns out, that's probably just literally the binary they ship additionally to the game which gets stuck, probably some kind of timeout because it detects errors it can't fix. Executed it myself and it gives you some output - error blabla. Further googling, none of the fixes worked. I ended up having to do an inplace upgrade of Windows that fixed the GameServices, since none of the resolutions I found online to fix it worked. If you have this issue, you also can't use the Xbox App, it will error out. Having the GameServices finally repaired, the Xbox App started to work properly again. Afterwards the Steam Version of the game launched without any problems in like, 20 seconds tops. No issues since, I have 8 hours in the game now.

I've waited about 30 minutes and then the game started. I didn't see the shader compiling part, although that might be because I've been making breakfast; I've only heard the audio coz I was still wearing my headset. However, after adjusting some graphic settings it told me to restart the game. Did so, and so far same procedure: "Running install script ("GamingRepair.PROGRAM")" After 14 minutes it changed to running, in the Taskmanager there is an "Avowed" process running, but game is not starting. After 24 minutes the game finally started. That's.. harsh. Waiting 24 minutes to play the game is a bit much. I never saw any shaders compiling dialogue. I'm in my third restart now, 15 minutes in... sorry, but even if the game starts and is playable (not sure yet if it really is), 20+ minutes to start the game is just too much, there's something wrong!pbYw