Fallout 4 Patch 1.10 163 May 2026

Title: Unpacking Fallout 4 Patch 1.10.163 – The “Creation Club Shakeup” That Changed the Modding Landscape

Posted by: TheCommonwealthArchivist

Date: April 12, 2026

Platforms: PC (Steam, GOG), Xbox One, PlayStation 4 fallout 4 patch 1.10 163

If you’ve been wandering the glowing sea of Fallout 4 modding for as long as I have, you know that Bethesda has a certain… signature approach to updating a game that’s technically over a decade old. We all thought the major patches were done after the next-gen update in 2024. Then, quietly, almost stealthily, Patch 1.10.163 dropped. And it’s caused more ripples than a Deathclaw doing a cannonball into Lake Quannapowitt.

Let’s break down exactly what this 3.2GB patch (on PC; smaller on consoles) actually does, why half the modding community is cheering and the other half is screaming into the void, and what it means for your next survival mode run.

The Modding Catastrophe

However, the headline consequence of 1.10.163 was not its features—it was what it broke. The patch silently updated the game’s master files (.esm) and executable, rendering the vast majority of PC mods dependent on Fallout 4 Script Extender (F4SE) completely inoperable. F4SE, the community’s lifeline for complex mods like Sim Settlements 2, M’s Abominations, and Custom Camera, required a separate update from its volunteer developers—a process that took weeks. Title: Unpacking Fallout 4 Patch 1

In the interim, thousands of modded playthroughs were bricked. Steam users who had not disabled automatic updates found their load orders shattered, with warnings of “missing masters” and immediate crashes to desktop. The patch also silently re-enabled the game’s built-in mod manager, overriding third-party tools like Vortex and Mod Organizer 2 for unsuspecting users, causing duplicate load orders and ghosted mods.

Worse, the patch introduced its own unique bugs: for some Series X users, the “60 FPS mode” would toggle off randomly, reverting to a stuttering 30 FPS. On PS5, previously stable settlement build limits began triggering premature memory errors. PC users reported that the new widescreen support, while functional, broke HUD and UI mods that had previously fixed the interface themselves.

The Verdict: Should you stay on 1.10.163?

The Silent Downgrade Backlash

Within 48 hours, the modding community mobilized. The “Fallout 4 Downgrader” tool—a script that reverts the game to pre-patch 1.10.163 executable while retaining the new Creation Club content—became essential reading on Reddit and Nexus Mods. Bethesda’s official Discord was flooded with requests for an opt-out branch on Steam (which never materialized). If you’ve been wandering the glowing sea of

By mid-May, Bethesda released a hotfix (1.10.164) addressing the most egregious console crashes and re-adding the “weapon debris” toggle. However, the underlying issues for F4SE mods persisted for nearly a month, as the Script Extender team had to reverse-engineer the new executable’s memory addressing. For many mod authors, this was the final straw; several popular mods announced they would not update for the new patch, citing burnout and Bethesda’s lack of communication.

Fallout 4 Patch 1.10.163: The Update That Broke (And Then Fixed) Your Mod List

If you’re a seasoned Sole Survivor, you’ve probably felt a chill run down your spine when you see a pop-up saying Fallout 4 has updated. For years, the game has been in a stable, "finished" state. That is, until Bethesda dropped Patch 1.10.163.

At first glance, it looks like a standard maintenance update. But for the modding community, this specific patch (released in late 2023/early 2024 depending on your platform) was a seismic event. Let’s break down what it actually did, why it caused chaos, and how to fix it.

Unlisted Technical Fixes

Most importantly, Patch 1.10.163 did not touch the core lighting shaders (unlike the disastrous 1.10.75 patch), meaning ENB presets and Reshades remained fully functional.