The Fallout 4 Patch 1.10.163, released on December 4, 2019, was a minor update primarily focused on supporting new Creation Club content and fixing specific bugs within that ecosystem. While it didn't introduce major gameplay overhauls, it was a significant milestone for modders due to its impact on the Script Extender.
Below is a breakdown of what this patch entailed and how it affected the game. Key Changes and Fixes
According to the official Fallout 4 Patch History, the 1.10.163 update addressed the following:
Creation Club Support: Added compatibility for new content releases, including the Virtual Workshop and various skins.
Stability Improvements: Minor under-the-hood fixes to prevent crashes when loading specific Creation Club assets.
Bug Fixes: Resolved issues where certain items from previous updates were not appearing correctly in the player's inventory or workshop menu. The Impact on Modding (F4SE)
For many players, the most notable aspect of Patch 1.10.163 was that it broke the Fallout 4 Script Extender (F4SE).
Update Requirement: Every time the game’s executable (Fallout4.exe) is updated, F4SE must be updated to match the new version.
Mod Compatibility: This meant that high-level mods—like UI overhauls or complex gameplay systems—stopped working until the F4SE team released a compatible version.
Pro-Tip: Many veterans in the community recommend setting Steam to "Only update this game when I launch it" and only launching through the F4SE loader to avoid unexpected version mismatches. Community Perspectives
The reception of 1.10.163 was mixed. Discussions on Reddit's Fallout 4 community often centered on the frustration of "minor" updates breaking complex mod lists.
The Positive: It kept the game supported and provided new official content for players who prefer the plug-and-play nature of the Creation Club.
The Negative: The lack of significant "Vanilla" bug fixes (like the long-standing "long loading times" or "downtown Boston crashes") led some players to view these patches as mere storefront updates. Summary Table: Patch 1.10.163 at a Glance Release Date December 4, 2019 Primary Focus Creation Club Content Support Affected File Fallout4.exe (v1.10.163.0) Required F4SE v0.6.19 (or newer)
The rain in the Commonwealth didn’t wash the grime away; it just made the rust bleed.
Elias sat on the edge of the collapsed highway overpass, his legs dangling over the ruins of downtown Boston. The Pip-Boy light flickered—a habit he’d meant to fix for months—casting jittery green shadows across his lap. He wasn’t looking at the skyline, though. He was looking at the small, battered casing in his hand.
It was a holotape. Not a pre-war relic, not a diary of some long-dead survivor. It was a data packet he’d pulled from the wreckage of a crashed Vertibird near the Glowing Sea. The label, scrawled in sharp, military marker, read: Update v1.10.163.
To anyone else, it was garbage. To Elias, who had spent years listening to the static of the Brotherhood’s internal comms, it was a death sentence. fallout 4 patch 1.10 163
"Clean and simple," he muttered, his voice raspy from disuse. He thumbed the play button one last time.
“...rectifying logic error in settler aggression protocols. Atrium behavior corrected. Compensating for memory reallocation in the Institute's genetic sequencing...”
The voice was robotic, detached. But the implication was terrifying. This wasn't a tactical update. It was a reality patch. The Institute wasn't just making Synths anymore; they were rewriting the way the world worked. They were patching the "anomalies"—people who didn't fit their simulation. And Elias had just flagged himself as an anomaly by stealing the tape.
A static buzz erupted in his earpiece. The calm before the storm.
"Knight Sergeant Elias," a voice boomed. It was Elder Maxson, or a very good imitation of him. "Your telemetry is offline. Return to the Prydwen immediately for... recalibration."
Elias stood up, the servos in his T-51 power armor whining in protest. "Recalibration. Is that what you're calling executions now?"
"We are correcting errors, Sergeant. You are carrying corrupted data. It compromises the integrity of the unit. Do not force a manual override."
Elias looked north. Through the haze, he could see the Prydwen hovering like a bloated gray whale against the bruised purple sky. He could run. He could hide in the Glowing Sea where the radiation would fry his trackers. But he knew how the updates worked. The patches always came. They rolled out, silent and invisible, until the version of the world you knew was gone.
"Not today," Elias said. He switched his radio frequency to the open broadcast channel. "Sanctuary, this is Elias. I'm coming in hot. And I’m bringing the noise."
"Negative, Sergeant," the voice hissed, losing the Maxson cadence, becoming colder, more synthetic. "The patch is already initializing."
The world stuttered.
For a fraction of a second, the rain stopped mid-air. The distant rumble of thunder cut out. It was a frame skip—a lag in reality. Elias felt a headache spike behind his eyes, a sensation of his memories being shuffled like a deck of cards. He remembered dying in the war. He remembered waking up. He remembered a son, a wife, a bomb.
But for a second, he remembered being on an operating table, wires plugged into his brain, a voice whispering, “Test run 1.10.162 failed. Prepare for iteration 163.”
Then, the world snapped back. The rain fell harder.
"Stabilize," Elias grunted, forcing his brain to hold onto the present. He holstered the tape and unslung his laser rifle. The safety clicked off with a satisfying chunk.
Below him, the streetlights flickered. He saw movement in the shadows of the ruins. Not feral ghouls. Not raiders. They moved too smoothly. They walked with the same synchronized gait. Synths. A whole platoon of them, stepping out of the gloom, their faces blank, their eyes glowing with the soft blue hue of a fresh boot-up. The Fallout 4 Patch 1
They were the patch. They were here to delete him.
Elias took a breath of filtered air. He looked at the holotape again. Version 1.10.163. A fix for "unexpected behavior."
He aimed his rifle at the approaching tide of metal and flesh. If they wanted to debug the Commonwealth, they were going to have to fight for every line of code.
"Come and get me," he whispered.
He pulled the trigger, and the night turned to fire.
Title: The Final Archive: An Analysis of Fallout 4 Patch 1.10.163
In the sprawling, irradiated wasteland of the Commonwealth, change is usually a volatile force. Radstorms sweep the landscape, Super Mutants raid settlements, and the political tides shift between the Brotherhood of Steel and the Institute. Yet, for the dedicated inhabitants of the PC gaming community, the most significant—albeit invisible—shift occurred not with a nuclear blast, but with the quiet release of Fallout 4 Patch 1.10.163.
Released in early 2019, this patch was ostensibly minor. It did not introduce new quests, nor did it overhaul gameplay mechanics. On the surface, it was a housekeeping update, a final polish from Bethesda. However, Patch 1.10.163 represents a critical inflection point in the lifecycle of a "Game as a Service" title, serving as the definitive bridge between the vanilla experience and the complex world of script extenders and modern modding.
To understand the gravity of Patch 1.10.163, one must first understand the context of its release. By early 2019, Fallout 76 had launched to a turbulent reception, and support for the single-player Fallout 4 had largely winded down. The community had settled into a rhythm, relying heavily on the "Fallout 4 Script Extender" (F4SE). This tool allows modders to access code deeper than the standard Creation Engine allows, enabling complex mechanics like the "Place Everywhere" building mod or advanced camera systems. The Script Extender is version-dependent; it hooks into the specific binary code of the game’s executable.
When Bethesda deployed Patch 1.10.163, it broke the existing version of the Script Extender. In the modding community, a patch that breaks the Script Extender is akin to a power outage in a bustling city. Complex mods ceased to function, and players found their modded games crashing upon startup. This created a momentary panic: Was this an intentional breakage? Was Bethesda trying to phase out modding support to push players toward the Creation Club paid content?
The reality of the patch, however, was far more nuanced. The patch itself was focused on the "Creation Club"—Bethesda’s marketplace for official, curated mods. The update brought changes to the categories and the way the game handled these downloadable assets, likely preparing the backend infrastructure for future content drops or cross-compatibility with the then-struggling Fallout 76.
While the patch caused immediate headaches for modders who had to wait for the F4SE team to update their software, it ultimately solidified the "final" state of the game for several years. Because the patch modified the executable file (the .exe), it forced the modding community to converge on this specific version. Once the Script Extender was updated to accommodate 1.10.163, it became the new standard. Even today, years later, the "next-gen" update of 2024 notwithstanding, a vast portion of the modding ecosystem is still tethered to the specific binary architecture established by 1.10.163.
Furthermore, the patch highlighted a growing friction between the "pure" modding community and the corporate strategy of the Creation Club. By prioritizing updates that facilitated the Creation Club infrastructure—updates that offered little tangible benefit to the average player not using that service—Bethesda signaled where their maintenance priorities lay. For a player running a "vanilla plus" load order, the patch was an annoyance that required downloading a new F4SE binary. For the mod author, it was a reminder that their playground was ultimately owned by the game developer.
However, there is a silver lining to the longevity of Patch 1.10.163. Because the game remained relatively stable after this update for such a long period, it allowed the modding scene to mature significantly. Total conversion mods like Sim Settlements 2 reached their apex during the reign of the 1.10.163 executable. The stability provided by this specific patch version allowed creators to plan long-term projects without the fear of the game shifting underneath them every few months.
In retrospect, Fallout 4 Patch 1.10.163 is a fascinating case study in game preservation and community management. It was a patch that offered almost nothing to the standard player, disrupted the hardcore community, yet ultimately provided a stable platform that allowed the game to thrive for half a decade. It serves as a testament to the resilience of the modding community, who turned a breaking point into a foundation, ensuring that the Commonwealth remained vibrant long after the developers moved on to other projects.
patch 1.10.163 (released December 4, 2019) is widely considered the definitive "Old Gen" version of the game. While officially a minor update, it has become a central "feature" of the modding community as the most stable baseline for PC players. Key Features of Patch 1.10.163 If you’ve been wandering the glowing sea of
Virtual Workshop Creation: Added support for the large-scale Virtual Workshops Creation Club content, which includes four exotic VR landscapes (Grid World, Atomic Crater, Desert Island, and GNR Plaza) with infinite building resources.
Maximum Mod Compatibility: It is the final version before the "Next-Gen" updates (v1.10.984+), making it the required version for complex mods like Fallout: London and thousands of others that rely on the Fallout 4 Script Extender (F4SE).
Creation Club Content: This version stabilized support for the Creation Club marketplace, including ESL file format support and better load order management.
GOG Version Standard: The GOG.com version of Fallout 4 is locked to 1.10.163 by default, providing a DRM-free, stable experience without forced auto-updates. Why Players "Downgrade" to 1.10.163
Many PC players use tools like the Simple Fallout 4 Downgraders to revert their game from the Next-Gen version back to 1.10.163 to: Fallout 4 patches | Fallout Wiki
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
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.
Despite the initial pain, 1.10.163 became the target version for nearly every major mod author. Why? Because Bethesda stopped updating frequently. From 2019 to 2023, 1.10.163 was the de facto standard.
The only major mods that struggle with 1.10.163 are those relying on outdated DLLs compiled for earlier versions (like 1.9.4). If a mod hasn't been updated since 2018, downgrade your F4SE or find a replacement.
If you purchased Fallout 4 on Steam after April 2024, you are likely on the broken Next-Gen patch. Here is the safest method to revert to 1.10.163.
For players, patches like 1.10 are crucial as they can significantly improve the gaming experience by:
According to the official patch notes, 1.10.163 was surprisingly boring. It mainly addressed:
Sounds harmless, right? Wrong.