CBS.log file corrupt

[Mindslaver]

Hello everyone,

I have the same issue that I have read on different forum posts concerning a CBS.log file corrupt after running sfc /scannow in an elevated cmd.exe. This is the first time this has happened, and happened recently within the past few days (seemingly following a recent windows update from what I can tell). I have read the other threads on this site to try and figure it out for myself, but to no avail. Attached should be the most recent CBS.log zip file. If I did it wrong let me know! Also, I have attached a dxdiag.txt file to look over all the specs on my PC. Thanks in advance for any help.

Regards,

Stephen

 

[Mindslaver]

Update time!

Alright, I did some digging in my cbs.log file to find the exact root of the problem. I found the files and googled them, and came across Niemiro's sfcfix.exe. I used it and voila! Fixed! The file in question were
C:\Windows\winsxs\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18839_none_fe0845bb1d97efda\utc.app.json and
C:\Windows\winsxs\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18839_none_fe0845bb1d97efda\telemetry.ASM-WindowsDefault.json

Followed by a recent Optional Windows Update. Which I believe to be (KB3022345). Which caused the corrupt files. If you are having the same issues I definitely recommend https://www.sysnative.com/forums/downloads/sfcfix/

Thanks again Sysnative! and Niemiro!

Regards,

Stephen

 

[Go The Power]

Hello and welcome

Glad to hear you have resolved the issue :) We have a thread on this corruption here:
https://www.sysnative.com/forums/windows-update/14163-guide-kb3022345-causing-corrupt-files.html