PowerEdge: Windows CBS logs taking up too much disk space due to compression failures

Summary: The log files in the %systemroot%\Logs\CBS folder should be automatically compressed into .cab files when they reach a certain size. If this compression fails, the logs can grow large. Further, the failure of the compression utility causes other large log files to be generated, resulting in a large amount of disk-space consumption. ...

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.

Symptoms

  • Large, uncompressed log files in the %systemroot%\Logs\CBS folder
    • There is a single CBS.log file, plus one or more files with names in the CbsPersist_datetime.log format.
  • One or more large .cab files in the %systemroot%\Temp folder

Cause

Component-Based Servicing logs its activity in the %systemroot%\Logs\CBS folder. These files contain entries which are useful when troubleshooting issues with Windows Update or adding roles and features, as well they document what corrupt files, if any, are found and replaced by the System File Checker (SFC) and Dism cleanup processes.

The active log is named CBS.log. When it reaches a certain size, it is renamed to CbsPersist_datetime.log, then compressed into a .cab file of the same name. Sometimes, however, the CBS.log file's size increases rapidly, and the integrated compression utility (makecab.exe) is unable to compress it as a result.

Though this situation is rare, when it does happen, it causes disk space to be consumed rapidly. This is because makecab.exe repeatedly attempts to compress the file, fails to do so, and then tries again shortly thereafter. Each time this happens, it generates a large log file of its own (with a .cab extension) in the %systemroot%\Temp folder.

Resolution

To fix the issue, perform the following steps:

  1. Stop the Windows Modules Installer service using any of these methods:
    • Launch the Services console, right-click the Windows Modules Installer service, and select Stop.
    • In PowerShell, run stop-service TrustedInstaller
    • At a command prompt, run net stop TrustedInstaller.
  2. Launch File Explorer and browse to %systemroot%\Logs\CBS.
  3. Delete or rename all files in this folder. Do not delete the folder itself.
  4. Browse to %systemroot%\Temp.
  5. Delete all files in this folder that have a .cab extension.
  6. Reboot the affected server.

Affected Products

Microsoft Windows Server 2016, Microsoft Windows Server 2019, Microsoft Windows Server 2022, Microsoft Windows 2012 Server, Microsoft Windows 2012 Server R2, OEMR R440, OEMR R450, OEMR R540, OEMR R550, OEMR R5500, OEMR R640, OEMR R6415, OEMR R650 , OEMR R650xs, OEMR R6515, OEMR R6525, OEMR R660, OEMR R660xs, OEMR R6615, OEMR R6625, OEMR R740, OEMR R740xd, OEMR R740xd2, OEMR R7415, OEMR R7425, OEMR R750, OEMR R750xa, OEMR R750xs, OEMR R7515, OEMR R7525, OEMR R760, OEMR R760xa, OEMR R760XD2, OEMR R760xs, OEMR R7615, OEMR R7625, OEMR R840, OEMR R860, OEMR R940, OEMR R940xa, OEMR R960, OEMR XR4510c, OEMR XR4520c, OEMR XR5610, OEMR XR8610t, OEMR XR8620t, PowerEdge R440, PowerEdge R450, PowerEdge R540, PowerEdge R550, PowerEdge R640, PowerEdge R6415, PowerEdge R650, PowerEdge R650xs, PowerEdge R6515, PowerEdge R6525, PowerEdge R660, PowerEdge R660xs, PowerEdge R6615, PowerEdge R6625, PowerEdge R740, PowerEdge R740XD, PowerEdge R740XD2, PowerEdge R7415, PowerEdge R7425, PowerEdge R750, PowerEdge R750XA, PowerEdge R750xs, PowerEdge R7515, PowerEdge R7525, PowerEdge R760, PowerEdge R760XA, PowerEdge R760xd2, PowerEdge R760xs, PowerEdge R7615, PowerEdge R7625, PowerEdge R840, PowerEdge R860, PowerEdge R940, PowerEdge R940xa, PowerEdge R960, PowerEdge XR4510c, PowerEdge XR4520c, PowerEdge XR5610, PowerEdge XR8610t, PowerEdge XR8620t ...
Article Properties
Article Number: 000201058
Article Type: Solution
Last Modified: 16 Jul 2025
Version:  4
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.