Battle.net Cleanup: Old Agent Folders, agent.log and Setup Leftovers

What Battle.net leaves on disk

The Agent is Battle.net's updater daemon, and it lives in %ProgramData%\Battle.net\Agent — in numbered folders like agent.8064, one per updater build. Every launcher update leaves the previous folder behind, so five years of Battle.net means a graveyard of dead Agents. The same folder holds agent.log, a verbose text log that keeps appending for years and is a known quiet grower — given long enough, that one file reaches hundreds of megabytes on its own.

Two caches feed the launcher's Chromium interface: %LocalAppData%\Battle.net\BrowserCache, the browser cache of the store UI, and %ProgramData%\Blizzard Entertainment\Battle.net\Cache, the launcher-side cache. %ProgramData%\Battle.net\Setup stores the update payloads the launcher downloads — archives that stay on disk after the update is installed. Add the Battle.net-Setup.exe that has been sitting in your Downloads folder since install day, and the full picture is five distinct kinds of leftovers.

• %ProgramData%\Battle.net\Agent\agent.XXXX — numbered updater builds; everything except the newest is deletable junk
• %ProgramData%\Battle.net\Agent\agent.log — the updater's log; grows for years, safe to delete with Battle.net closed
• %ProgramData%\Battle.net\Setup — downloaded update payloads; safe to empty once the update is installed
• %LocalAppData%\Battle.net\BrowserCache — Chromium cache of the store UI; the standard fix for a blank or frozen shop
• %ProgramData%\Blizzard Entertainment\Battle.net\Cache — launcher-side cache; rebuilds on the next start
• Battle.net-Setup.exe in Downloads — the installer you ran once; archive it or delete it

The cleanup order that works

Close Battle.net completely first — including the tray icon — and check Task Manager for Agent.exe, because the updater keeps running after the launcher window closes. Then delete the old agent.* folders, keeping the one with the highest number, remove agent.log, and empty Setup. None of this touches your games or their saves: Blizzard saves live server-side or inside the game folders, and the launcher re-creates whatever it misses on the next start.

BrowserCache and Cache rebuild at the next launch, and you stay signed in, because account data lives elsewhere. Deleting BrowserCache is also the standard first fix when the shop renders blank or the launcher hangs on "Connecting" after an update — a corrupted Chromium profile is the usual culprit, the same pattern as Teams or Spotify. Kleaner PRO does this whole Battle.net category in one pass — old Agent builds, logs, caches and leftover installers — which is worth it if you would rather not repeat the ritual by hand every few months.

Questions and Answers

Read next