Destiny 2 Hotfix 4.1.0.4 arrived on June 28, 2022, after Bungie scheduled a maintenance window to address a focused set of bugs and known issues. For readers reviewing Destiny 2's patch history in 2026, the update remains a compact case study in how Bungie handles server downtime, sandbox corrections, photosensitivity concerns, and transparency around unresolved problems. It was not a seasonal expansion or a sweeping sandbox overhaul. It was a targeted hotfix, and its scope shows how live-service maintenance often works: a short outage, a clear timeline, a list of fixes, and a separate list of issues that still needed attention.
Maintenance Window and Server Timeline
Bungie brought the servers down for roughly an hour and published a schedule so players could plan around the outage. The downtime applied to both Destiny 1 and Destiny 2, even though the patch itself targeted Destiny 2. The key phases were as follows:
| Phase | Pacific Time | British Summer Time | UTC | What Happened |
|---|---|---|---|---|
| Sign-on limits begin | 8 AM PDT | 4 PM BST | — | Sign-on and game integration features became unavailable on web, mobile, third-party apps, and the Bungie Store |
| Maintenance begins | 9 AM PDT | 5 PM BST | 1600 UTC | Destiny 1 and Destiny 2 maintenance started |
| Games go offline | 9:15 AM PDT | 5:15 PM BST | 1615 UTC | Destiny 1 and Destiny 2 were brought offline |
| Hotfix rollout | 10 AM PDT | 6 PM BST | 1700 UTC | Hotfix 4.1.0.4 began rolling out across all platforms and regions |
| Maintenance completes | 2 PM PDT | 10 PM BST | 2100 UTC | Destiny 1 and Destiny 2 maintenance finished |
During the sign-on restriction period, players could not access several connected features. After the games went offline, no one could sign in until maintenance completed. Bungie also directed players to monitor the official server status page if the game did not load properly after the downtime. That guidance remains relevant in 2026, even though the 2022 schedule itself is historical and should not be treated as an active maintenance window.
What Hotfix 4.1.0.4 Fixed
The patch notes focused on a handful of gameplay, visual, and raid-related problems. The most notable fixes included:
-
🛡️ Correcting an issue where players could shoot through Barricades, Ward of Dawn, and thin walls when the Piercing Sidearms artifact mod and Armor-Piercing Rounds weapon mods were equipped.
-
⚠️ Fixing an issue where the Crucible Vermilion shader effects caused unintended photosensitivity issues.
-
🔎 Investigating special effects in Nightmare Containment activities that caused unintended photosensitivity concerns.
-
🪽 Fixing an issue where Wings of Sacred Dawn did not offer the proposed airborne effectiveness buff.
-
🦵 Fixing an issue where Peregrine Greaves did not offer the proposed airborne effectiveness buff.
-
🥾 Fixing an issue where Peacekeepers did not offer the proposed airborne effectiveness buff.
-
🏛️ Fixing an issue where the Master Vault of Glass raid did not have all Challenges active when available through the new raid and dungeon rotator.
The photosensitivity fixes are especially important because they show that Destiny 2 patches are not only about damage numbers or loot drops. Visual effects can affect player health and comfort, and Bungie treated those reports as maintenance-worthy problems. The airborne effectiveness fixes also reflect a period when Bungie was actively tuning how exotic armor pieces supported aerial combat. In 2026, those changes read as part of a broader effort to align exotic armor behavior with intended sandbox design.
Known Issues After the Hotfix
Bungie also listed several known issues that were not fully resolved by Hotfix 4.1.0.4. These items mattered because they told players what to expect after the patch, rather than leaving them to discover problems without context.
-
❌ The pattern for crafting Nezarec's Whisper could not be untracked.
-
❌ Defeating targets while Radiant with Knock 'em Down did not refund melee energy when used with Caliban's Hand.
-
❌ Calus Mini-Tool and Drang (Baroque) did not update to gold Masterwork borders after upgrading to two Enhanced traits.
-
❌ The Empty Grief Seasonal Challenge would not be completed if a player picked up the scythe that spawned in the final encounter, or if the player used weapon traits that caused explosions, such as Dragonfly. Players were advised to complete the encounter with their equipped weapons to complete the Challenge.
The Empty Grief note is a useful example of how specific live-service issues can be. A challenge might fail not because of a broad server fault, but because a particular interaction, such as picking up an encounter object or triggering an explosion perk, does not register correctly. Bungie's workaround was simple: avoid the problematic interaction and complete the encounter with equipped weapons.
Why the Patch Still Matters in 2026
By 2026, Destiny 2 has moved through many seasons, sandbox revisions, and maintenance cycles, so Hotfix 4.1.0.4 is not a current patch note. It is a historical reference point. Still, it illustrates several enduring features of Destiny 2's live-service model: short maintenance windows, platform-wide hotfix rollouts, separate fixed and known-issue lists, and attention to accessibility concerns such as photosensitivity. For players and researchers looking back at how Bungie communicated updates in the Witch Queen era, the June 28 hotfix is a clear snapshot. Anyone checking Destiny 2's status in 2026 should consult current Bungie announcements and live server status information rather than relying on this 2022 timeline.