Diablo IV Patch 3.2.3: How to Fix the Prime Evil Powers Quest Block

The October 14 hotfix prevents a quest progression bug

Blizzard's Diablo IV patch notes list version 3.2.3, build 73883, for all platforms on October 14, 2026. The patch addresses a seasonal quest problem: a character could use a Splinter of a Prime Evil before finishing the Seasonal questline, which prevented that character from completing the line and accessing Prime Evil Powers. This is a targeted fix, not a full seasonal rebalance.

The important detail is Blizzard's developer note. The patch prevents the issue from happening to characters going forward, but it does not reset quest progress for characters already affected. That means installing the update may not make the stuck character's quest suddenly resume. If you already encountered the bug, follow Blizzard's stated workaround rather than repeating the same steps on that character.

Blizzard says to create a new character in the same partition and complete the Seasonal questline. The note specifies that this applies within the same Normal or Hardcore and Normal or Solo Self-Found partition. It says this unlocks Prime Evil Powers for all characters in that partition. Read the exact wording in the current notes before choosing a character type, especially if you play across multiple modes.

This guide focuses on that documented workaround and a careful way to check your progress. It does not promise that every quest issue has the same cause or solution. If your symptoms differ, compare them with the official description and use Blizzard support for account-specific problems. Avoid deleting characters or changing modes based on assumptions that are not in the patch notes.

  PATCH FACT

Blizzard says the fix prevents new cases but does not repair an already bugged character's quest progress. The workaround is a new character in the same partition.

Check whether the official workaround applies to you

Before creating another character, make sure the issue matches Blizzard's description. The patch note refers to using a Splinter of a Prime Evil before completing the Seasonal questline, followed by being unable to finish that questline or access Prime Evil Powers. If you are stuck at a different step, do not assume the workaround will solve it; first compare your quest state with the official note.

Confirm that the game is updated to patch 3.2.3 or a later build. The notes identify the fix as an all-platform change, and Blizzard maintains a continuing patch page. A launcher can sometimes need a restart to show an update, so check your platform's version information and make sure installation completed before repeating quest actions.

Keep the character's mode and partition in mind. Blizzard specifically says the new character must be in the same partition, naming Normal or Hardcore and Normal or SSF. If you start a character in another mode, it may not share the relevant unlock. When in doubt, verify the character selection details and Blizzard's current terminology rather than relying on a community shorthand.

Take a screenshot or note of your quest journal before making changes. This does not alter the game, but it helps you describe the issue accurately if you contact support or compare your state with the patch note. Do not share private account information in public posts. A short description of the action, the quest step, and the error is usually more useful than a vague report that the season is broken.

• Check that your symptom matches the Splinter of a Prime Evil issue.
• Confirm patch 3.2.3 or later is installed.
• Identify the affected character's Normal/Hardcore and Normal/SSF partition.
• Keep notes before starting a new character.

Follow Blizzard's workaround step by step

First, update Diablo IV through the platform you use and confirm the game has finished installing. Blizzard lists patch 3.2.3 for all platforms. If you play on more than one device, check each installation rather than assuming the update on one platform updated another. Then return to character selection and identify the partition where the issue occurred.

Create a new character in that same partition. Blizzard's note does not tell players to delete the affected character, and it does not ask them to restart the entire account. Keep the original character available unless Blizzard support gives you a separate instruction. The workaround is specifically to complete the Seasonal questline on another character in the same partition.

Play through the Seasonal questline with the new character and follow the current in-game objectives in order. Do not use a Splinter of a Prime Evil before the questline is complete. The patch was designed to prevent that sequence from blocking progression again. If an objective is unclear, use the quest tracker and Blizzard's support documentation rather than skipping ahead based on an old guide.

After completing the questline, check the relevant seasonal interface on the affected partition to see whether Prime Evil Powers are available to its characters. Blizzard says the completion unlocks the powers for all characters in that partition. If that does not happen, record what you completed, your platform, and your current version, then contact Blizzard support with those details.

  SAFE STEP

