Fallout 4 Patch 1.10 163 -

For many players, Fallout 4 patch 1.10.163 is the gold standard for stability and modding. Released in December 2019, this version was the final major update before the controversial 2024 "Next-Gen" patches. While newer versions exist, 1.10.163 remains a critical anchor for the community, especially for those running heavy mod lists or playing the massive Fallout: London total conversion. Key Features and Content in 1.10.163

Though primarily known for adding Creation Club content, patch 1.10.163 included several specific additions that expanded the base game:

Virtual Workshops: This was the headline addition, allowing players to travel to new VR worlds like Grid World, Atomic Crater, and the Capital Wasteland’s GNR Plaza from any settlement.

Settlement Resources: The VR workshops provided limitless resources and huge building limits, alongside 40 new workshop items.

Bug Fixes: The update addressed general stability, specifically regarding the enabling and disabling of mods through the in-game menu. Why Modders Prefer Version 1.10.163

Following the release of the "Next-Gen" update (version 1.10.984 and higher), many players chose to downgrade their game back to 1.10.163. There are three primary reasons:

F4SE Stability: The Fallout 4 Script Extender (F4SE) is the backbone of advanced modding. Every time Bethesda updates the game's executable (.exe), F4SE breaks. Because 1.10.163 was static for years, it has the most robust mod support. fallout 4 patch 1.10 163

Legacy Mod Compatibility: Many classic mods were never updated for the 2024 architecture. Running 1.10.163 ensures that older, "essential" mods—like LooksMenu or certain physics fixes—continue to function without crashing.

The "Next-Gen" Issues: The newer 2024 updates introduced new bugs, including broken ultra-wide support and issues with the Blitz perk and Two-Shot weapons. How to Verify or Revert to 1.10.163

If you are unsure which version you are running, launch the game and check the bottom right corner of the Settings menu.

Method 1: The Steam Console (Best for clean installs)

  1. Open Steam and go to your Library.
  2. Right-click Fallout 4 > Properties > Betas. Select "none" (unless you own the old beta branch).
  3. Close Steam completely.
  4. Open Windows Run (Win + R) and type: steam://nav/console
  5. In the Steam Console, type: download_depot 377160 377161 6543815410771607743 Wait for the download to finish. This is the exact 1.10.163 Fallout4.exe.
  6. Replace your current .exe with this one.

1. The Context: Why 1.10.163 Exists

To understand Patch 1.10.163, you must rewind to 2017. Bethesda launched the "Creation Club"—a storefront for paid mini-mods (Creations). This required frequent updates to the game’s executable (Fallout4.exe) to implement new store hooks, security protocols, and ESL file support (light plugins).

By 2019, the community was tired of weekly 100MB updates that changed nothing visible but broke the Fallout 4 Script Extender (F4SE) every time. Patch 1.10.163 was Bethesda’s attempt to consolidate. It was a "stable branch" update designed to:

  • Finalize the Creation Club’s backend architecture.
  • Permanently address the audio loop crash in the Corvega Assembly Plant.
  • Optimize how the engine handles ultra-high-resolution textures on GPUs with more than 4GB of VRAM.

For two years, 1.10.163 was the definitive version of Fallout 4. For many players, Fallout 4 patch 1

2. The Script Lag “Fix”

Remember how downtown Boston would turn into a slideshow the moment three different scripted mods tried to fire at once? Patch 1.10.163 introduces a thread-prioritization system for Papyrus scripts. In plain English: high-priority scripts (combat, quest stages) now get CPU time before low-priority scripts (settler idle animations, wandering NPC schedules).

Early benchmarks show a 15-20% improvement in frame pacing in heavy combat zones like Faneuil Hall or Quincy Ruins. It’s not a miracle—you’ll still drop frames—but the stutter is noticeably less violent.

Fallout 4 Patch 1.10.163: The Final Major Update and Its Lasting Impact on the Commonwealth

Published by: The Commonwealth Technical Institute
Date: Post-War Analysis, 2024

In the sprawling, post-apocalyptic world of Fallout 4, few numbers carry as much weight among the dedicated modding community and survival-mode purists as 1.10.163. For the uninitiated, this seemingly random string of digits—Fallout 4 patch 1.10.163—represents a turning point. It is the last significant, widely-adopted update Bethesda Game Studios released for their 2015 magnum opus before shifting focus to Fallout 76 and, eventually, Starfield.

Released in late 2019 (following a rapid succession of minor updates throughout 2019), Patch 1.10.163 did not introduce new quests or legendary weapons. Instead, it refined the engine, broke thousands of mods, and ultimately stabilized the platform for what has become a never-ending renaissance of community-driven content. This article dissects every aspect of Patch 1.10.163: what it fixed, what it broke, and why you still need to know about it in 2024.

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. Method 1: The Steam Console (Best for clean installs)

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.

Should You Update?

If you’re on PC and use F4SE (Fallout 4 Script Extender): Do not auto-update. Wait for the F4SE team to release a new build (usually 3-7 days). Set Steam to “Only update when I launch” and launch through your mod manager.

If you’re on console (Xbox/PS4/PS5): You have no choice. The update is mandatory. But here’s the silver lining: the stability improvements actually help on the Series X. My test save with 150 mods on Xbox Series X now holds 60fps in downtown Boston for about 90% of the time. That’s unheard of.

