WRITTEN ARTICLE · BETA TROUBLESHOOTING
WoW Forever beta known issues: errors, access and troubleshooting
Check Blizzard’s beta issues, separate game bugs from addon errors, and find a practical reporting checklist for access, quests, classes and crashes.
Artwork © Blizzard Entertainment
Start with the symptom, not a reinstall
An error during beta can come from the game, an addon or a connection problem. Record what you were doing and the first error before changing several settings at once. Keep a note of your client build so a later result can be compared fairly.
This page is a dated reference, not a live server-status service. Use the original Blizzard thread for the latest changes; a planned fix does not mean the build installed on your machine contains it.
Selected issues on Blizzard’s September 17 list
These are selected official reports, grouped by what a player may notice.
| Area | Reported issue | Listed status |
|---|---|---|
| Interface | Barber-chair errors; minimap positioning | Known issue |
| Social | Character friends disabled | Known issue |
| Waylaid Crates | Stack-size and essence turn-in problems | Next-build fix planned |
| Legacy | Opening with Y below level 25 can cause errors | Known issue |
| Combat | Incorrect glancing-blow values | Work in progress |
| Guilds | Charter signatures can fail | Temporary zero-signature hand-in |
| Exploration | Coldridge Valley map reveal | Next-build fix planned |
Beta missing, Install greyed out or unable to enter?
Confirm access before diagnosing addon problems. Blizzard directs players to select Forever Beta under In Development in Battle.net. Eligible bundle access can take up to 30 minutes and may require a launcher restart.
Check the full access guide below before purchasing anything or following a workaround. An installation folder alone does not establish that your account can enter the test.
How to distinguish game errors from addon errors
Warcraft Tavern reports inherited Retail addons and keybinds in the beta. That is a reason to inspect the enabled addon list before assuming you are testing a clean interface.
Our suggested isolation procedure: note which addons are enabled; temporarily disable them for the test; repeat the same action; then re-enable one at a time. Preserve settings and backups. If the error also occurs without addons, do not blame Wisp merely because it was installed earlier.
Record the first failing action, rather than collecting many later errors that may all have the same cause. Changing a .toc number can remove an outdated label without fixing an incompatible API.
Class tests need the known-issue context
Blizzard lists Starshards/Twilight Focus, Paladin Vengeance and Holy Strike, Firestone tooltips and pet-stat displays among the affected areas. Consult the original list before judging a talent from a single result.
Keep the same equipment, level and target when comparing choices. A display problem and an actual damage calculation problem need different evidence; note which one you observed. Our nine talent proposals include beta-testing notes and remain untested theorycraft.
Crashes, disconnects and latency: what to record
For a crash, record the operating system, graphics hardware, client build and exact trigger. Follow the technical-support link in Blizzard’s launch article. Do not delete all saved settings as your first diagnostic step.
For a disconnect, record the time and whether it happened at login, during loading or in the world. For latency, distinguish delayed actions from low frame rate. Avoid presenting an untested VPN, graphics tweak or addon as a guaranteed fix.
We have not confirmed a universal Mac-crash or EU-latency fix. A workaround reported by another player needs a matching environment and repeatable test before we recommend it as reliable.
A useful report you can copy
Use the following fields. Remove account identifiers, private chat and personal filesystem paths from screenshots or logs before sharing them.
| Field | What to include |
|---|---|
| Environment | Client version/build, OS and relevant hardware |
| Character context | Class, level, zone and affected quest or talent |
| Reproduction | Short numbered steps, expected result and actual result |
| Addon comparison | Whether the same steps fail with addons disabled |
| Evidence | First error, relevant screenshot and observation time |
Related reading and guides
Sources and review notes
- Blizzard / Kaivax: beta known issues, 17 September
- Blizzard: the Forever beta is now live; access and first-week content
- Warcraft Tavern: Forever loads Retail addons and keybinds, 17 September
Source review: 18 September 2026. Official issues below are from Blizzard’s September 17 list. Planned fixes are not marked resolved without a later confirmation. Troubleshooting advice is ours; this is not a Wisp client playtest.
