Fallout 4 Patch 110 163 May 2026

Have a story about how patch 1.10.163 broke your save? Share it in the comments below (in your imagination, since this is an article).

Published by: The Commonwealth Chronicle
Reading Time: 7 minutes fallout 4 patch 110 163

In the annals of Fallout 4’s post-launch support, few version numbers have sparked as much discussion, frustration, and eventual grudging acceptance as patch 1.10.163. Released in late 2019 and early 2020 (depending on your platform), this update arrived nearly four years after the game’s initial launch. It was not a content drop like Far Harbor or Nuka-World; instead, it was a foundational shift—one that primarily targeted the game’s modding ecosystem and the then-upcoming launch of the Creation Club’s “Fractured Steel” mini-quest. Have a story about how patch 1

For PC players, console modders, and those still wandering the glowing sea, understanding 1.10.163 is essential. This article breaks down exactly what changed, why it broke your mod list, and how to live with—or without—this controversial patch. Patch 1

Patch 1.10.163 is arguably more famous (or infamous) for its relationship with the Fallout 4 Script Extender (F4SE) . Because Bethesda changed the game’s executable signature and internal function addresses, F4SE had to be updated. Mods relying on F4SE (e.g., LooksMenu, Place Everywhere, Mod Configuration Menu) broke temporarily.

As a result, a large portion of the modding community froze their game version to 1.10.163 using Steam’s “Stay on this version” option (before Steam deprecated that feature for many games). Even today, many mod guides recommend downgrading to 1.10.163 for maximum compatibility, because: