Crash, Error, Disconnect, and Blocked-Progress Troubleshooting
Record the error code, time, platform, and reproduction steps, then safely isolate service status, client, network, and character or quest progression.
Save the exact error and time, then check current patch notes and Blizzard Support for that code or known issue. If widespread, wait for service recovery; if device-specific, restart, update, and verify files; if network-specific, isolate the connection; if character or quest-specific, re-track, relog, change area, and reproduce. Do not delete characters, install unofficial tools, or alter save data.
Five Facts to Record First
5Exact Error and Time
Capture code, message, time, and whether it followed an update.
Platform and Edition
Record PC or console, launcher, owned DLC, and game version.
Scope of Impact
Determine all characters, one character, one region, one quest, or party-only.
Reproduction Steps
Safely reproduce the shortest sequence from login to symptom once.
Most Recent Change
Record recent patch, driver, setting, network, DLC, or quest changes.
Decision Checks
5Service Outage or Maintenance
Exclude widespread service issues before changing the device.
Check official support, Battle.net status, current notices, and another device or connection.
For a widespread outage, avoid repeated retries and wait for official recovery.
Stop before reinstalling or resetting settings during an official outage.
For expansion-only access failure, isolate license ownership and platform.
Test base-game login separately from expansion-region access.
Launch, Crash, and Game Files
Isolate temporary conflicts, missing updates, and damaged files safely.
Check restart, OS, game and GPU updates, free space, background conflicts, and file verification.
Try restart, updates, official launcher repair, then category-specific settings reset one at a time.
Stop before character deletion, unofficial repair, or bulk registry changes.
Check DLC installation separately from the base-game update.
Base-game-only users omit DLC checks and use the same device flow.
Disconnects, Latency, and Login Failure
Locate reproduction at service, home network, or device.
Check wired versus wireless, another connection, router restart, other services, and party-only behavior.
Exit active content, log out, restart equipment, and retest safely in town.
Stop before unsupported port changes or disabling security.
Separate shared War Plan synchronization from general connectivity.
Use a base-game solo town or public event for the same network comparison.
Blocked Quest or Dungeon Progress
Safely recover tracking, instance, or objective-state mismatch.
Check tracked quest, prerequisites, objective text, floor, party leader, and current known issues.
Try town return, re-track, relog, then safe instance recreation in that order.
Stop before irreversible choices, reward claims, or valuable-item consumption.
Separate expansion quest prerequisites from War Plan or Cube unlocks.
Use the same safe order for base campaign and class quests.
Evidence for Official Support
Create a reproducible report without sensitive information.
Collect code, time, version, region, character type, steps, attempted fixes, and images.
Submit the shortest reproduction and results to the matching official support category.
Stop before posting passwords, auth codes, personal data, or full system details publicly.
State edition, purchase platform, and inaccessible expansion feature.
Base-game-only reports state game version and affected content.
Troubleshooting Safety Boundaries
6- Keep the exact error code; do not reuse fixes for a different code.
- Do not reinstall or reset during an official outage.
- Do not delete characters, consume valuables, use unofficial tools, or alter save data.
- Do not recommend permanent security disablement or unsupported port changes.
- No unverified universal fix, wait duration, or recovery time is guaranteed.
- Never include passwords, auth codes, or personal data in logs or public reports.
Checks as of Patch 3.1.1
4- Current notes continue to list quest, dungeon, UI, and controller fixes.
- Do not equate a fixed issue with a current symptom; check build number.
- For a specific disconnect code, search its official article before generic steps.
- Console-specific issues also require the platform's official support.
Related Guides
8Settings Guide
Safely reset input and graphics.
Patch 3.1.x
Review known fixes.
Progression
Check prerequisite order.
Expansion Access
Separate DLC ownership.
Skovos and Temis
Review expansion unlock order.
War Plans
Isolate shared progression.
Activities
Choose a reproduction area.
Build Diagnostics
Separate bugs from build faults.