WoW Forever Beta Known Issues & Week 1 Status Guide (Sep 2026)

Four days into the World of Warcraft: Forever beta and we are still sitting on the same client Blizzard shipped on September 17: build 1.60.1.69913. That is not a crisis by itself. It is a classic early-beta beat. The Known Issues list already labels roughly eight problems as fixed in the next build, Kaivax posted a same-day EU routing update on September 21, and player threads are loud about addon settings that refuse to stick, city FPS drops, Mac client pain, and a wave of beta removals tied to names and chat.

This piece is the week-1 bugs and status field guide. It is not the cap, dungeons, and what-to-test overview, and it is not the how to join / packs walkthrough. If you already have a character on Zephras or Coldridge, use this to decide what is worth testing hard before the first patch lands, and what you should treat as temporary noise.

What is the Forever beta status as of September 21?

World of Warcraft: Forever beta opened September 17, 2026, PST, and runs through October 21, 2026, PST. Blizzard’s launch post is clear on the early band: week 1 opens the Skyborne race and Zephras Isle, Hall of Thanes (13–18), Ruins of Lordaeron (15–20), and all zone content up to level 20. The level cap starts at 20 and raises to 30 later in the test. Full Forever launch remains November 4, 2026, at 3:00 p.m. PST, included with Subscription or Game Time.

As of the morning of September 21, community patch watchers still see 1.60.1.69913 as the live beta build. That means every “fixed in the next Beta build” line on the Known Issues list is sitting in queue. The first working-week window after the launch weekend is exactly when you expect that build to move.

Treat week 1 as a systems and stress test, not a polished preview tour. Queues, disconnects, and UI half-states showed up hard on day one in player comments. Some of that is expected beta noise. Some of it is tracked. The rest is what you should log and send upstream instead of rage-quitting for the week.

Which Forever beta known issues are fixed in the next build?

Blizzard’s Known Issues post (opened September 17, expanded September 18) explicitly tags these as fixed in the next Beta build:

• Waylaid Crates fail when an item’s maximum stack size is smaller than the quantity the crate asks for
• Waylaid Crate: Apprentice Curiosities rejects Greater Magic Essence and wrongly accepts Lesser Magic Essence
• Teldrassil quest Escaping Ban’ethil: Sentinel Lynessa Duskblossom runs too fast and spams Strike
• Starshards (Night Elf Priest racial) does not benefit from the Twilight Focus talent
• Vengeance (Retribution Paladin talent) can activate off periodic critical strikes
• Ranking up Holy Strike does not feel meaningful per rank
• Create Firestone ranks 3 and 4 omit the conjured-item tooltip section
• Coldridge Valley does not reveal on the map when explored

That is eight concrete promises. Two of them matter for class feel right now. The Vengeance fix should stop Retribution from counting periodic crits toward the talent, which means Ret numbers on this build are inflated relative to the next one. Holy Strike’s rank curve getting a feel pass is the other class-facing change you will actually notice when you retrain.

If you are mid-level on a Dwarf or Night Elf route, keep testing those quests and crates on this build so Blizzard has before-and-after data. Just do not write a launch theorycrafting spreadsheet that assumes Vengeance still procs off DoT crits after the next client.

What Forever beta bugs are still marked work in progress?

The same Blue list carries a longer WIP set with no next-build promise. These are the ones that change how you play or how you read your sheet:

• Glancing blows are wrong for casters at every level (chance and damage reduction). Melee glancing damage reduction is wrong against higher-level targets (chance is fine; equal-level reduction is fine). Character-sheet glancing numbers are therefore inaccurate.
• Queueing an on-next-attack ability (Heroic Strike / Cleave / Raptor Strike) disables your spell queue window
• Taking damage while channeling Arcane Missiles fires a full-damage bolt instead of a truncated one
• Armor bonuses from consumables and buffs are multiplied by Bear Form armor
• Resurrection sickness duration is wrong at lower levels
• Guild charters may not accept signatures; Blizzard temporarily allows handing in a charter with no signatures
• Cooldown Manager is unfinished and varies by class
• Character pane does not display Level, Class, or Titles
• Warlock / Hunter pet character-sheet stats (mana, health from Stamina, hit scaling, expertise, movement speed) are incomplete or wrong
• Opening the Legacy System with hotkey Y before level 25 throws LUA errors on tabs 1 and 3
• Barber chairs cause a LUA error
• Character friends in beta are disabled
• The minimap may sit partially off-screen

