Free tools Windows power users keep installed
One-click scans. No signup required.
Start with this order: disable every mod, verify the game files, back up your saves, reset Bannerlord’s configuration, then check Windows Security and GPU selection. These steps address the most common causes of Bannerlord doing nothing after Play, closing at Preparing to Launch, crashing after the TaleWorlds intro, or failing while loading a campaign or battle.
There is no single universal fix. The correct solution depends on whether the failure is caused by a mod, damaged installation file, stale configuration, blocked Documents folder, missing Microsoft runtime, graphics initialization, memory pressure, or a specific damaged asset.
Identify the type of crash first
| Symptom | Most useful first checks |
|---|---|
| Play changes to Stop, then returns to Play | Disable mods, verify files, check antivirus and dependencies |
| Launcher opens and immediately closes | Reset Configs, remove stale launcher data, check OneDrive, try a direct executable |
| Crashes after the TaleWorlds video | Verify files, clear shaders, investigate UI sprite files and GPU selection |
| Only a modded save crashes | Test a new vanilla campaign; suspect mod, version, DLC, or save incompatibility |
| Only battles or sieges crash | Check VRAM, RAM, page-file configuration, graphics settings, and drivers |
| Only multiplayer fails | Repair BattlEye and reset multiplayer-specific data |
| The entire PC freezes or reboots | Investigate drivers, temperatures, RAM, power, overclocking, and Windows stability |
Meeting the minimum specification does not guarantee stable performance in Bannerlord’s large battles. The current Steam listing specifies a 64-bit operating system, 6 GB RAM, and hardware such as a GTX 660 2 GB or Radeon HD 7850 2 GB at minimum. Its recommended specification is 8 GB RAM and a GTX 1060 3 GB or RX 580-class GPU. Integrated graphics require additional system memory.
There is also a platform distinction: the store page still displays Windows 7 as the game’s minimum operating system, but the Steam Client itself requires Windows 10 or later. A Windows 7 installation can therefore have a client-support problem even when the game listing shows Windows 7.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
As an Amazon Associate I earn from qualifying purchases.
Before changing files: protect saves
Close Bannerlord and Steam before renaming or deleting anything. Back up this folder:
C:Users<username>DocumentsMount and Blade II Bannerlord
At minimum, copy the Game Saves folder somewhere outside Documents. Do not load a save that depends on disabled mods. Test the main menu or a new vanilla campaign instead; loading a modded save without its required modules can cause further problems or damage the save.
If Documents is redirected through OneDrive, also make a separate backup before changing synchronization settings.
#1 Best Overall
Quick fixes to try in order
- Restart Steam and Windows. Allow pending game, Windows, and graphics-driver updates to finish.
- Disable all mods. Use the Bannerlord launcher if it opens. If it does not, temporarily move third-party folders out of the game’s
Modulesdirectory rather than deleting them. - Verify the installation. In Steam, open Library, right-click Bannerlord, choose Properties, open Installed Files, and select Verify integrity of game files. Client labels can vary by version. Use Epic’s equivalent verification option if you own the Epic edition.
- Start a new vanilla campaign. If that works while an old save does not, the installation is less likely to be the problem.
- Re-enable mods gradually. Add them in small groups, beginning with required frameworks, and confirm that each mod supports your installed Bannerlord version and DLC configuration.
Verification can replace missing or corrupted official files, but it may not remove leftover mods or repair user data in Documents and ProgramData. Steam’s general guidance also treats games that close immediately after “Preparing to Launch” as launch crashes and includes file verification among the standard remedies.
Reset Bannerlord’s configuration and cache
Reset the Configs folder
Rename—not immediately delete—the following folder:
C:Users<username>DocumentsMount and Blade II BannerlordConfigs
For example, rename it to Configs.old, then launch Bannerlord. The game should create fresh configuration files. This can remove corrupted graphics or launcher settings, but it also resets saved preferences.
Reset launcher data
If the launcher has missing buttons, incorrect module information, or closes immediately, rename:
C:Users<username>DocumentsMount and Blade II BannerlordConfigsLauncherData.xml
This is one of the workarounds listed in TaleWorlds’ technical checklist. The checklist was published and last edited years ago, so treat its exact paths and filenames as build-dependent rather than guaranteed current behavior.
Clear shader data
For crashes involving textures, icons, UI rendering, or shaders, rename or remove:
C:ProgramDataMount and Blade II BannerlordShaders
ProgramData is hidden by default. After clearing the folder, run Steam’s file verification again. Do not remove save data as part of this targeted reset.
Rank #2
- Explore, fight and conquer your way across the vast continent of Calradia, making friends and enemies along the way. Raise your own army and lead it into battle, commanding and fighting alongside your troops in the thick of the action.
- Play the game the way you want to play it! Plot your own path to power in a dynamic sandbox adventure where no two playthroughs are the same.
- Create and develop your own character to match your playstyle. Progress skills by performing actions as you gain access to a selection of perks that represent your mastery of a talent.
- See the availability of goods ebb and flow in a simulated feudal economy, where the price of everything from incense to warhorses fluctuates with supply and demand. Turn anarchy to your advantage by being the first to bring grain to a starving town after a siege or reopening a bandit-plagued caravan route.
- Put your tactical prowess and combat skills to the test against players from all over the world in a variety of different multiplayer game modes, ranging from small-scale skirmishes up to huge and epic sieges with hundreds of players.
Reset multiplayer data only when multiplayer is affected
For a multiplayer-specific launch failure, try renaming:
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →DocumentsMount and Blade II BannerlordDataNative
This is a targeted workaround, not a first-line reset for every campaign player.
Check Windows Security, antivirus, and OneDrive
Bannerlord needs to read and write files under Documents. Windows Security or third-party antivirus software can block the game, launcher, or crash reporter.
- Open Windows Security.
- Go to Virus & threat protection and inspect protection history.
- Open Ransomware protection and check Controlled folder access.
- If Bannerlord is blocked, add the executable through the allowed-app option.
- Check your antivirus quarantine and application-blocking logs.
Use an explicit allow rule rather than permanently disabling antivirus protection. TaleWorlds’ checklist specifically identifies Controlled Folder Access and security software as possible causes of blocked launch or crash reporting.
If Documents is managed by OneDrive, pause or exit OneDrive temporarily and test again. Confirm that the Bannerlord folder is accessible and not stuck in an online-only state. Do not simultaneously edit saves from multiple PCs, and remember that changing OneDrive settings can affect other Documents files.
Update the driver and select the correct GPU
Laptops and hybrid-GPU desktops can start Bannerlord on integrated Intel graphics instead of the dedicated NVIDIA or AMD adapter. In Windows, open Settings > System > Display > Graphics, add Bannerlord if necessary, choose Options, and select the high-performance GPU. You can also set the preference in the NVIDIA or AMD control panel.
Download drivers only from the manufacturer:
If the crash began immediately after a driver update, a clean driver installation or a previous stable driver may be worth testing. Disconnect external displays temporarily if the game appears to select the wrong adapter.
TaleWorlds’ older checklist mentions the graphics_adapter value in:
C:Users<username>DocumentsMount and Blade II BannerlordConfigsengine_config.txt
Back up the file before changing it. The checklist suggests trying 0, but that number does not universally mean “dedicated GPU” on every computer. Use Windows’ graphics preference or the GPU control panel first.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Rank #3
Increase virtual memory for GPU or large-battle crashes
For errors such as RGLGPU_DEVICE::LOCK_TEXTURE, graphics-memory pressure may be involved. Leave the Windows page file system-managed where possible:
- Open Windows search and enter Advanced system settings.
- Open View advanced system settings.
- Under Performance, choose Settings, then open Advanced.
- Under Virtual memory, choose Change.
- Enable Automatically manage paging file size for all drives, or ensure the page-file drive has adequate free space.
- Restart Windows.
Virtual memory is not a replacement for insufficient physical RAM or VRAM. Lower demanding graphics settings, close background applications, and check temperatures and driver stability. A whole-system freeze or reboot points beyond ordinary game-file corruption and may involve overheating, unstable RAM, overclocking, power delivery, or hardware failure.
Fix specific errors and launch stages
Missing DLL
Do not download individual DLL files from random websites. Install or repair the official Microsoft Visual C++ packages from Microsoft’s supported Visual C++ Redistributable page. Copy the missing filename exactly when searching documentation, and remember that the required architecture can matter on 64-bit Windows. One runtime package will not necessarily resolve every dependency error.
“Unable to initialize Steam API”
This commonly appears when launching Bannerlord.exe directly while Steam is closed. Start Steam first and launch through the client for normal Steam integration. The message does not by itself prove that Bannerlord’s files are damaged.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrash after the intro video or broken UI
Verify files, reset Configs, and clear the shader folder first. TaleWorlds’ checklist also names these UI files as targeted workarounds:
<SteamLibrary>steamappscommonMount & Blade II BannerlordGUIGauntletUIspriteData.xml<SteamLibrary>steamappscommonMount & Blade II BannerlordModulesNativeGUINativeSpriteData.xml<SteamLibrary>steamappscommonMount & Blade II BannerlordModulesSandBoxGUISandBoxSpriteData.xml
Only rename or remove a file after confirming its exact spelling and location in your installation, then verify the files. These older checklist entries are not guaranteed fixes for every current build.
Decompression failure naming a .tpac file
Delete or rename only the asset named in the error, then verify the installation:
Rank #4
- Erkunden und erobern Sie den riesigen Kontinent Calradia und machen Sie sich dabei neue Freunde und Feinde
- Spielen Sie das Spiel, wie Sie möchten: Die umfangreiche Singleplayer-Sandbox-Kampagne eröffnet ihnen alle Möglichkeiten!
- Stürmen Sie das Schlachtfeld mit hunderten Einheiten auf dem Bildschirm, jede davon mit ihrer eigenen, detaillierten KI
- Die Multiplayer-Modi bieten sowohl kleine Scharmützel als auch epische Belagerungen mit hunderten Spielern
C:Program Files (x86)SteamsteamappscommonMount & Blade II BannerlordModulesNativeAssetPackages
Your Steam library may use a different drive or folder. Do not randomly delete asset packages; the filename in the error is essential.
Multiplayer failure
If multiplayer shows no servers or Quickplay is unavailable, inspect:
<Bannerlord>binWin64_Shipping_ClientBattlEye
Run the included BattlEye repair or installation batch file. This is separate from single-player troubleshooting.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Test the game without the launcher
A direct launch can show whether the launcher is failing while the game executable remains usable. Open:
<SteamLibrary>steamappscommonMount & Blade II BannerlordbinWin64_Shipping_Client
Try Bannerlord.exe. You can also test these launcher executables:
TaleWorlds.MountAndBlade.Launcher.Singleplayer.exeTaleWorlds.MountAndBlade.Launcher.Multiplayer.exe
Direct launching may disable the Steam overlay and may produce the Steam API message described above.
For advanced diagnosis, open the folder, click the File Explorer address bar, type cmd, press Enter, and run:
Bannerlord.exe /singleplayer _MODULES_*Native*SandBoxCore*CustomBattle*Sandbox*StoryMode*_MODULES_ /anticheat
This is a diagnostic workaround, not the normal launch method. A missing DLL points toward dependencies; a generated crash report can indicate whether the launcher is failing to initialize correctly.
Also check whether an old “Fixed Launcher” modification left files behind. TaleWorlds’ checklist specifically warns that remnants of this modification can interfere with launching.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsPerform a true clean reinstall
Use this only after the reversible steps above. A normal uninstall may leave altered installation files and user data.
- Back up
Game Saves, record your Bannerlord version, DLC, and mod list, then uninstall from Steam or Epic. - Close Steam or the Epic client completely.
- Remove remaining installation files, confirming the path before deleting anything.
- Rename or remove the Bannerlord folder under Documents only after backing up saves.
- Rename or remove
C:ProgramDataMount and Blade II Bannerlord. - Reinstall the game.
- Launch it completely vanilla and test a new campaign.
- Restore saves first, then reintroduce mods gradually. Restore saves—not the entire old configuration tree—when testing.
Typical locations include:
<Steam>steamappscommonMount & Blade II Bannerlord<Epic>Mount & Blade II BannerlordC:Users<username>DocumentsMount and Blade II BannerlordC:ProgramDataMount and Blade II Bannerlord
A clean reinstall does not guarantee success if the underlying problem is a driver, Windows permission, unstable hardware, or an incompatible save.
When the problem is probably Windows or hardware
Focus beyond Bannerlord if other games also crash, Windows reports driver timeouts, the PC locks up, reboots, shows visual artifacts, or becomes unstable under load. Check GPU and CPU temperatures, remove overclocks, test RAM, inspect available disk space, and install stable chipset and graphics drivers. A game that merely closes is usually an application-level problem; a full system crash is not.
Contact support with useful evidence
If Bannerlord still fails in a clean vanilla test, contact the current PLAION Bannerlord Helpcenter and use its PC troubleshooting and support routes. Include:
Recommended Free Tools
- The exact error wording and crash identifier from the Bannerlord crash uploader.
- Whether the failure occurs vanilla or only with mods.
- Steam or Epic, Bannerlord version, and installed DLC.
- GPU model, driver version, CPU, RAM, and Windows version.
DxDiagandMsInforeports.- Recent changes such as a game update, driver update, mod installation, OneDrive migration, or hardware change.
- Whether a new campaign works while an existing save fails.
PLAION’s support pages provide current categories for driver updates, clearing Steam cache, uninstalling or updating the game, and submitting diagnostic logs.
Quick Recap
Final troubleshooting checklist
- Back up saves and record the exact error.
- Disable every mod and test a new vanilla campaign.
- Verify files through Steam or Epic.
- Rename
Configs; resetLauncherData.xmlif the launcher is affected. - Check Controlled Folder Access, antivirus quarantine, and OneDrive.
- Update or roll back the GPU driver and select the dedicated adapter.
- Clear shaders or the specifically named damaged
.tpacasset, then verify again. - Repair Microsoft Visual C++ dependencies.
- Try the direct executable to separate launcher and game failures.
- Repair BattlEye for multiplayer-only problems.
- Perform a clean reinstall only after backing up saves.
- Send the crash identifier, DxDiag, MsInfo, logs, and reproduction details to PLAION support.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.




