The Battlefield 6 weekly challenge tally bug appears when Week 3 still shows 10/11 completed even though you’ve finished all tasks.
This weekly progress issue started after the latest update and happens because the challenge tracker is not refreshing its local progress state.
This creates confusion and makes your completed Week 3 look unfinished even when all challenges are done.
Quick Fix
Refresh your challenge data by forcing the menu to reload your weekly progress. If the tally still doesn’t update, apply the fixes below.
Fix 1: Refresh the Weekly Challenge UI to Fix Incorrect 10/11 Count
The weekly challenge tally bug is usually caused by the Week 3 panel not refreshing after the last challenge completes. Reloading the challenge UI forces a fresh sync and often updates the number correctly.
Refreshing the menu fixes the tally without needing to restart the game.
Steps:
- Open Weekly Challenges.
- Switch between Week 2 → Week 3 → Week 4.
- Return to the main menu.
- Open Weekly Challenges again.
Testing Step:
Check if Week 3 now reads 11/11 instead of 10/11.
Root Cause:
The challenge panel does not auto-update your final task completion until the UI refreshes.
Fix 2: Log Out and Back Into EA Account to Resync Weekly Progress
Sometimes the server has your correct 11/11 data but the client shows 10/11. Logging out forces the game to pull your updated weekly progress from the EA servers.
This resync quickly corrects tally desync issues.
Steps:
- Return to the main menu.
- Log out of your EA account.
- Log back in.
- Reopen the challenge screen.
Testing Step:
Check if the tally now shows 11/11.
Root Cause:
The client is using outdated cached data instead of pulling your updated server progress.
Fix 3: Restart the Game to Rebuild Challenge Tracking
Weekly challenge tallies are rebuilt on startup. Restarting the game forces a full refresh of the challenge system and usually fixes the incorrect Week 3 tally.
This fix is most effective after a patch or mid-week refresh.
Steps:
- Close Battlefield 6 fully.
- Restart the EA App/Steam.
- Launch the game again.
- Open the Weekly Challenges tab.
Testing Step:
See if Week 3 now updates to 11/11 completed.
Root Cause:
Challenge tracking scripts finalize only during a clean session load.
Fix 4: Complete Any Daily/Bonus Challenge to Trigger a Hard Refresh
When the final Week 3 challenge fails to fire a completion trigger, completing any additional challenge forces the game to recalculate your weekly totals.
This usually updates the count instantly.
Steps:
- Complete a quick Daily Challenge.
- Return to the Weekly tab.
- Allow the system to recalc challenges.
Testing Step:
Look for Week 3 flipping from 10/11 → 11/11 immediately.
Root Cause:
The last Week 3 challenge didn’t send a completion event, so a new challenge forces recalculation.
Fix 5: Verify Game Files to Restore Broken Weekly Challenge Scripts
If the update installed incorrectly, the challenge completion scripts may be missing or corrupted, causing the tally to freeze at 10/11. Repairing game files restores them.
Steps:
- EA App → Battlefield 6 → Manage.
- Select Repair.
- Restart the game.
Testing Step:
Open the Weekly Challenge panel and check for the correct tally.
Root Cause:
Corrupted challenge metadata prevents full completion from displaying.
Fix 6: Change Matchmaking Region to Reload Weekly Challenge Data
The Weekly Challenge 3 tally bug can appear when your region’s playlist hasn’t synced with the latest challenge data. Switching regions forces Battlefield 6 to pull a fresh weekly-progress table, which often corrects the stuck 10/11 value.
This is especially effective right after mid-week updates or silent backend changes.
Steps:
- Go to Settings → Matchmaking Region.
- Select a different region (EU/NA/Asia).
- Return to the main menu.
- Open Weekly Challenges.
Testing Step:
Check if Week 3 now updates from 10/11 to 11/11.
Root Cause:
Regional playlist sync delays cause your client to load outdated weekly challenge progress.
Fix 7: Change Game Language to Reset the Weekly UI Script
Language toggles force the game to rebuild UI XML files, including the weekly challenge progress container. This refresh often fixes any stuck tally values across all weeks.
This method helps when UI scripts fail to refresh after completing your last challenge.
Steps:
- Go to Settings → Language.
- Switch to another language.
- Restart the game.
- Switch back to your preferred language.
Testing Step:
Reopen the weekly tab—Week 3 should show 11/11 complete.
Root Cause:
Broken UI script containers prevent the final challenge state from displaying properly.
Fix 8: Open the Store Page to Force an Account Entitlement Sync
The in-game store triggers a hard entitlement sync every time you open it. This refresh often fixes challenge tally bugs because the store pulls updated profile data from EA’s servers.
This is a quick way to fix any stuck progression values.
Steps:
- Open the Store.
- Scroll through any bundle.
- Return to the Weekly Challenges tab.
Testing Step:
Check if the challenge counter now updates to 11/11.
Root Cause:
Entitlement sync forces a refresh of your challenge-completion state.
Fix 9: Switch Between Controllers/Inputs to Refresh Challenge State
Battlefield 6 sometimes loads a separate challenge-state container depending on your active input device. Switching inputs forces the game to reload progression data.
This can correct the stuck 10/11 tally instantly.
Steps:
- Plug in a controller (or unplug it).
- Move once to force input detection.
- Return to weekly challenges.
Testing Step:
See if Week 3 now displays full completion.
Root Cause:
Input-device context loads different UI progression tables, which can override outdated data.
Fix 10: Delete Settings Folder to Rebuild Weekly Progression Metadata
If the game has been played across multiple patches, your settings folder might contain outdated challenge references. Removing it lets Battlefield 6 rebuild clean weekly challenge metadata.
This is the strongest fix before reinstalling anything.
Steps:
- Close the game.
- Go to Documents → Battlefield 6 → Settings.
- Delete the Settings folder.
- Relaunch Battlefield 6.
Testing Step:
Open Weekly Challenges—Week 3 should now show the correct 11/11 tally.
Root Cause:
Old config files block the updated weekly-completion metadata from loading.
Did the tally get stuck at 10/11 immediately, or did it change later?
If it froze at 10/11 the moment you finished the last challenge, it’s likely a backend sync failure. This usually happens when the server registers the challenge but the weekly counter fails to update in the same tick.
If it changed later—after switching modes or completing another match—that points to a delayed UI refresh, not a failed completion.
Players often see this when weekly progression is under heavy load after a patch, especially in regions with busy servers.
Are specific challenges completed individually but not counted in the total?
This is the most common pattern. One challenge shows a green checkmark but refuses to add to the weekly total.
Players typically see this with:
- Multi-step objectives
- Mode-specific tasks
- Challenges requiring assists or revives
These challenges can appear completed visually while the backend still flags one sub-step as incomplete.
If a single task shows as done but won’t contribute, it’s almost always a progression sync mismatch, not a user error.
Does restarting the game or switching servers fix the weekly tally?
Sometimes—but not reliably. Restarting forces a fresh fetch of your progression state, which can correct a stale weekly count.
Switching servers (especially to another region) forces the backend to revalidate your profile.
Players report:
- 1 in 3 cases fix after a restart
- Progress sometimes appears correctly after joining a new lobby
If neither works, the tally is stuck server-side and needs a backend refresh from the devs.
Are players in your region reporting the same 10/11 Week 3 bug?
Yes—multiple regions are reporting the exact same Week 3 tally freeze after the patch. NA, EU, Asia, and Oceania players all mention being stuck at 10/11 despite completing everything.
This suggests the issue is not tied to hardware or platform, but a global Week 3 progression bug introduced in the update.
Whenever weekly challenges break across regions at the same time, it almost always points to a backend objective not firing properly.
Did any challenge require multiple steps that might not have registered?
Multi-step challenges are notorious for failing to award the final completion tick. Challenges involving:
- Staged objectives (1/3 → 2/3 → 3/3)
- Damage + kills combos
- Assist-based counters
- Objective captures spread across modes
…can visually show as finished while the backend misses the last increment.
If your 10/11 is caused by one of these, it’s almost certainly a step that registered client-side but failed to save server-side, which is the most common cause of stuck weekly tallies.
