Please Help Interpret CBS.log File

FVS

New Member
#1
I ran a sfc /scannow at an Elevated Command Prompt and got the message that there were some corrupted files that it could not fix, to check the CBS.log file. I converted the file to a .text file and have attached it to this post. I have no idea how to interpret this file. I would really appreciate if someone would read the information and give me some advise as to how to proceed further. Thanks so very much in advance!
 


Attachments

Saltgrass

Excellent Member
Microsoft Community Contributor
#2
It looks like tcpmon.in is having the problem. The link below will show how to replace it if you have a copy. The listing show which Windows Package the file was part of, with might be an update.

A good source for files is other computers or image backups. There may be others, but there should be at least two on your system, but the listing also notes the backup is corrupted also. Anyway, something about the file does not pass the test.

2013-01-20 12:39:34, Info CSI 00000139 [SR] Cannot repair member file [l:20{10}]"tcpmon.ini" of Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

2013-01-20 12:39:37, Info CSI 0000013b [SR] Cannot repair member file [l:20{10}]"tcpmon.ini" of Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

2013-01-20 12:39:37, Info CSI 0000013c [SR] This component was referenced by [l:202{101}]"Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.WindowsFoundationDelivery"

2013-01-20 12:39:37, Info CSI 0000013f [SR] Could not reproject corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:20{10}]"tcpmon.ini"; source file in store is also corrupted
Use the System File Checker tool to troubleshoot missing or corrupted system files on Windows Vista or on Windows 7

If you have an OEM machine, the OEM may have altered the file, which might keep it from checking correctly..
 


Last edited:

FVS

New Member
#3
Thanks so much for taking the time to review my post!! I will see what I can do with the information you posted.
 


This website is not affiliated, owned, or endorsed by Microsoft Corporation. It is a member of the Microsoft Partner Program.