None of these are “ignore and hope.” They are the reason beta exists. Log them when they block a clean test, then move to a different system so your /played still produces useful feedback.

What did Kaivax say about EU Forever beta routing on September 21?

European testers spent the first couple of days fighting movement freezes, world-interaction stalls, and disconnects. Forum reports early on even tracked beta traffic landing on West Coast cloud paths. On September 21, Kaivax posted Addressing EU Beta Routing Issues.

The short version from Blue:

• Routing issues in the first days hurt movement, interaction, and sometimes staying connected
• Engineers focused on anything inside Blizzard’s control
• Over the prior 24 hours, Blizzard developed and implemented solutions to streamline routing to the Beta for the EU region
• Some remaining routing pain can sit outside Blizzard (ISP problems, upstream detours, firewall software that slows or blocks the game)
• They believe the in-house fixes should have improved or fixed what many players saw, and they will keep monitoring

If you are an EU tester who could barely leave the starting hut on day one, re-test connectivity today before you write off the week. If you still rubber-band after the routing pass, document traceroute / ISP notes in a bug report instead of assuming the September 17 failure mode is still the official server state.

Which player-reported Forever beta problems are loudest right now?

These are not on Kaivax’s Known Issues list as of the September 18 update. They dominate forum threads and the WoW Forever Builds weekend roundup, so treat them as community signal:

Addon settings that do not save

Multiple testers say addons forget options after a relog or `/reload`, which points at SavedVariables not writing cleanly. Unit frames and layout packs get hit first. Community workaround addons exist; some players say they help, others say they do not. Until Blue confirms a fix, assume you may need to re-apply layouts after every session and keep a screenshot of your Edit Mode setup.

City FPS drops and memory pressure

One common report: steady outdoor FPS in a Skyborne starter area, then a collapse to teens in Stormwind or Dalaran. That pattern smells like a city asset / memory leak problem more than a “your PC is bad” problem. Test outdoors, then a capital, then outdoors again, and include hardware plus graphics preset in the report.

Mac client instability

Mac players have posted loading-screen crashes after character create since launch. Community advice circulating includes dropping graphics hard, and at least one thread points at setting Secondary Lighting to Fair before entering the world. If you are on Mac, stabilize the client first. Content feedback is useless if you cannot stay in the world for ten minutes.

Beta removals for names and chat

A fast-growing “Banned from Beta” thread collected dozens of replies in hours. Most replies assume naming-policy breaks or offensive chat. Blizzard has not published a dedicated Blue PSA on that wave in the sources above. The practical rule is the same as every public test: name characters like you would be fine seeing them quoted in a moderation note, and keep chat clean. Refund expectations after a few hours of play are usually low.

How should you spend week 1 while the Forever beta is still on 1.60.1.69913?

You have a hard level-20 ceiling for now, two new dungeons in the 13–20 band, Skyborne / Zephras content, and a pile of WIP combat UI. Use that.

Prioritize feedback Blizzard cannot get from a spreadsheet:

• Quest escorts and zone reveal bugs that are already tagged next-build (prove the before state)
• Class talent edge cases on the next-build list (Vengeance, Starshards / Twilight Focus, Holy Strike ranks)
• Glancing-blow feel on caster and melee against higher-level mobs, with combat logs attached
• Pet sheet lies for Hunter and Warlock while you still remember what Classic-era scaling “felt” like
• Dungeon queue health for Hall of Thanes and Ruins of Lordaeron once you are in band
• EU latency and disconnect rates after the September 21 routing changes

Deprioritize until the next build or a hotfix:

• Final Retribution DPS rankings that lean on current Vengeance proc behavior
• Perfect addon UI setups you expect to survive relogs
• Map completion OCD in Coldridge while fog-of-war is broken
• Barber / friends-list / Legacy-hotkey rabbit holes unless you are specifically UI testing

If you are already thinking past beta into launch economy prep, keep notes on vendor prices, early crafting loops, and gold sinks you notice under the level-20 cap. That kind of soft intel travels well into November without depending on buggy sheet math. Players who want a launch-ready character path can watch AccountShark’s Forever waitlist and gold prep coverage separately; this article stays on the beta client’s health.

