Problem: Battle.net Call of Duty Season 01 Reloaded “175GB+ download / stuck preload / redownloads whole game” (few clear fixes)

Published: 2026-01-20 00:00 (local time)

Quick Summary

Many Battle.net players trying to preload or update Call of Duty: Black Ops 7 / Warzone report a gigantic download (often ~175GB) that looks like a full reinstall.
Some users report the preload disappearing mid-download, getting stuck, or looping into repeated “update” behavior.
Activision acknowledged an issue causing “unusually large download sizes” and temporarily disabled Battle.net preloading while a fix was in progress.
Because installs vary by which modes/packs you have (MP, Zombies, Warzone, High-Res assets), there’s no single fix that works for everyone.
Workarounds focus on (1) letting the corrected update re-check files, (2) repairing Battle.net + the game install, and (3) preventing storage/network interruptions.

What’s happening

In early January 2026, a widespread issue hit Battle.net users preparing for the Season 01 Reloaded update for Call of Duty: Black Ops 7 and Call of Duty: Warzone. Players reported Battle.net offering an abnormally large preload—commonly around 175GB—creating the impression that the launcher was forcing a full redownload of the game. Reports also describe the update getting stuck part-way, pausing indefinitely, or vanishing entirely from the launcher after partial progress.

This wasn’t just “Call of Duty updates are big.” Activision’s public messaging (as relayed by multiple outlets) stated Battle.net preloading was disabled due to an issue causing “unusually large download sizes,” and that the expected size should be far smaller (commonly reported as ~20–30GB depending on installed content). Players were told that when the corrected download became available, progress should appear “mostly complete” because Battle.net would re-use the already-downloaded data where possible.

Who’s affected: primarily PC players updating via Battle.net (notably those with multiple content packs installed). The pain is amplified for players with limited SSD space, slower/unstable connections, or data caps—because a 175GB “oops” download can be functionally unplayable to retry.

Likely causes (what research suggests)

A Battle.net preload sizing/packaging error: Activision indicated the large download sizes were unintended and disabled preloading while addressing the issue, suggesting a packaging or manifest problem rather than normal patch growth.
Content-pack variance: Call of Duty installs are modular (Warzone-only vs. full install; optional assets). That can change what Battle.net thinks you “need,” and can turn a small update into a large replacement download when something mismatches.
Interrupted or partially applied preload data: Users on Blizzard’s forums and Reddit describe preloads stopping around mid-progress, then disappearing—consistent with Battle.net removing/withdrawing the faulty preload and leaving players with partial data that must be validated later.
Disk space + file validation behavior: When space runs low or files can’t be written cleanly, Battle.net may loop into “repair/update” states that look like an endless redownload.

Solutions & Workarounds

1) Wait for (and trigger) the corrected Battle.net update, then force a file re-check

Who it helps: Battle.net PC players who saw the 175GB preload, partial preload, or a vanished preload.

Step-by-step:
- Close the game completely.
- Fully exit Battle.net (use the system tray icon to quit, not just the window X).
- Reopen Battle.net and check for an update again.
- If available, start the update and let it run; if it “jumps” quickly to near-complete, that’s expected behavior per reports of progress being mostly complete after the fix.
Risks/tradeoffs: Still may download a lot if your installed packs are mismatched; could take hours on slower connections.
Stop and contact official support when: The update repeatedly resets to 0% after multiple relaunches, or Battle.net shows persistent install errors.

2) Run “Scan and Repair” on the game (after any withdrawn preload)

Who it helps: Players stuck in odd states after the preload was disabled/withdrawn, or who suspect corrupted/partial data.

Step-by-step:
- In Battle.net, select Call of Duty (Black Ops 7 / Warzone entry).
- Open the options menu (gear icon) and choose Scan and Repair.
- Let it complete, then try updating again.
Risks/tradeoffs: Scan/Repair can take a long time and may still lead to a large download if it decides local data is unusable.
Stop and contact official support when: Scan/Repair fails with repeated errors, or completes but the launcher still insists on reinstalling every time.

3) Ensure you have enough free space (more than you think) and avoid “near-full SSD” behavior

Who it helps: Anyone hitting stuck downloads, repeated verification, or patch-apply failures.

Step-by-step:
- Check your install drive’s free space.
- Temporarily free a large buffer (many players aim for 100GB+ during major CoD updates; more if you have multiple packs installed).
- Reboot your PC (clears locked files), then retry the update.
Risks/tradeoffs: You may need to uninstall other games/apps temporarily; moving the install between drives can also trigger revalidation downloads.
Stop and contact official support when: You have ample free space and the launcher still errors at the same point every time.

4) Temporarily disable bandwidth limits and “sleep” interruptions (Battle.net + Windows)

Who it helps: Players with updates pausing, slowing to zero, or failing overnight.

Step-by-step:
- In Battle.net settings, remove/raise any download throttles while updating.
- In Windows Power & Battery settings, prevent sleep while plugged in during the download.
- If using Wi‑Fi, consider a wired connection for the update window.
Risks/tradeoffs: Higher bandwidth use on your network; may impact others at home.
Stop and contact official support when: Downloads fail even on a stable wired connection and no throttles.

5) As a last resort: clean reinstall (only after you’ve tried repair + re-check)

Who it helps: Players in a persistent loop where Battle.net can’t reconcile the install.

Step-by-step:
- Back up any important local settings if applicable.
- Uninstall Call of Duty from Battle.net.
- Reboot PC.
- Reinstall, then install only the modes you actually play (e.g., avoid extra packs if you don’t need them).
Risks/tradeoffs: Time-consuming and data-heavy; worst option for data caps.
Stop and contact official support when: A fresh install still produces the same abnormal download/loop behavior (suggesting an account/launcher-side issue).

Prevention (so it doesn’t come back)

Keep a large free-space buffer on the drive where Call of Duty is installed, especially around seasonal updates.
Install only the content packs you use (Warzone-only vs full MP/Zombies), to reduce mismatch and patch size exposure.
Avoid pausing/resuming giant updates repeatedly; if you must stop, fully exit Battle.net and resume later.
Schedule major downloads when your connection is stable (avoid peak hours if your ISP is congested).

FAQ

Q: Is the 175GB download “normal” for Season 01 Reloaded?
A: Reporting indicates it was not intended on Battle.net; Activision messaging described it as an issue causing unusually large download sizes and disabled preloading while addressing it.

Q: Why did my preload disappear in Battle.net?
A: Users reported the preload being pulled/disabled, which can make the launcher stop showing it until the corrected update is released.

Q: If I already downloaded part of the huge preload, is it wasted?
A: Not always. Reports indicated the corrected update might start “mostly complete,” implying Battle.net may re-use previously downloaded data where possible.

Q: Should I delete folders to save space?
A: Avoid manual deletion unless you’re doing a full reinstall. Deleting the wrong data can force even larger re-downloads or break the install.

Q: Does this affect Steam players the same way?
A: The widespread reports and the specific “disabled preloading” messaging center on Battle.net’s preload behavior.

Q: When should I contact support?
A: If Scan/Repair fails repeatedly, the update constantly resets, or a clean reinstall still loops, it’s time to contact official support with your Battle.net logs and error details.