The documented numbered updates below are for the Demo, not the October 13 retail release. As of October 15, 2026, no numbered post-launch patch log has been confirmed for this page. Do not use Demo version 1.03 as proof of your installed retail version.
Documented update history
| Date | Build discussed | Main scope |
|---|---|---|
| June 12, 2026 | Demo 1.03 | Loading crashes, blood effects, audio and GPU detection |
| June 10, 2026 | Demo 1.02 | Upscaling support, crashes and progression problems |
| June 8, 2026 | Demo 1.01 | Stability, Chapter 1 performance and Lantern interactions |
| October 10, 2025 | Pre-release playtest | Save corruption checks, equipment and frame-generation defaults |
Demo 1.03 changes
The June 12 update addressed a crash while loading Witch Hunt and another crash involving corrupted blood effects. It also mitigated an audio loop after killing certain enemies, improved automatic GPU detection, and continued performance work across the Demo's two levels.
These are historical fixes for that Demo build. They do not establish that the same problem is present, absent or fixed in a current console or retail PC installation.
Demo 1.02 changes
The June 10 notes restored DLSS 4.5 and XeSS 3 features on supported GPUs and added hardware checks for AMD FSR4 Frame Generation and AntiLag2. Hardware support was a condition of those changes, rather than a promise that every GPU could use every option.
The update also addressed crashes linked to excessive player events and certain blocked attacks. Other fixes covered becoming stuck after respawning, skyboxes, persistent blood effects on backstabbed enemies, the Demo progression cap, unavailable Mice dialogue, and jumps in loading or shader-compilation progress screens.
The announcement instructed Demo players to restart after enabling Frame Generation. Treat that instruction in its original build context rather than as a universal remedy for retail problems.
Demo 1.01 changes
The first numbered Demo hotfix targeted crashes during memory cleanup and tutorial screens. It also addressed places where players could become trapped in Chapter 1 geometry, improved performance in parts of Revival and the General Lothaire encounter, and made Lantern interactions more consistent across both Demo levels.
The same announcement said ray tracing had been temporarily disabled while the team investigated a fix. That historical statement is not a current retail feature list.
The older playtest hotfix
The October 2025 playtest update addressed several save-related crashes, added checks against save corruption, and fixed Fire disappearing from equipment. It also moved a weapon-change tutorial and corrected Frame Generation being enabled by default.
Its build predates both the June Demo and the retail launch. Applying old configuration-file workarounds to a newer installation without matching instructions can change settings without resolving the current issue.
Checking a current installation
Check the version or build information shown by your platform or game, then compare the platform, date and build named in an official announcement. An available platform download and a published changelog are different pieces of information; one does not supply the missing details of the other.
If a current problem has no matching published fix, record the platform, installed build, the action that reproduces it and any crash-report reference. Avoid assuming that a similar symptom in an old Demo means the retail issue has the same cause.