Answered by:
CBS.persist.log - Can Delete?
Question
-
Answers
-
Hi,
The SFC.exe program writes the details of each verification operation and of each repair operation to the CBS.log file. The CBS.persist.log is generated when the CBS gets to be around 50 meg in size. CBS.log is copied to cbs.persist.log and a new cbs.log file is started.
It would be useful only for troubleshooting issues. If you are sure your system is running fine, you can delete this file. SFC.exe will create a new one, next time it is run.
Hope this helps.
Regards,
Bruce
- Marked as answer by Bruce-Liu Monday, December 5, 2011 2:22 AM
All replies
-
Hi,
The SFC.exe program writes the details of each verification operation and of each repair operation to the CBS.log file. The CBS.persist.log is generated when the CBS gets to be around 50 meg in size. CBS.log is copied to cbs.persist.log and a new cbs.log file is started.
It would be useful only for troubleshooting issues. If you are sure your system is running fine, you can delete this file. SFC.exe will create a new one, next time it is run.
Hope this helps.
Regards,
Bruce
- Marked as answer by Bruce-Liu Monday, December 5, 2011 2:22 AM
-
I would like to bump this as I am attempting to manage multiple 2008 R2 machines that are quickly running out of disk space. I'm trying to find a way to manage this without having to log into the machine every other day to delete this file.
Is there a setting, registry, or property that I can adjust to have this file deleted or forced to be rolled and compressed? I'm working on getting anything on this but yet have to find any means of management. I really don't want to hack the system by putting a task in to run and delete.http://social.technet.microsoft.com/Forums/windowsserver/en-US/a026dea1-7473-4d82-8521-f3362ebb0a44/cbslog-ballooning?forum=winserverManagement
-
There isn't a way to set the files to delete, no. How much space are the logs consuming on your machine that you need to do this daily?
--Joseph [MSFT] http://blogs.technet.com/b/joscon/
- Proposed as answer by bfleishman_jaydien.com Thursday, September 8, 2016 12:39 PM
-
-
Gotcha, I saw that you're on both threads I replied to this morning. I'm looking into it and hope to have something for you shortly. I don't believe log level is configurable down, only upwards (more verbose). Once I have something I'll reply to the threads for you.
--Joseph [MSFT] http://blogs.technet.com/b/joscon/
-
-
They are growing to a size anywhere between 2-14GB in a days time. Most of these machines I have expanded the disk space to 100GB+ (Origiinally around 50GB) just to slow the amount of times I have to log in and delete.
I am seeing the same thing just start happening recently. On a few of my 2008 R2 servers the cbs.log files grew to 80+GB. I deleted everything in the cbs folder again but they are starting their growth again.- Proposed as answer by mmck98226 Friday, October 31, 2014 1:30 AM
-
I figured this out. I had a relatively new WMI query that was checking on windows updates status. It was set to run too frequently and was filling up my logs.
- Proposed as answer by Defenestrate_MacrosOft Friday, June 10, 2016 8:16 PM
-
Great, I'm glad you found root cause here.
--Joseph [MSFT] http://blogs.technet.com/b/joscon/
- Proposed as answer by vibrant voxel Sunday, October 23, 2016 4:19 PM
- Unproposed as answer by vibrant voxel Sunday, October 23, 2016 4:19 PM
-
-
to delete, you maybe first need to stop the “Windows Module Installer” service
- Proposed as answer by Felipe Feydit Monday, April 6, 2015 6:38 PM
-
How about locking Windows out of the CBS folder?
Simply take ownership and deny all to Everyone.
That's my usual solution to retarded behaviour by Windows.
Like Desktop.ini showing up in the burn folder when I put a RW disk in the drive and giving me the option to commit the change. Kill that burn folder without wasting a second hunting for registry settings that may or may not exist.
-
Instead of completely denying permissions to a folder (which can lead to other problems, like event logs full of errors or outright failures in system processes), you can set it to compressed instead. On this particular folder that cuts the logs down to almost a tenth of their size, so if you have a runaway logging problem at least you don't have to deal with it as often. A scheduled task is another reasonable band-aid.
Most of the Windows folder hierarchy can be set compressed, as long as the kernel and ntfs.sys are untouched.
On topic, I've noticed that mine is also filling up with crap from Windows Updates much more quickly than usual recently, although only ~10 megs a day, not gigs. Gigs a day makes me think WU is probably continually failing and retrying; might be a good idea to rebuild the server if you've already tried troubleshooting WU.
-
-
I have absolutely NO idea why i'm getting this issue after reading this post! xD
im Running Win7 Professional (work PC - wish i could just get a Win10 Enterprise! :'( hehe ) and i've just deleted around 20Gb worth of silly logs...
if my system faults as some1 wrote might happen - then i guess i'll just go ahead and use a Win10 Enterprise TP!
damned be centralized IT departments! :(
anyways - just wanted to poke a thanks by y'all for a very usefull post! :D
-
It looks like extensive log records are generated when there are a significant number of errors, most likely from poor Microsoft updates. I'm not getting an excessive amount of transactions logged when booting the machine. These might be useful if they could all be sent to Microsoft for analysis and corrective action.
-
You actually don't need to reboot. Just stop the "Windows Modules Installer" service, add your userid to the C:\Windows\Logs\CBS folder security with full control, then delete the files, then remove the security again. Restart service. Done.
Info provided as-is without warranties of any kind.
-
-
-
If the WMI process is currently writing to the CBS.log file, you cannot delete it, even if you have permission/ownership of the file. Stopping the service (which probably requires a reboot) is the only option at this point.
In my experience (Windows 7 Pro SP1), disabling the WMI service and rebooting causes the CBS.log file to be compressed (into a dated CbsPersist_yyyymmddhhmmss.cab file), and replaced by a new smaller CBS.log file.
Compressing the directory seems to be the simplest approach. But it does not eliminate the problem.
-
How about have Disk Cleanup utility include these files as well? Or, better yet, let users choose the age of these files for cleanup/deletion, since whatever program creating these files definitely doesn't hold old files anymore. This utility already creates DeepClean.log in this CBS folder.
Then, how about expand this utility to cover all old log files? I just don't understand why it's users' responsibility to manually check and clean these logs known for being obsolete.
-
-
I figured this out. I had a relatively new WMI query that was checking on windows updates status. It was set to run too frequently and was filling up my logs.
After coming here, or whilst, I considered it was related to windows update.
I am going to turn of the auto-update settings, which I had on only because Update would just search and search, and no results.
I wonder how many people with this bloated log have windows update to auto download, and either install auto or decide.
This has never happened to me before, And when it comes to Installing Windows, I have installed it 50+ times just for 7. And I normally never use that setting.
-
-
-
Here's a copy/paste of some research I did a while back when running out of disk space due to cab's in C:\Windows\Temp and CbsPersist's in C:\Windows\Logs\CBS.
----------
It seems a file makecab.exe is trying to zip some CBS log files, but it's unable to, so it creates this cab file instead... every 30 minutes.
Create a scheduled task and put the final switches down where they belong:
cmd.exe /c del C:\Windows\Temp\*cab* /Q
cmd.exe /c del C:\Windows\Logs\CBS\*CbsPersist* /Q-----------
It doesn't fix the illness, but it schedules a good nose-wiping.
- Proposed as answer by Zhongming Yan Friday, June 16, 2017 7:27 AM
-
First of all be sure you have the latest Windows update agent:
https://support.microsoft.com/en-us/kb/949104
Delete everything in the C:\Windows\Temp folder; you may not be able to delete a few files, that's ok. I've also deleted all but the current month of CbsPersist_99999999.log and CbsPersist_99999999.cab files in the C:\Windows\Logs\CBS folder without issue.
-
-
-
-
-
Yes , you can remove its.
CBS basically logs the details of the installing phase & CBS persist is when the CBS gets overloaded.
CBS persist basically has the latest information & removing these files should not matter to the OS.
Note: CBS is used to investigate the installing issue & its not a system critical.
however after deleting there is a new CBS created with latest information.
- Proposed as answer by Mahen1984 Sunday, April 22, 2018 6:18 AM
-
Hello Pen,
No. I believe you cannot reduce the size of it.
there can be multiple CBS persist logs after the overload of the older CBS.
Note: CBS is used to investigate the installing issue & its not a system critical.
There is no point in keeping a 75gb CBS.log file,
Please delete it if you don't need it for any troubleshooting, the machine will create a new one starting with low size .- Proposed as answer by Mahen1984 Sunday, April 22, 2018 6:22 AM