The Elder Scrolls IV: Oblivion Remastered / GAME HISTORY

Oblivion Remastered Paralysis Crash: Bethesda Points to Update 1.2

Bethesda Support says Update 1.2 resolved several crashes involving paralyzing effects in Oblivion Remastered. Update the game before relying on launch-era combat workarounds; the statement does not promise that every crash is eliminated.

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

Scope: Oblivion Remastered and Bethesda Support article 70157. The original 2006 game is outside this report’s scope.

The official answer comes before the workaround

Bethesda’s support page now directs players with paralyzing-effect crashes to Update 1.2. That is stronger evidence of a later resolution than an old thread saying the problem is still happening. It does not identify every affected combat interaction or guarantee that an unrelated crash has the same cause.

What players were reporting

In a May 2025 Steam account, Beardo described a crash involving a Daedroth and the Marksman 75 paralysis effect. The poster was uncertain whether the initial or a repeated hit triggered it. UESP separately records repeated paralysis as a crash condition. Keep that uncertainty rather than converting the report into a proven exact-hit rule.

1. A Marksman attack applies paralysis to an enemy.
2. The player continues the encounter, potentially hitting the paralyzed target again.
3. The game closes in the reported case, interrupting progress since the last save.

What to check now

Confirm that the installed game includes Update 1.2 or a later release before retrying the encounter. Retain an earlier save. If a crash still occurs, report the platform, installed build, enemy and action sequence. That gives support something more specific than a general statement that the remaster crashes.

The limits of the fix

The support wording concerns several paralyzing-effect crashes. It is not a statement that every combat crash, mod conflict or save problem has been solved. Alchemy and physics incidents also appear in older discussion, but the checked sources do not establish a shared code cause. Avoid adding an unsupported technical explanation or requiring players to abandon a Marksman build on an already updated game.