Home / Star Wars: Knights of the Old Republic / Game history

Star Wars: Knights of the Old Republic / GAME HISTORY

KOTOR Leviathan Freeze: Dialogue Lock or Post-Malak Exit Crash?

Aspyr documents a specific crash after the Malak fight when leaving while controlling a companion: reload a save aboard the Leviathan and control the main character.

By Patchlo Editorial Desk · Published October 29, 2026 · Sources checked October 29, 2026

Short answer

Aspyr documents a specific crash after the Malak fight when leaving while controlling a companion: reload a save aboard the Leviathan and control the main character. That advice does not establish a fix for a conversation that has already stopped.

Scope: Aspyr’s documented exit-crash scenario, alongside separate Steam and Xbox One backward-compatibility player reports.

A party in a city in Knights of the Old Republic
Official store gameplay screenshot; not a reproduction of the Leviathan failure. Image source ↗

Where Aspyr’s workaround applies

The support article concerns leaving after the fight with Malak while a companion is selected. Its instruction is to reload aboard the Leviathan and take control of the main character. The location and selected character matter; “the Leviathan froze” is not enough to identify that case.

  1. Keep a separate copy of the current save.
  2. If the failure matches Aspyr’s post-fight exit crash, load a save aboard the ship.
  3. Select the main character before attempting the exit.

A stalled conversation needs a separate diagnosis

The player question behind this article describes Malak reaching an empty dialogue state. Reloading and a new playthrough reportedly did not solve it. The platform was not given, so assigning that case the cause from Aspyr’s exit-crash article would go beyond the evidence.

An Xbox One backward-compatibility report describes a hang after the turret section involving Jolee and Carth. The poster later succeeded after loading from before Manaan and changing the rescue character. Several things changed together; the account does not prove that choosing Mission alone causes the failure.

What older saves can and cannot establish

In a separate Steam discussion, an older save helped one player and failed another. Loading farther back can discard completed dialogue, travel and combat without guaranteeing a different outcome. Keep the earlier file rather than repeatedly overwriting it. The checked sources do not supply a final fix version for every dialogue lock, and console warping is not presented here as a routine repair.

Join the conversation

Have a question, correction or a different take? Share it below. Comments appear immediately after submission.

3–2,000 characters. Your name and comment will be public. Please avoid personal contact details, advertising and abuse. Comment policy & privacy

Reader comments

Loading comments…