Onimusha: Way of the Sword Patch Notes & Update Tracker
Updated October 12, 2026 · Facts cross-checked against the sources listed below
Thirty-nine days after launch, still no patch — the live build remains version 01.000.001 (the preload revision), the build Steam serves has not changed since September 2, and no patch notes exist on any platform. Nor has anyone from Capcom replied in the forums, and we can now put a clean number on it.Across all 14,671 comments we have read on the board — 1,353 topics, re-checked October 12 — the developer badge appears exactly zero times. It does appear on the two pinned opening posts, which is what Capcom’s own account posting a thread looks like — an earlier version of this page counted those in and said “fourteen”, which overstated how close the company has come to replying. Scoped properly to replies, the figure is zero. The troubleshooting thread is at 173 replies. Capcom’s only official Steam post since launch is the September 8 “1 million copies sold” celebration, and the same week the game went to #1 on Japan’s sales chart. This page is the permanent tracker: every patch, its version numbers per platform, and what it actually fixed — sourced from official notes only, never from secondhand headlines.
Update history
| Date | Version | What it did |
|---|---|---|
| Sep 2, 2026 | 01.000.001 (PS5 preload) | Launch build delivered via preload — one revision above the disc master; contents undocumented ⚠ version from PS Store listing |
| Sep 4, 2026 (console launch night) | Still 01.000.001 | No version bump observed through the first console night; no patch notes. Capcom’s launch-day post is a preventive PC troubleshooting checklist (driver minimums: NVIDIA 596.49+ / AMD 26.5.1+) with no known-issues list |
| Sep 5-7, 2026 (launch weekend + Monday) | Still 01.000.001 | No patch through the launch weekend or the first Japanese business day despite the crash wave — Steam’s recovery to Very Positive (87.6%) came from community workarounds, not a fix. The frame-generation crash remains live; the official troubleshooting thread has grown to 76 replies with zero staff responses, while the game set Capcom-2026 Steam records on consecutive days (81,559, then 85,081 concurrent players) |
| Sep 8, 2026 (day five) | Still 01.000.001 | Day five, no patch and no technical acknowledgment — but the first official Steam post since launch: a “1 million copies sold” celebration, whose press release thanks players for “all player feedback.” The troubleshooting thread stands at 93 replies, still zero staff; the Japanese pinned thread (3 replies) shows the same silence, retiring the “wait for the Japanese work week” theory. A second crash cluster — repeatable mid-game area crashes with no community fix — is documented on the performance page |
| Sep 19–20, 2026 (days sixteen and seventeen) | Still 01.000.001 | Eighteen days on one build; we did not read the board on September 19, so this row covers two days. The board added 24 topics and roughly 290 comments (1,195 topics, 12,641 comments in all), the troubleshooting thread reached 152, and the developer badge is still on none of it. Steam crossed 90% positive for the first time (90.1%), with the Chinese–English gap at its narrowest, 8.1 points. The loudest new thread is the final boss — 46 replies in two days: no checkpoint between phases, a second phase several players find hard to read, two admitting to a trainer — folded into the boss page. Two new single-account blockers arrived with self-reported fixes: a black screen at the Arashiyama malice-tower cutscene, cleared by adding -dx12 to the Steam launch options, and a launch failure cleared by deleting hid.dll from the Steam folder; plus a block button that also opens the weapon wheel (two accounts, no fix). A one-line “soft locked at Okuni’s Kabuki Dance” (#152) gave no trigger and is not counted. In Steam’s app records a new DLC entry, Materials Pack: Red Souls III, appeared between the two reads with no public store page ⚠ app-record entry only; no announcement |
| Sep 18, 2026 (day fifteen) | Still 01.000.001 | Sixteen days on one build. The board added 11 topics and 181 comments overnight (1,174 topics, 12,352 comments in all) and the developer badge is still on none of them — but the Japanese official thread moved for the first time since launch, from four replies to six, both from players: a long report of parries and Issen misregistering after the Mount Oe awakening event, and a one-line “have you acknowledged the crash logs yet”. No new lockout: the softlock sweep of the new posts came back empty, and the three threads under watch (the early-purchase items, The Light of Vengeance, the three-restarts account) drew no reply. Two launch failures did arrive, one of them — a Family-Sharing copy — cleared by installing REFramework, and the final-boss threads settled a small fact for the boss page: three phases, no checkpoint between them, on Story difficulty too |
| Sep 17, 2026 (day fourteen) | Still 01.000.001 | Fifteen days on one build. The board added 13 topics and 335 comments overnight (1,166 topics, 12,213 comments in all) and the developer badge is still on none of them. No new lockout of any kind: the softlock sweep of the new posts came back empty, and neither the Light of Vengeance thread nor the September 15 “three stalls, three restarts” account drew a reply. What moved was outside the game. Both interactive map sets are now complete — MapGenie took the “Under Construction” tags off Arashiyama and Shanaoh Castle, IGN added Shanaoh Castle — and the collectible count picked up a dissenting source: the Japanese Gamerch wiki lists 54 Oni Stones against PowerPyx’s revised 55, so the collectibles page now shows 274–275 rather than choosing. Two smaller player-sourced answers went up: how the early-purchase items are actually claimed (a story point, then Additional Content), and why Issen: Range keeps failing (distance, obstacles, latency) |
| Sep 16, 2026 (day thirteen) | Still 01.000.001 | Fourteen days on one build. The board added 24 topics and 204 comments overnight and the developer badge is still on none of them. No new lockout could be confirmed, but The Light of Vengeance drew a fourth “same problem” report with no details, and — the more useful find — one player described three quest stalls in a single run that all cleared on a restart, which is why the softlock advice now says plainly that restarting without a manual save is a gamble that has gone both ways. A side quest, Some Unfinished Monkey Business, gained its first hard-crash report, and a third player says his saves stopped loading after a crash during the credits. On the sales side, SteamDB’s full-week chart for September 8–15 has Onimusha at #7 (The Blood of Dawnwalker #4) |
| Sep 15, 2026 (day twelve) | Still 01.000.001 | Thirteen days on one build. For the first time we read every thread on the board in full — 11,690 comments — and the developer badge is on none of them. That full read corrected two things we published on September 14. The frame-rate cap is not converging: at least 13 players say it helped and at least 9 capped and still crashed. And Shadows Fall is no longer the most-affected quest: the softlock pattern now stands at nine cases, with The Light of Vengeance on three. One of the new cases also showed that fast-travelling away and back can trigger a lockout on its own, which meant our advice to “leave the area and come back first” was wrong — it has been corrected |
| Sep 14, 2026 (day eleven) | Still 01.000.001 | Twelve days, no patch, and still not one Capcom reply — now measured as 0 developer badges across 361 comments. Two more softlock cases surfaced, taking the pattern to six, and one of them is a second Shadows Fall rift — making that quest the most-implicated in the game at the time (corrected September 15: The Light of Vengeance has since overtaken it). The first genuine workaround in the blocker family also appeared, though it fixes the Mount Oe gauntlet rather than the rift lockouts. On the crash side we reported four players converging on capping the frame rate below what the GPU can hold (corrected September 15: across the whole board the cap fails for a sizeable minority and is not a reliable fix) |
| Sep 13, 2026 (day ten) | Still 01.000.001 | Ten days, no patch, and not one Capcom reply anywhere — now measured rather than assumed (see above). The bigger finding was a gap in our own work: the board runs to 630 topics across 42 pages and our previous sweeps had only reached page eight, so three further softlocks posted between September 5 and 8 had been sitting unread. Set beside the Shadows Fall case they share one mechanism, and it is not crashing — see the softlock pattern. A second, separate Mount Oe blocker was posted on September 12, and the Intel stutter fix gained a named tool plus an explicit AMD negative |
| Sep 12, 2026 (day nine) | Still 01.000.001 | Nine days on one build. We pulled Capcom’s pinned troubleshooting post in full to check whether it had been quietly revised. A correction, made September 13: we said it carried no edit marker. It does — the post was edited once, twenty-five minutes after going up on September 3, and never again. Our check missed it because the marker sits in the post footer rather than the comment body. The conclusion is unchanged, and arguably firmer: frozen for ten days, and still containing no known-issues list — it is the same generic eleven-step checklist it launched with. The developer badge still appears nowhere except the two pinned opening posts. A third softlock was reported, at the Shadows Fall rift, and the Intel stutter finding gained a cross-generation test and a negative control |
| Sep 11, 2026 (day eight) | Still 01.000.001 | Nine days on the same build and no announcement. We checked every thread active in the previous 24 hours — ninety of them, 544 new replies — and the developer badge still appears only on the opening posts of the two pinned threads. The troubleshooting thread reaches 115. The same day, the game went to #1 on Japan’s sales chart with 76,530 PS5 copies. On the technical side: a fourth player confirmed the Hyper-Threading stutter fix, the first AMD crash fixes appeared, the NVIDIA 616.92 tally reached four bad to two fine, and a new softlock was reported at the Mount Oe gate |
| Sep 10, 2026 (day seven) | Still 01.000.001 | A full week with the same build — Steam has served 24769601 since September 2 — and still no announcement since the million-copies post. The pinned troubleshooting thread reaches 109 replies; we checked the page markup and the developer badge appears exactly once, on the account that opened the thread — no reply anywhere carries it. “Constant crashing” is at 152, the Oni Refuge stutter thread jumped 15 in a day to 74, and fifteen new bug threads opened. Two things changed the technical picture: the community found the first independently reproduced stutter fix (disabling Intel P-cores), and NVIDIA’s 616.92 driver landed on the 9th with players blaming it and crediting it in equal measure. The forum mood shifted too, from asking for a fix to asking to be acknowledged at all |
| Sep 9, 2026 (day six) | Still 01.000.001 | Steam’s build unchanged since September 2; no announcement since the million-copies post (now 142 comments, 2,429 upvotes, a handful asking for a fix). The troubleshooting thread reaches 105 replies, still zero staff; “Constant crashing” reaches 147, with the frame-rate cap hardened into the consensus workaround and the “RTX 5000 only” theory killed by RTX 4080 and RX 9070 XT reports. New on the ledger: the Okuni’s Kabuki Dance island softlock (three players in one day). Steam’s weekly chart for September 1–8 has the game at #2 behind The Blood of Dawnwalker |
| Sep 21, 2026 (day eighteen) | Still 01.000.001 | Nineteen days on one build. The board added 16 topics and 168 comments in a day (1,211 topics, 12,809 comments in all), the troubleshooting thread reached 155, and the developer badge is still on none of it — the newest post there asks Capcom outright whether a patch is coming for a shader cache that has to be deleted before every launch. Steam held above 90% for a second reading (90.2%), and the Chinese–English gap closed to 7.7 points. No new softlock case; the day’s new bugs are single reports — a Steam Overlay that pins the mouse cursor mid-screen, and a player whose stutter arrived with NVIDIA 616.92 in every game he owns. The only real movement was ours: the stuttering fix and the face models now have their own pages, and the costumes and game length pages were rebuilt on the guides and medians that now exist |
| Sep 22–23, 2026 (days nineteen and twenty) | Still 01.000.001 | Twenty-one days on one build; we did not read the board on September 22, so this row covers two days. The board added 20 topics and 396 comments (13,172 comments across 1,226 listed topics), the troubleshooting thread reached 156, and the developer badge is still on none of it. The only change in Steam’s app record was two store tags trading places. Steam reviews held at 90.3%. No new softlock case. The new reports are singles: random freezes on SteamOS, a 30 fps lock after using REFramework to get past the boot crash, and a second 16 GB card that crashed until texture quality came down. Two new threads ask for controller button remapping, which the game does not offer by design. New here: a charms page with every effect and unlock, since the early-purchase Lion Dog charm leaves sale on September 24 and 25 |
| Sep 28, 2026 (day twenty-five) | Still 01.000.001 | Twenty-six days on one build; we did not read the board on September 25, 26 or 27, so this entry covers four days. The app record changed once more, and it was store tags trading places again. The board added 35 topics and 473 comments; the developer badge is on none of them, and the troubleshooting thread went from 156 to 160. A third player hit a stuck objective in Okuni’s Kabuki Dance, and the Russian reporter took theirs to the official thread. Four players now agree the final boss’s phase-two “zero damage” is armour, not a bug. The early-purchase bonus closed on September 24 and 25, and our editions and charms pages still described it as open until today. Steam reviews rose to 90.6% |
| Oct 12, 2026 (day thirty-nine) | Still 01.000.001 | Forty days on one build. We did not check on October 11, so this row covers two days. The app record changed again, and again only two store tags swapped places. No Capcom post. The board added seven topics and 50 comments, with the developer badge on none. New in the performance ledger: a crash during fast travel that forces Windows to reboot, a black loading screen after skipping a cutscene, and an untested Options-button workaround for the DualSense map key. Steam reviews held just under 91% (90.96%) |
| Oct 10, 2026 (day thirty-seven) | Still 01.000.001 | Thirty-eight days on one build. The app record changed once more, and again only two store tags swapped places. No Capcom post. The board added two topics and 24 comments, with the developer badge on none. A second player reports overwriting a Carnage save by starting from scratch, now on the missions page, and the official troubleshooting thread gained a crash-then-blocked entrance report at Kiyomizu-dera. Steam reviews held at 90.9% |
| Oct 9, 2026 (day thirty-six) | Still 01.000.001 | Thirty-seven days on one build. Steam’s app record changed again, and this time we could compare it with the saved copy field by field: two store tags swapped places, and nothing else moved. No Capcom post. The board added three topics and 49 comments, with the developer badge on none. New single reports: a “Failed to save” error (code CSE 03400AAAAAAT), and a player whose cleared save was overwritten when starting Carnage, now on the missions page. Steam reviews held at 90.9% |
| Oct 8, 2026 (day thirty-five) | Still 01.000.001 | Thirty-six days on one build; we did not read the board from September 29 to October 7, so this entry covers ten days. The build Steam serves is unchanged. Steam’s app record did change, but we no longer had our earlier copy to compare it with field by field, so we cannot say what moved; nothing about it touched the build. Capcom posted nothing on Steam. The board added 56 topics and 694 comments, the troubleshooting thread went from 160 to 169, and the developer badge is on none of it. One of the two Linux players stuck at an endgame loading screen got through by turning DLSS off. New single reports: a third Mount Oe blocker, a crash when ringing the bell in The Oni’s Apprentice, a controller that also drives the mouse cursor, and combat hints that never stop in New Game Plus. Steam reviews rose to 90.9%. On game length, the HowLongToBeat story median rose from 21 to 22 hours as the sample doubled |
| Sep 24, 2026 (day twenty-one) | Still 01.000.001 | Twenty-two days on one build. Steam’s app record changed again, and again it was only store tags trading places. The board added 10 topics and 105 comments; the developer badge is on none of them, and the troubleshooting thread stayed at 156. A correction to how we count: Steam’s topic list only shows threads active in the last 30 days, so four old threads that vanished from it on September 23, and four more today, were not deleted. They aged off. We now count the 13,381 comments across 1,251 topics we have read. A second player reported the Okuni cutscene that never plays, two weeks after the first. Steam reviews rose to 90.4%. Three English guides now agree that charms and their levels carry into New Game+, and the charms page no longer marks that as single-source |
That is the honest whole of it as of September 28. We are not going to pad this page with invented fix lists — several search results already do, and none of them cites an official source. When the first real notes land, they go here verbatim with the official link, the same day.
How we will report each patch
- Official text only. Capcom’s notes get quoted, not paraphrased — paraphrase is how “planned for a future patch” becomes “added” in secondhand coverage.
- Per-platform version numbers, because PC and console numbering will drift apart and searchers use the numbers as queries.
- The fixed-or-not ledger: each known issue from the demo period gets an explicit fixed / not-fixed / not-mentioned status per patch, checked against community reports rather than assumed from the notes.
Known issues awaiting their first patch
Carried over from the demo period and the launch reviews, the watchlist we check against every patch: the washed-out image complaint (a community-made tweak and an HDR analysis exist, but no official toggle), soul-absorb trigger failures on some third-party and Xbox controllers, the forced depth-of-field with no menu switch, no ultrawide support beyond 16:9, and the handheld age-verification softlock reported on SteamOS devices. Added since launch: the mid-game area crashes that frame caps only partly tame, and the Okuni’s Kabuki Dance island softlock — three players stranded on September 8 after a death or crash on the sandbar left the boat gone — a Mount Oe gate that stays shut if you climb down before shooting the barrels (September 10), and saves in the end-game castle area that will not load. None of these has an official acknowledgment yet ⚠ community reports, collected from the official troubleshooting thread. The deep dive on each issue — with the community fixes that exist as of September 28 — lives on the performance page; this page stays the ledger of what each patch changes.
Playing tonight? Check exactly when your platform unlocks — and if you kept your demo save, the Kubi Akari charm is waiting in the full game.
Frequently Asked Questions
Is there a day-one patch for Onimusha: Way of the Sword?
Apparently not beyond the preload revision. Capcom’s notice warned “additional update data” might download after launch, but through the first console night no version above 01.000.001 was observed and no notes were published. The launch build is effectively the preload build — one revision above the disc’s 01.000.000.
What version is the game at right now?
01.000.001 on PS5, per the preload listing. Steam and Xbox version numbers have no public listing yet; we will record each platform’s numbering scheme here as patches land, since Capcom titles usually run different version strings per platform.
Where do official patch notes appear?
Historically for Capcom: the Steam news hub for PC and the official site or support pages for consoles. We link every patch here verbatim from those sources — if a change is not in official notes, we say so rather than repeating secondhand claims.
What do players want patched first?
Thirty-seven days in, the list reads: mid-game area crashes, still with no universal fix — a 195-reply thread where capping the frame rate helps many players but fails for a sizeable minority; traversal stutter in the Oni Refuge and the Kyoto hub, which has a reproduced fix on Intel hybrid CPUs (keeping the game off the P-cores — see our stuttering page) but none from Capcom; the “Okuni’s Kabuki Dance” island softlock, now two confirmed lockouts on the boat to the island, one after a crash and one after a death; saves in the end-game castle area refusing to load; and then the older asks — the washed-out image, native DualSense support on PC, 32:9 ultrawide and an FOV slider. Capcom has acknowledged none of it in public, and the loudest thing on the forum now is players asking for acknowledgement rather than for a patch.
Sources
- Capcom — Release and preload notice (“additional update data”)
- Steam news hub — where official notes appear first
- PS Store tracker — preload version 01.000.001
- Steam community — official demo troubleshooting thread (known issues)
- Capcom — launch-day PC troubleshooting sticky (driver minimums)
- Capcom — the September 8 “1 million sold” announcement (first official Steam post since launch)
- Steam thread — “Constant crashing” (193 replies, no staff reply)
- Steam thread — “Last boss” (46 replies in two days, Sep 18–19: the checkpoint complaint, again)
- Steam thread — “Okuni Kabuki Dance Mission Bug/Glitch/Game breaking?” (island boat softlock, Sep 8)
- Steam — SteamDB weekly top sellers, 1–8 September (Onimusha #2)