Blizzard's note says to create a new character in the same partition and complete the seasonal questline. It does not say to delete the old character.

Mistakes that can waste time or complicate the issue

Do not keep trying the same quest interaction on the affected character if it is the exact bug Blizzard describes. The developer note says its patch does not reset already bugged quest progress. Repeating the action may not clear the state, and it can make it harder to explain which steps you have already tried.

Do not create the workaround character in a different partition. The partition requirement is part of Blizzard's instruction, not a minor preference. Check the mode shown at character creation and choose the matching one. If you play Hardcore or Solo Self-Found, take extra care to confirm the labels before starting.

Do not treat unofficial instructions as a replacement for the patch notes. Community posts can be useful when players compare experiences, but one person's workaround may apply to a different quest issue, platform, or build. If advice conflicts with Blizzard's explicit note, use Blizzard's instruction as the baseline and ask support about your specific case.

Avoid sharing account credentials, one-time codes, or remote access with anyone claiming they can repair the character. Official support does not need your password. Use Blizzard's own support site and keep any screenshots or error details limited to information relevant to the quest problem.

• Don't delete the affected character based on this issue alone.
• Don't choose another partition for the workaround character.
• Don't assume a different quest bug has the same fix.
• Use Blizzard's official support channel for unresolved cases.

Other gameplay issues included in patch 3.2.3

The same patch notes include several additional bug fixes. Blizzard says Tyrael's spawn location after defeating Baal could make it difficult to pick up Baal's loot, and that the Sandstone Golem could fail to respawn if a player died during the fight. It also corrected an issue where the Countess could pass through a fog wall and prevent encounter progression.

The update also addresses certain affixes that could not be rerolled with the Horadric Cube. Blizzard names Impairment Reduction, Barrier Generation, +Healing, and Critical Strike Damage. If you use the Cube and believe an affix is still unavailable, first check that the relevant item and affix are eligible under the current rules. The patch note describes particular affixes, not a universal change to every reroll limitation.

Blizzard says it fixed an issue where not all monsters dropped Unbroken Bones during the Necromancer class mechanic quest Call of the Underworld. It also lists general stability, performance, visual, and user-interface improvements. The notes do not give a separate performance guarantee for each platform, so treat those lines as a summary of intended fixes rather than a promise of a specific frame rate.

These items are useful if you are deciding whether a problem is part of the latest patch. Compare what you see with the exact bug descriptions and build date. If an issue continues after updating, it may need a different fix or a later patch. Record the steps that reproduce it and send them through Blizzard's official support or reporting route.

• Baal loot pickup after defeating the boss.
• Sandstone Golem respawn after player death.
• Countess fog-wall encounter progression.
• Selected Horadric Cube affix rerolls and Unbroken Bones drops.

A clean plan for returning to the season

If your character was affected, decide whether the new-character workaround is worth the time for you. Blizzard's note is specific about what it expects to unlock, but the quest still needs to be completed again on that character. If you would rather wait for another update or ask support first, that is reasonable; do not feel pressured to erase progress or rush through content.

If your character was not affected, update the game and continue the Seasonal questline normally. The patch is intended to prevent the invalid early use of a Splinter from blocking completion. Follow the quest objectives and avoid using the item ahead of the intended step. If you see an error, capture the wording and check Blizzard's current patch page for a newer note.

Keep patch notes close when seasonal systems change. A fix can alter how an interaction behaves, while a workaround may remain necessary for accounts already in a broken state. Guides can become outdated quickly, so check their publication date and compare them with the current official source before following a long sequence of instructions.

Patch 3.2.3 is a good example of why a small bug fix can matter to gameplay. It prevents one sequence from blocking access to a seasonal power system, but it does not retroactively repair all progress. Knowing that distinction can save time, protect your character choices, and help you explain the issue clearly if the official workaround does not resolve it.

  NEXPLAY TAKE

Follow the official workaround exactly, keep the affected character intact, and contact Blizzard if the same-partition completion does not unlock the powers.