The warehouse behind Windows Update
C:\Windows\SoftwareDistribution is Windows Update's warehouse: every update is downloaded into the Download subfolder first, staged there, and only then handed to the installer. Next to it sits DataStore with DataStore.edb, an ESE database holding your update history — the list you see under View update history. The folder also carries small bookkeeping: SLS with metadata for the update scan, PostRebootEvent with markers for actions that finish after a restart. On a healthy machine it idles at a few hundred megabytes; after a failed feature update or a stuck cumulative patch it can hold 10–20 GB of dead payload. The size itself is not a fault — the trouble starts when the database or the staged files get corrupted and every retry re-downloads the same broken package.
What lives inside, shelf by shelf
Before deleting anything it helps to know which part does what, because half the folder costs you nothing to lose and the other half is genuinely missed. The six residents below are essentially everything you will find in there.
- Download: the update payloads themselves — the heavy part; safe to empty, Windows re-downloads what it needs
- DataStore\DataStore.edb: the update-history database — delete it and the installed-updates list goes blank
- SLS: metadata for the update scan — rebuilt automatically on the next check
- PostRebootEvent: markers for pending post-reboot actions — gone once the restart completes
- tmp: scratch space for in-flight downloads — touch only with the services stopped
- ReportingEvents.log: a plain-text log of update events — small and handy for diagnosis
The safe routine — and when it actually helps
The correct order: stop the Windows Update service and BITS (net stop wuauserv, net stop bits), rename the folder to SoftwareDistribution.old, start the services back up and click Check for updates. Stopping the services is not optional: files held by wuauserv will not delete or rename while it runs. This fixes the classic stuck-update symptoms — errors like 0x80070002, downloads hanging at one percentage forever, updates that install and then offer themselves again. The price is that the update history in Settings goes blank, because you deleted the database that stored it. What it does not fix: slow downloads on a slow line, metered-connection throttling, or Delivery Optimization upload — that is a different cache with its own toggle.
Questions and Answers
Is it safe to delete the SoftwareDistribution folder?
Yes, if the Windows Update service and BITS are stopped first — Windows rebuilds the folder on the next check. You lose only the update history list, nothing else.
Why is SoftwareDistribution taking up so much space?
Usually a failed or half-downloaded feature update left its payload in Download. Emptying the folder with the services stopped reclaims it; a healthy install sits at a few hundred megabytes.
Know what is included before you buy.
The one-time 30-minute trial covers core tools. PRO-labelled features stay locked until a paid license is activated.
Read next
Write to us: [email protected]