What CBS.log is and why it balloons
CBS stands for Component-Based Servicing — the Windows subsystem that installs updates, enables features and runs System File Checker repairs. Every one of those operations is journaled into C:\Windows\Logs\CBS\CBS.log, which is why the file exists and grows a little after each update session. Periodically, Windows archives the current log into pairs of files named CbsPersist_<date and time>.cab and .log, and these archives are supposed to be pruned automatically after a while.
The system works until something breaks: when an update fails and retries in a loop — a stuck TiWorker or TrustedInstaller is the usual suspect — the log and its archives grow with every attempt. On machines that failed the same update for months, CBS folders have been observed near the terabyte mark. A CBS folder measured in gigabytes is therefore not just disk noise: it is usually the fingerprint of an update problem worth fixing.
Deleting the CBS logs safely
The golden rule is timing: do the cleanup while no update is installing. Check first — Settings → Windows Update should show no download or install in progress, and a reboot right before the cleanup is the cleanest starting point. The current CBS.log is held open by the TrustedInstaller service, so expect “file in use” on it; the CbsPersist archives are almost always free to delete.
The practical sequence from an elevated command prompt:
- net stop wuauserv — stops the update service so nothing writes into the log mid-delete
- net stop TrustedInstaller — releases the current CBS.log (safe to stop; it restarts on demand)
- del /f /q C:\Windows\Logs\CBS\CbsPersist_* — removes the archived .cab and .log files
- del /f /q C:\Windows\Logs\CBS\CBS.log — clears the current log; Windows recreates it on the next servicing event
- net start wuauserv — brings the update service back (TrustedInstaller starts on its own when needed)
Keeping the CBS folder from ballooning again
On a healthy system you rarely need to touch this folder again: Windows rotates and prunes the logs itself. If CBS.log rockets back to gigabytes within weeks, the real fix is repairing Windows Update — run the built-in troubleshooter, then DISM /Online /Cleanup-Image /RestoreHealth and sfc /scannow, so the failing component finally installs and the retry loop ends. In stubborn cases, stopping and restarting the services or the classic reset of Windows Update components does the job.
Because Disk Cleanup and Storage Sense ignore C:\Windows\Logs\CBS entirely, it remains a classic blind spot of manual housekeeping. Kleaner PRO treats Windows log folders — CBS and its siblings like DISM and WindowsUpdate — as a first-class junk category: the scanner shows the current size, deletes the archives safely and schedules the locked CBS.log for removal on the next reboot.
Questions and Answers
Is it safe to delete CBS.log?
Yes, as long as no update is installing. The file is a plain text journal; Windows recreates it from scratch the next time servicing runs. Deleting it does not affect updates themselves.
Why is my CBS.log so large?
Repeated failed update attempts keep appending to the log — a stuck TrustedInstaller or TiWorker process is the usual culprit. Deleting the log frees space, but the update problem is what needs fixing.
Can I delete CbsPersist files?
Yes. CbsPersist_*.cab and .log are compressed archives of old logs; once written, they are never needed again. They are the first thing to remove when the CBS folder grows.
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]