The Legend of Zelda: Twilight Princess / GAME HISTORY

Twilight Princess Cannon Room Save Bug: Why Shad Can Be Missing

A historical Wii report describes loading a cannon-room save with Shad absent, while the exit scene and Midna still behave as though he is present. Copying that affected save to another slot did not resolve the reported lock.

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

Scope: Historical Wii cannon-room reports. No final official fix version or disc-revision guarantee was verified in the checked record.

The saved state came before the warp

Lord Yoshi’s Zelda Universe post describes a friend reaching Lake Hylia after moving the cannon, then switching off without saving there. The last save was from before the warp. Reloading returned the player to the cannon room, where the normal conversation with Shad was unavailable. Saving after the warp is not the sequence described in that account.

The reported sequence

The post separates a successful action during one session from the earlier state restored on the next load.

1. The player saves before the cannon is warped.
2. The player asks Shad to leave and moves the cannon to Lake Hylia.
3. The session ends without another save after that progress.
4. Loading restores the cannon room, but Shad is absent during ordinary movement.

Trying the exit shows Shad in a short scene; afterward he is absent again. Midna refuses the warp because of his supposed presence, and the player cannot obtain the conversation prompt needed to ask him to leave.

Why copying the slot did not help

The poster tried copying the same game data into a blank slot. The copied file reproduced the problem. That observation supports keeping a separate, earlier checkpoint; it does not support treating a duplicate of the affected state as a repaired file.

Avoidance and the historical limit

For an original Wii playthrough, retain a save from before this sequence and avoid making the room your only stopping point. The checked forum contains claims about replacement discs and revisions, but no official documentation confirming those claims was verified here. A report that one file was trapped is also not proof that every later release has the same defect or that every possible recovery route is impossible.