If you’re a vanilla purist: Update without fear. The patch fixes two quest bugs and doesn’t affect the base experience.

For many players, Fallout 4 patch 1.10.163 is the gold standard for stability and modding. Released in December 2019, this version was the final major update before the controversial 2024 "Next-Gen" patches. While newer versions exist, 1.10.163 remains a critical anchor for the community, especially for those running heavy mod lists or playing the massive Fallout: London total conversion. Key Features and Content in 1.10.163

Though primarily known for adding Creation Club content, patch 1.10.163 included several specific additions that expanded the base game:

Virtual Workshops: This was the headline addition, allowing players to travel to new VR worlds like Grid World, Atomic Crater, and the Capital Wasteland’s GNR Plaza from any settlement.

Settlement Resources: The VR workshops provided limitless resources and huge building limits, alongside 40 new workshop items.

Bug Fixes: The update addressed general stability, specifically regarding the enabling and disabling of mods through the in-game menu. Why Modders Prefer Version 1.10.163

Following the release of the "Next-Gen" update (version 1.10.984 and higher), many players chose to downgrade their game back to 1.10.163. There are three primary reasons:

F4SE Stability: The Fallout 4 Script Extender (F4SE) is the backbone of advanced modding. Every time Bethesda updates the game's executable (.exe), F4SE breaks. Because 1.10.163 was static for years, it has the most robust mod support.

Legacy Mod Compatibility: Many classic mods were never updated for the 2024 architecture. Running 1.10.163 ensures that older, "essential" mods—like LooksMenu or certain physics fixes—continue to function without crashing.

The "Next-Gen" Issues: The newer 2024 updates introduced new bugs, including broken ultra-wide support and issues with the Blitz perk and Two-Shot weapons. How to Verify or Revert to 1.10.163

If you are unsure which version you are running, launch the game and check the bottom right corner of the Settings menu.

Method 1: The Steam Console (Best for clean installs)

  1. Open Steam and go to your Library.
  2. Right-click Fallout 4 > Properties > Betas. Select "none" (unless you own the old beta branch).
  3. Close Steam completely.
  4. Open Windows Run (Win + R) and type: steam://nav/console
  5. In the Steam Console, type: download_depot 377160 377161 6543815410771607743 Wait for the download to finish. This is the exact 1.10.163 Fallout4.exe.
  6. Replace your current .exe with this one.

1. The Context: Why 1.10.163 Exists

To understand Patch 1.10.163, you must rewind to 2017. Bethesda launched the "Creation Club"—a storefront for paid mini-mods (Creations). This required frequent updates to the game’s executable (Fallout4.exe) to implement new store hooks, security protocols, and ESL file support (light plugins).

By 2019, the community was tired of weekly 100MB updates that changed nothing visible but broke the Fallout 4 Script Extender (F4SE) every time. Patch 1.10.163 was Bethesda’s attempt to consolidate. It was a "stable branch" update designed to:

For two years, 1.10.163 was the definitive version of Fallout 4.

2. The Script Lag “Fix”

Remember how downtown Boston would turn into a slideshow the moment three different scripted mods tried to fire at once? Patch 1.10.163 introduces a thread-prioritization system for Papyrus scripts. In plain English: high-priority scripts (combat, quest stages) now get CPU time before low-priority scripts (settler idle animations, wandering NPC schedules).

Early benchmarks show a 15-20% improvement in frame pacing in heavy combat zones like Faneuil Hall or Quincy Ruins. It’s not a miracle—you’ll still drop frames—but the stutter is noticeably less violent.

Fallout 4 Patch 1.10.163: The Final Major Update and Its Lasting Impact on the Commonwealth

Published by: The Commonwealth Technical Institute
Date: Post-War Analysis, 2024

In the sprawling, post-apocalyptic world of Fallout 4, few numbers carry as much weight among the dedicated modding community and survival-mode purists as 1.10.163. For the uninitiated, this seemingly random string of digits—Fallout 4 patch 1.10.163—represents a turning point. It is the last significant, widely-adopted update Bethesda Game Studios released for their 2015 magnum opus before shifting focus to Fallout 76 and, eventually, Starfield.

Released in late 2019 (following a rapid succession of minor updates throughout 2019), Patch 1.10.163 did not introduce new quests or legendary weapons. Instead, it refined the engine, broke thousands of mods, and ultimately stabilized the platform for what has become a never-ending renaissance of community-driven content. This article dissects every aspect of Patch 1.10.163: what it fixed, what it broke, and why you still need to know about it in 2024.

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.

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.

Should You Update?

If you’re on PC and use F4SE (Fallout 4 Script Extender): Do not auto-update. Wait for the F4SE team to release a new build (usually 3-7 days). Set Steam to “Only update when I launch” and launch through your mod manager.

If you’re on console (Xbox/PS4/PS5): You have no choice. The update is mandatory. But here’s the silver lining: the stability improvements actually help on the Series X. My test save with 150 mods on Xbox Series X now holds 60fps in downtown Boston for about 90% of the time. That’s unheard of.

If you’re a vanilla purist: Update without fear. The patch fixes two quest bugs and doesn’t affect the base experience.