Blizzard's latest listed Overwatch bug-fix update is deliberately small. It restores PC DualSense functionality, fixes a Sombra challenge, and clears old replay codes.

The latest listed fix is intentionally small

Blizzard's Overwatch patch-note page lists a bug-fix update dated October 20, 2026. It names two corrections: the Not so Thankless challenge can now be completed by thanking Sombra, and DualSense controllers should work properly on PC again. The page also says replay codes have been wiped. Those are the changes in this specific entry. The much larger October 6 season update and October 13 hero hotfix appear below it, but they should not be casually presented as new October 20 changes.

That distinction is useful for players searching for Overwatch update or Overwatch patch notes. A game can feel different after a large season launch, a balance hotfix, and a later bug-fix update, even though each release has a different scope. This article focuses on the latest listed maintenance entry and explains what players can actually check. We will also put the earlier season changes in context where necessary, without claiming that Blizzard silently added another hero, map, or balance pass on October 20.

DualSense input on PC should be restored

The most practically important fix for some PC players is the DualSense controller issue. Blizzard says it fixed a bug where DualSense controllers were not working properly on PC. The note does not specify whether the failure affected Steam, Battle.net, wired connections, wireless connections, certain menus, or every mode. It also does not list a new controller setting. Readers should treat the statement as a broad bug-fix description, not an exact troubleshooting guide for every possible DualSense problem.

If you were affected, update Overwatch through your normal launcher and restart it before testing. Check whether the controller responds in menus and then in a safe practice environment. Keep other input layers and remapping software in mind if behavior still differs from expectations, but avoid assuming they caused the original Blizzard bug. Comparing a direct connection and your usual setup can help isolate a local issue. If it remains broken, record the launcher, connection method, operating system, and whether other games recognize the controller before contacting support.

A Sombra thank-you can now count

The other named fix concerns the Not so Thankless challenge. Blizzard says players were prevented from completing it by thanking Sombra, and the bug has been corrected. That is an unusually specific patch note, but it illustrates how challenge tracking can depend on small interactions rather than combat balance. If you were stuck on this task, the update gives you a reason to try again. It does not imply that all challenge-tracking problems in the game have been resolved.

The safest check is to confirm you have the current build, read the challenge's own wording, and perform the intended interaction in a supported context. If progress still does not appear, note exactly what you did and where. Do not assume that simply opening a menu or using a voice line in an unrelated mode satisfies the condition; the patch note does not spell out every eligibility rule. The confirmed change is that thanking Sombra should no longer be blocked by the reported bug.

Why an old replay code may no longer open

Blizzard also states that replay codes were wiped with the October 20 bug-fix update. For anyone who saves codes to review a match, share a clip, or discuss a team fight, this is the detail most likely to cause surprise. An old code failing after the patch does not automatically mean your account lost recorded progress or that a friend gave you a fake code. The developer directly warned that the replay-code set was cleared. The note does not describe a recovery process for those codes.

For future reviews, export the footage or capture the key moment before a known patch whenever possible. A replay code is a convenient pointer into a live client, not the same thing as a permanent video file. If you want to coach a teammate or document a bug, a short clip with time and context will survive a code wipe more reliably. After October 20, start with fresh matches and fresh codes. Make sure the person opening one is using a compatible current version.

Do not confuse this with the October 13 hero hotfix

The same patch-note page lists an October 13 hotfix with hero adjustments, including Doctrine, Sombra, Roadhog, Kiriko, and D.Mon. That is separate from the October 20 entry. If you have noticed a different hero feel recently, checking the earlier date is sensible, but the two bug fixes on October 20 are not a new round of those balance numbers. Mixing release dates is a common way update articles accidentally mislead readers, especially when a page displays several patches in one long feed.

Blizzard's October 6 season notes are larger again, covering Reign of Talon Season 5, the Grim Doctrine theme, seasonal activities, and many systems. Those changes create the background in which the October 20 fix arrived. They are not evidence that every feature mentioned there was altered again two weeks later. When reading a live patch page, begin at the relevant date header and stop at the next date header. This simple habit keeps a small maintenance update from being mistaken for a full new season.

A sensible controller troubleshooting sequence

If DualSense still feels wrong on PC after the patch, work from the least disruptive checks upward. Verify the game completed its update, restart the launcher and client, then confirm the controller is recognized by Windows and works outside Overwatch. Try the connection method you normally use before swapping cables or input wrappers. If a remapping layer is enabled, record that fact for support. Changing several settings at once makes it hard to identify what helped and may introduce a separate problem.

The official note is not a claim that every DualSense configuration works identically. It identifies a fixed bug. A remaining issue may involve local configuration, a different game bug, or a specific setup not covered by the original report. Provide enough detail for a support ticket instead of declaring the patch a failure based on one unexplained symptom. For players whose controller now works, the practical conclusion is simple: keep the current client installed and enjoy the restored input.

Why a two-fix patch still deserves attention

A short maintenance patch can be more useful than a long balance list for the people it affects. A player locked out of their preferred controller cannot benefit much from a new map. Someone pursuing a challenge needs its progress to count. Replay users need to know when saved codes stop working. The October 20 entry addresses those everyday frictions directly. Its value is not measured by the number of new cosmetics or hero tweaks it contains.

At the same time, a narrow patch should receive a narrow headline. There is no official basis in this entry to say Overwatch has launched another character, changed the meta, or solved every PC input issue. The responsible reading is that Blizzard fixed two identified bugs and reset replay codes. If a later hotfix appears, that should get its own date and context. Search-friendly coverage is most useful when a reader can find the exact answer without sorting through inflated claims.

The quick take for returning players

Update the client, test DualSense on PC if it was failing, retry Not so Thankless if thanking Sombra did not count, and replace any replay workflow that depends on pre-patch codes. Those four actions map cleanly to Blizzard's October 20 note. If you play on console with no controller issue and do not use replay codes, you may barely notice this maintenance release. That is normal; not every patch is designed to change every match.

Keep the official patch page bookmarked because Overwatch's live notes can change again. When sharing advice, include the date so other players know whether you mean the October 6 season launch, the October 13 hero hotfix, or this October 20 repair. Clear dates and precise scope make patch coverage more useful than dramatic language. The October 20 entry is a good example: small, specific fixes that matter to the players who were blocked, plus one replay-code warning worth seeing before it surprises you.

SOURCES & FURTHER READING

CHECK THE ORIGINALS.

Facts and update details above are based on these official sources. Details can change as the game is updated.

TAGSOverwatchOctober 2026DualSenseSombraPatch Notes