Here’s a troubleshooting write-up for the issue: “Total War: Three Kingdom crashes after the SEGA logo (following a recent update).”
Sometimes, the crash occurs because the game's launcher or executable is blocked by Windows Defender or a third-party antivirus from connecting to the internet (which it tries to do right after the logo screens).
C:\Program Files (x86)\Steam\steamapps\common\Total War THREE KINGDOMS)..exe files (specifically Three_Kingdoms.exe and the launcher executable).The most common cause. TW3K’s mod manager does not always force-disable incompatible mods after a game update. When the game loads, it attempts to call modded database tables (e.g., cdir_events_mission_option_junctions) that have been renamed or removed by the patch. The engine fails gracefully—or rather, fails to proceed—after the logo sequence. total war three kingdoms crash after sega logo updated
If you have tried all six steps and still crash after the Sega logo, your Windows registry likely has a corrupted AppX deployment for the Game Bar or Xbox Game Bar. This is a known issue with Windows 11 24H2 and Unity/Bink-based games.
The final fix:
Get-AppxPackage *Microsoft.GamingServices* | Remove-AppxPackageGet-AppxPackage *Microsoft.XboxApp* | Remove-AppxPackageThis resolves the "invisible overlay" that crashes the game exactly at the Sega → Menu transition.
Post-update, antivirus software may quarantine or block new executable components (e.g., ThreeKingdoms.exe, BEService.dll). The launcher runs, the logos play, but when the main executable tries to write to cached shader directories or verify DRM, access is denied, leading to a silent CTD. Here’s a troubleshooting write-up for the issue: “Total
Updates can corrupt core files.
A 2024 Windows update quietly removed older VC++ runtimes. Total War: Three Kingdoms needs specific versions from 2015-2022. The Feature: Whitelist the game executables
The Fix:
vc_redist.x64.exe and vc_redist.x86.exe (yes, the 32-bit one; the launcher still uses it) are installed.The test: If the event viewer shows KERNELBASE.dll or MSVCP140.dll as the faulting module, this is your fix.