What should you do when Forever beta bugs block a session?

• Update GPU drivers and confirm you are on the Forever Beta tile in Battle.net, not a different WoW flavor.
• Reproduce once with addons disabled if the bug looks UI-related.
• Note build 1.60.1.69913, realm, race/class, level, and exact steps.
• For EU connectivity, re-test after Kaivax’s September 21 routing note before assuming the day-one path is unchanged.
• For Mac crashes, lower graphics and try the Secondary Lighting / Fair community workaround before filing a duplicate “won’t launch” report.
• Expect beta characters not to carry to November 4. Spend your /played on feedback quality, not on a forever bank alt fantasy.

The beta calendar still gives you runway through October 21. The first patch after launch weekend is the real week-1 story. Until that build drops, the Known Issues list is your checklist, the EU routing post is your connectivity baseline, and the player threads are the early-warning radar for problems Blue has not formally claimed yet.

Frequently Asked Questions

What is the current WoW Forever beta build on September 21, 2026?

As of September 21 morning checks reported by WoW Forever Builds, the Forever beta is still on 1.60.1.69913, the same build that launched on September 17. That means every issue marked “fixed in the next Beta build” on Blizzard’s Known Issues list has not shipped to the live test client yet.

Which WoW Forever beta known issues are fixed in the next build?

Blizzard’s list tags eight items for the next build: Waylaid Crate stack failures, Apprentice Curiosities essence targeting, the Escaping Ban’ethil escort on Teldrassil, Starshards not gaining Twilight Focus, Vengeance proccing from periodic crits, Holy Strike rank feel, Create Firestone ranks 3–4 tooltip text, and Coldridge Valley not revealing on the map. Those are Blue promises, not player rumors.

Did Blizzard fix EU WoW Forever beta routing problems?

On September 21, Kaivax said engineers implemented solutions over the prior 24 hours to streamline EU beta routing, after early-test movement, interaction, and disconnect problems. Blizzard also notes some remaining pathing issues can sit with ISPs, upstream routes, or local firewall software. EU players should re-test after that post before assuming day-one routing is still in force.

Why do my Forever beta addon settings reset after a relog?

Player reports describe SavedVariables failing to persist across relog or `/reload`, especially for unit-frame and layout addons. That problem is not listed on the September 18 Known Issues post. Until Blizzard confirms a fix, expect to re-apply settings, keep a layout screenshot, and file a bug with addon names attached.

Is the WoW Forever beta Mac client supported right now?

Mac players are in the test, but community threads report loading-screen crashes after character creation and other graphics instability. Workarounds circulating include lowering graphics settings and setting Secondary Lighting to Fair. Stabilize first, then test content. Official Known Issues focus on gameplay systems, not a dedicated Mac crash entry.

What is the Forever beta level cap in week 1?

Blizzard’s Forever Beta Now Live post says the level cap starts at 20 when the test begins and raises to 30 later. Week 1 content is built around that early band: Skyborne / Zephras, Hall of Thanes, Ruins of Lordaeron, and zone content up to 20.

When does the WoW Forever beta end and when does Forever launch?

Beta runs through October 21, 2026, PST. World of Warcraft: Forever launches globally on November 4, 2026, at 3:00 p.m. PST, with access included for Subscription or Game Time players per Blizzard’s pre-purchase article.

Are people getting removed from the Forever beta for names or chat?

Forum threads claim a wave of beta removals, often blamed on naming policy or chat. Those reports are player-side as of this writing; treat them as a reminder to follow naming and chat rules, not as a confirmed Blue policy post. Pick names you would be comfortable defending in a support ticket.

Should I theorycraft Forever classes hard on build 1.60.1.69913?

Soft takes are fine. Hard rankings that depend on Vengeance periodic crits, glancing-blow sheet values, or unfinished pet stats are premature. Several of those systems are either next-build fixes or WIP on the official list. Capture logs now, then rebuild conclusions after the first beta patch.

Where do I find the official WoW Forever beta known issues list?

Start with Kaivax’s Forever Beta Known Issues thread on the official forums (September 17 open, September 18 additions). Wowhead’s Forever news mirror is a convenient secondary copy of the same Blue text. Cross-check any “next build” claim against that post before you treat a fan roundup as source of truth.