Deciphering The CBS.log

[seekermeister]

I ran SFC a few hours ago, hoping to fix some network corruption. At the end, it said that it did find corruption (somewhere) that it couldn't fix, and referred to the cbs.log for details. That log is cumulative, so the only way to reference SFC results was by day and time, and even with that, the amount of lines involved is massive and cryptic.

Is there a way to see if it has dealt with specific files (network), without needing a computer for a brain?

 

[Casca]

How to analyze the log file entries that the Microsoft Windows Resource Checker (SFC.exe) program generates in Windows Vista

 

[CarlTR6]

Casca, thank your the link. I appreciate it.

 

[whs]

Open an elevated Command Prompt and paste this command into it:

findstr /c:"[SR]" %windir%\logs\cbs\cbs.log

This will show all the files you want to see in the Command Prompt window.
Since that window is not very practical for a detailed study, you want to paste the content into a Notepad, Wordpad or Word file.
For that you right click on the Command Prompt window (any place is good) and click Select All. Then you right click anywhere in the window. Now this whole text is stored on the clipboard and you can paste it into a document file (e.g. Notepad) where you can analyze it.

PS: Just saw that the link that Casca posted proposes a similar solution. Well, now you have 2 ways.

 

[seekermeister]

How to analyze the log file entries that the Microsoft Windows Resource Checker (SFC.exe) program generates in Windows Vista

Thanks for the link, but I'm not certain that it will provide the answer that I'm looking for. First, because for some reason, when I run the string in the Command Prompt, it says that it can't open the log, even though I have closed every other program that might have it locked. It does help to pick out the SFC lines by the SR notation, but even with that, the chore is greater than my old mind can deal with.

I guess that I will need to just try the network again, and see what happens. If it still fails, I'm wondering if there is a way to clean out all network files and start from scratch?

 

[Brink]

In addition to WHS's post, you could also post this command below in to have only the sfc /scannow details placed on your desktop.

findstr /c:"[SR]" %windir%\logs\cbs\cbs.log >%userprofile%\Desktop\sfcdetails.txt


If there were any files listed that could not be fixed by SFC, then you could extract them from your Windows 7 installation disc to replace them with.

http://www.sevenforums.com/tutorials/42776-extract-files-windows-7-installation-dvd.html

Hope this helps,
Shawn

 

[seekermeister]

I have tried changing the properties of CMD, even though I'm logged into the built in administrator account, to change it to run as administrator on the Compatibility tab, but everything on that tab is grayed out, and has a note at the top, that nothing can be changed, because it is part of this version of Windows. I also tried this in Safe Mode with the same results.

Looking at the Permissions for the administrator, the permissions are pretty limited, but trying to change them produces an Access Denied error.

Is it possible to give the Administrator full control of this, like the Trusted Installer has?

 

[Casca]

here...

 

[seekermeister]

here...

Thanks, I was looking on the wrong tab.

 

[seekermeister]

Okay, I've tried the commands again in elevated command prompt, and instead of it saying that it can't open the file, when I run "findstr /c:"[SR]" %windir%\logs\cbs\cbs.log" it does nothing. When I run findstr /c:"[SR]" %windir%\logs\cbs\cbs.log >%userprofile%\Desktop\sfcdetails.txt" it produces a txt file on the desktop, but it is blank.

 

[Brink]

You might go ahead and run the sfc /scannow command again, then run the other command for the log TXT file to see if something shows up in it.

 

[seekermeister]

I can open the cbs.log in EditPad, and it appears normal...just too big to deal with. Would it hurt anything if I deleted the cbs.log altogether, and run SFC again, so that all that it would contain is the SFC entries?

 

[Brink]

Well, the cbs.log will still contain everything and not just the SFC entries. Running the command in the post above in a elevated (run as administrator) command prompt will sift through the cbs.log and produce a txt file on your desktop with only the SFC entries from the cbs.log.

 

[seekermeister]

I finally got refocused on this, and ran SFC /scannow again, and this time the string for culling out the SR entries worked. I just wanted to see if I'm interpreting this correctly?

and Repair transaction
2010-04-30 23:06:53, Info CSI 00000489 [SR] Verify complete
2010-04-30 23:06:54, Info CSI 0000048a [SR] Verifying 100 (0
x0000000000000064) components
2010-04-30 23:06:54, Info CSI 0000048b [SR] Beginning Verify
and Repair transaction
2010-04-30 23:07:18, Info CSI 0000048d [SR] Verify complete
2010-04-30 23:07:19, Info CSI 0000048e [SR] Verifying 100 (0
x0000000000000064) components
2010-04-30 23:07:19, Info CSI 0000048f [SR] Beginning Verify
and Repair transaction
2010-04-30 23:08:02, Info CSI 00000491 [SR] Verify complete
2010-04-30 23:08:04, Info CSI 00000492 [SR] Verifying 100 (0
x0000000000000064) components
2010-04-30 23:08:04, Info CSI 00000493 [SR] Beginning Verify
and Repair transaction
2010-04-30 23:08:14, Info CSI 00000495 [SR] Verify complete
2010-04-30 23:08:15, Info CSI 00000496 [SR] Verifying 100 (0
x0000000000000064) components
2010-04-30 23:08:15, Info CSI 00000497 [SR] Beginning Verify
and Repair transaction
2010-04-30 23:08:24, Info CSI 00000499 [SR] Verify complete
2010-04-30 23:08:25, Info CSI 0000049a [SR] Verifying 100 (0
x0000000000000064) components
2010-04-30 23:08:25, Info CSI 0000049b [SR] Beginning Verify
and Repair transaction
2010-04-30 23:08:27, Info CSI 0000049d [SR] Verify complete
2010-04-30 23:08:28, Info CSI 0000049e [SR] Verifying 100 (0
x0000000000000064) components
2010-04-30 23:08:28, Info CSI 0000049f [SR] Beginning Verify
and Repair transaction
2010-04-30 23:08:33, Info CSI 000004a1 [SR] Verify complete
2010-04-30 23:08:34, Info CSI 000004a2 [SR] Verifying 100 (0
x0000000000000064) components
2010-04-30 23:08:34, Info CSI 000004a3 [SR] Beginning Verify
and Repair transaction
2010-04-30 23:08:40, Info CSI 000004a5 [SR] Verify complete
2010-04-30 23:08:42, Info CSI 000004a6 [SR] Verifying 100 (0
x0000000000000064) components
2010-04-30 23:08:42, Info CSI 000004a7 [SR] Beginning Verify
and Repair transaction
2010-04-30 23:08:52, Info CSI 000004af [SR] Verify complete
2010-04-30 23:08:53, Info CSI 000004b0 [SR] Verifying 100 (0
x0000000000000064) components
2010-04-30 23:08:53, Info CSI 000004b1 [SR] Beginning Verify
and Repair transaction
2010-04-30 23:08:58, Info CSI 000004b3 [SR] Verify complete
2010-04-30 23:08:59, Info CSI 000004b4 [SR] Verifying 100 (0
x0000000000000064) components
2010-04-30 23:08:59, Info CSI 000004b5 [SR] Beginning Verify
and Repair transaction
2010-04-30 23:09:07, Info CSI 000004b7 [SR] Verify complete
2010-04-30 23:09:08, Info CSI 000004b8 [SR] Verifying 100 (0
x0000000000000064) components
2010-04-30 23:09:08, Info CSI 000004b9 [SR] Beginning Verify
and Repair transaction
2010-04-30 23:09:13, Info CSI 000004bb [SR] Verify complete
2010-04-30 23:09:14, Info CSI 000004bc [SR] Verifying 100 (0
x0000000000000064) components
2010-04-30 23:09:14, Info CSI 000004bd [SR] Beginning Verify
and Repair transaction
2010-04-30 23:09:21, Info CSI 000004bf [SR] Verify complete
2010-04-30 23:09:22, Info CSI 000004c0 [SR] Verifying 100 (0
x0000000000000064) components
2010-04-30 23:09:22, Info CSI 000004c1 [SR] Beginning Verify
and Repair transaction
2010-04-30 23:09:32, Info CSI 000004c4 [SR] Verify complete
2010-04-30 23:09:33, Info CSI 000004c5 [SR] Verifying 100 (0
x0000000000000064) components
2010-04-30 23:09:33, Info CSI 000004c6 [SR] Beginning Verify
and Repair transaction
2010-04-30 23:09:40, Info CSI 000004c8 [SR] Verify complete
2010-04-30 23:09:41, Info CSI 000004c9 [SR] Verifying 100 (0
x0000000000000064) components
2010-04-30 23:09:41, Info CSI 000004ca [SR] Beginning Verify
and Repair transaction
2010-04-30 23:09:43, Info CSI 000004cc [SR] Verify complete
2010-04-30 23:09:44, Info CSI 000004cd [SR] Verifying 100 (0
x0000000000000064) components
2010-04-30 23:09:44, Info CSI 000004ce [SR] Beginning Verify
and Repair transaction
2010-04-30 23:09:54, Info CSI 000004d1 [SR] Verify complete
2010-04-30 23:09:55, Info CSI 000004d2 [SR] Verifying 100 (0
x0000000000000064) components
2010-04-30 23:09:55, Info CSI 000004d3 [SR] Beginning Verify
and Repair transaction
2010-04-30 23:10:16, Info CSI 000004d7 [SR] Verify complete
2010-04-30 23:10:17, Info CSI 000004d8 [SR] Verifying 100 (0
x0000000000000064) components
2010-04-30 23:10:17, Info CSI 000004d9 [SR] Beginning Verify
and Repair transaction
2010-04-30 23:10:24, Info CSI 000004de [SR] Verify complete
2010-04-30 23:10:25, Info CSI 000004df [SR] Verifying 100 (0
x0000000000000064) components
2010-04-30 23:10:25, Info CSI 000004e0 [SR] Beginning Verify
and Repair transaction
2010-04-30 23:10:34, Info CSI 000004eb [SR] Verify complete
2010-04-30 23:10:36, Info CSI 000004ec [SR] Verifying 100 (0
x0000000000000064) components
2010-04-30 23:10:36, Info CSI 000004ed [SR] Beginning Verify
and Repair transaction
2010-04-30 23:10:47, Info CSI 000004f4 [SR] Verify complete
2010-04-30 23:10:49, Info CSI 000004f5 [SR] Verifying 100 (0
x0000000000000064) components
2010-04-30 23:10:49, Info CSI 000004f6 [SR] Beginning Verify
and Repair transaction
2010-04-30 23:10:56, Info CSI 000004f8 [SR] Verify complete
2010-04-30 23:10:57, Info CSI 000004f9 [SR] Verifying 100 (0
x0000000000000064) components
2010-04-30 23:10:57, Info CSI 000004fa [SR] Beginning Verify
and Repair transaction
2010-04-30 23:11:05, Info CSI 000004fe [SR] Verify complete
2010-04-30 23:11:06, Info CSI 000004ff [SR] Verifying 100 (0
x0000000000000064) components
2010-04-30 23:11:06, Info CSI 00000500 [SR] Beginning Verify
and Repair transaction
2010-04-30 23:11:12, Info CSI 00000502 [SR] Verify complete
2010-04-30 23:11:14, Info CSI 00000503 [SR] Verifying 100 (0
x0000000000000064) components
2010-04-30 23:11:14, Info CSI 00000504 [SR] Beginning Verify
and Repair transaction
2010-04-30 23:11:24, Info CSI 00000529 [SR] Verify complete
2010-04-30 23:11:26, Info CSI 0000052a [SR] Verifying 100 (0
x0000000000000064) components
2010-04-30 23:11:26, Info CSI 0000052b [SR] Beginning Verify
and Repair transaction
2010-04-30 23:11:34, Info CSI 0000052d [SR] Verify complete
2010-04-30 23:11:35, Info CSI 0000052e [SR] Verifying 100 (0
x0000000000000064) components
2010-04-30 23:11:35, Info CSI 0000052f [SR] Beginning Verify
and Repair transaction
2010-04-30 23:11:42, Info CSI 00000531 [SR] Verify complete
2010-04-30 23:11:43, Info CSI 00000532 [SR] Verifying 100 (0
x0000000000000064) components
2010-04-30 23:11:43, Info CSI 00000533 [SR] Beginning Verify
and Repair transaction
2010-04-30 23:11:50, Info CSI 00000535 [SR] Verify complete
2010-04-30 23:11:51, Info CSI 00000536 [SR] Verifying 100 (0
x0000000000000064) components
2010-04-30 23:11:51, Info CSI 00000537 [SR] Beginning Verify
and Repair transaction
2010-04-30 23:11:57, Info CSI 00000545 [SR] Verify complete
2010-04-30 23:11:58, Info CSI 00000546 [SR] Verifying 100 (0
x0000000000000064) components
2010-04-30 23:11:58, Info CSI 00000547 [SR] Beginning Verify
and Repair transaction
2010-04-30 23:12:09, Info CSI 00000549 [SR] Verify complete
2010-04-30 23:12:10, Info CSI 0000054a [SR] Verifying 100 (0
x0000000000000064) components
2010-04-30 23:12:10, Info CSI 0000054b [SR] Beginning Verify
and Repair transaction
2010-04-30 23:12:19, Info CSI 00000559 [SR] Verify complete
2010-04-30 23:12:20, Info CSI 0000055a [SR] Verifying 100 (0
x0000000000000064) components
2010-04-30 23:12:20, Info CSI 0000055b [SR] Beginning Verify
and Repair transaction
2010-04-30 23:12:23, Info CSI 0000055d [SR] Verify complete
2010-04-30 23:12:24, Info CSI 0000055e [SR] Verifying 100 (0
x0000000000000064) components
2010-04-30 23:12:24, Info CSI 0000055f [SR] Beginning Verify
and Repair transaction
2010-04-30 23:12:29, Info CSI 00000561 [SR] Verify complete
2010-04-30 23:12:31, Info CSI 00000562 [SR] Verifying 100 (0
x0000000000000064) components
2010-04-30 23:12:31, Info CSI 00000563 [SR] Beginning Verify
and Repair transaction
2010-04-30 23:12:37, Info CSI 00000565 [SR] Verify complete
2010-04-30 23:12:39, Info CSI 00000566 [SR] Verifying 100 (0
x0000000000000064) components
2010-04-30 23:12:39, Info CSI 00000567 [SR] Beginning Verify
and Repair transaction
2010-04-30 23:12:41, Info CSI 00000569 [SR] Verify complete
2010-04-30 23:12:42, Info CSI 0000056a [SR] Verifying 100 (0
x0000000000000064) components
2010-04-30 23:12:42, Info CSI 0000056b [SR] Beginning Verify
and Repair transaction
2010-04-30 23:12:53, Info CSI 0000056d [SR] Verify complete
2010-04-30 23:12:55, Info CSI 0000056e [SR] Verifying 100 (0
x0000000000000064) components
2010-04-30 23:12:55, Info CSI 0000056f [SR] Beginning Verify
and Repair transaction
2010-04-30 23:13:02, Info CSI 00000571 [SR] Verify complete
2010-04-30 23:13:03, Info CSI 00000572 [SR] Verifying 100 (0
x0000000000000064) components
2010-04-30 23:13:03, Info CSI 00000573 [SR] Beginning Verify
and Repair transaction
2010-04-30 23:13:16, Info CSI 00000587 [SR] Verify complete
2010-04-30 23:13:17, Info CSI 00000588 [SR] Verifying 100 (0
x0000000000000064) components
2010-04-30 23:13:17, Info CSI 00000589 [SR] Beginning Verify
and Repair transaction
2010-04-30 23:13:25, Info CSI 00000591 [SR] Verify complete
2010-04-30 23:13:26, Info CSI 00000592 [SR] Verifying 100 (0
x0000000000000064) components
2010-04-30 23:13:26, Info CSI 00000593 [SR] Beginning Verify
and Repair transaction
2010-04-30 23:14:02, Info CSI 00000595 [SR] Verify complete
2010-04-30 23:14:04, Info CSI 00000596 [SR] Verifying 100 (0
x0000000000000064) components
2010-04-30 23:14:04, Info CSI 00000597 [SR] Beginning Verify
and Repair transaction
2010-04-30 23:14:10, Info CSI 00000599 [SR] Verify complete
2010-04-30 23:14:11, Info CSI 0000059a [SR] Verifying 100 (0
x0000000000000064) components
2010-04-30 23:14:11, Info CSI 0000059b [SR] Beginning Verify
and Repair transaction
2010-04-30 23:14:16, Info CSI 0000059f [SR] Verify complete
2010-04-30 23:14:17, Info CSI 000005a0 [SR] Verifying 100 (0
x0000000000000064) components
2010-04-30 23:14:17, Info CSI 000005a1 [SR] Beginning Verify
and Repair transaction
2010-04-30 23:14:23, Info CSI 000005a3 [SR] Verify complete
2010-04-30 23:14:24, Info CSI 000005a4 [SR] Verifying 100 (0
x0000000000000064) components
2010-04-30 23:14:24, Info CSI 000005a5 [SR] Beginning Verify
and Repair transaction
2010-04-30 23:14:32, Info CSI 000005a7 [SR] Verify complete
2010-04-30 23:14:33, Info CSI 000005a8 [SR] Verifying 100 (0
x0000000000000064) components
2010-04-30 23:14:33, Info CSI 000005a9 [SR] Beginning Verify
and Repair transaction
2010-04-30 23:14:38, Info CSI 000005ab [SR] Verify complete
2010-04-30 23:14:40, Info CSI 000005ac [SR] Verifying 100 (0
x0000000000000064) components
2010-04-30 23:14:40, Info CSI 000005ad [SR] Beginning Verify
and Repair transaction
2010-04-30 23:14:46, Info CSI 000005b0 [SR] Verify complete
2010-04-30 23:14:47, Info CSI 000005b1 [SR] Verifying 100 (0
x0000000000000064) components
2010-04-30 23:14:47, Info CSI 000005b2 [SR] Beginning Verify
and Repair transaction
2010-04-30 23:14:52, Info CSI 000005b4 [SR] Verify complete
2010-04-30 23:14:54, Info CSI 000005b5 [SR] Verifying 100 (0
x0000000000000064) components
2010-04-30 23:14:54, Info CSI 000005b6 [SR] Beginning Verify
and Repair transaction
2010-04-30 23:15:00, Info CSI 000005b8 [SR] Verify complete
2010-04-30 23:15:02, Info CSI 000005b9 [SR] Verifying 100 (0
x0000000000000064) components
2010-04-30 23:15:02, Info CSI 000005ba [SR] Beginning Verify
and Repair transaction
2010-04-30 23:15:09, Info CSI 000005bc [SR] Verify complete
2010-04-30 23:15:10, Info CSI 000005bd [SR] Verifying 100 (0
x0000000000000064) components
2010-04-30 23:15:10, Info CSI 000005be [SR] Beginning Verify
and Repair transaction
2010-04-30 23:15:18, Info CSI 000005c1 [SR] Verify complete
2010-04-30 23:15:19, Info CSI 000005c2 [SR] Verifying 100 (0
x0000000000000064) components
2010-04-30 23:15:19, Info CSI 000005c3 [SR] Beginning Verify
and Repair transaction
2010-04-30 23:15:24, Info CSI 000005c5 [SR] Verify complete
2010-04-30 23:15:25, Info CSI 000005c6 [SR] Verifying 100 (0
x0000000000000064) components
2010-04-30 23:15:25, Info CSI 000005c7 [SR] Beginning Verify
and Repair transaction
2010-04-30 23:15:33, Info CSI 000005c9 [SR] Verify complete
2010-04-30 23:15:34, Info CSI 000005ca [SR] Verifying 100 (0
x0000000000000064) components
2010-04-30 23:15:34, Info CSI 000005cb [SR] Beginning Verify
and Repair transaction
2010-04-30 23:15:42, Info CSI 000005cd [SR] Verify complete
2010-04-30 23:15:43, Info CSI 000005ce [SR] Verifying 100 (0
x0000000000000064) components
2010-04-30 23:15:43, Info CSI 000005cf [SR] Beginning Verify
and Repair transaction
2010-04-30 23:15:51, Info CSI 000005d1 [SR] Verify complete
2010-04-30 23:15:52, Info CSI 000005d2 [SR] Verifying 21 (0x
0000000000000015) components
2010-04-30 23:15:52, Info CSI 000005d3 [SR] Beginning Verify
and Repair transaction
2010-04-30 23:15:53, Info CSI 000005d5 [SR] Verify complete
2010-04-30 23:15:53, Info CSI 000005d6 [SR] Repairing 1 comp
onents
2010-04-30 23:15:53, Info CSI 000005d7 [SR] Beginning Verify
and Repair transaction
2010-04-30 23:15:53, Info CSI 000005d9 [SR] Cannot repair me
mber file [l:16{8}]"uDWM.dll" of Microsoft-Windows-DesktopWindowManager-uDWM, Ve
rsion = 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
2010-04-30 23:15:53, Info CSI 000005db [SR] Cannot repair me
mber file [l:16{8}]"uDWM.dll" of Microsoft-Windows-DesktopWindowManager-uDWM, Ve
rsion = 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
2010-04-30 23:15:53, Info CSI 000005dc [SR] This component w
as referenced by [l:190{95}]"Microsoft-Windows-DesktopWindowManager-uDWM-Package
~31bf3856ad364e35~amd64~~6.1.7600.16385.uDWM"
2010-04-30 23:15:53, Info CSI 000005df [SR] Could not reproj
ect corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:16{8}]"uDW
M.dll"; source file in store is also corrupted
2010-04-30 23:15:53, Info CSI 000005e1 [SR] Repair complete
2010-04-30 23:15:53, Info CSI 000005e2 [SR] Committing trans
action
2010-04-30 23:15:53, Info CSI 000005e6 [SR] Verify and Repai
r Transaction completed. All files and registry keys listed in this transaction
have been successfully repaired

It appears that the only unfixed problem is with the uDWM.dll...right? This wouldn't have anything to do with network corruption...would it?

EDIT:
The last line in the results makes it sound as though there are NO unrepaired problems, which seems to contradict the original report when running sfc /scannow.

 

[Brink]

That would be correct.

The uDWM.dll file is for the Microsoft Desktop Window Manager. It wouldn't hurt anything to extract this file from your Windows 7 installation disc to replace it with to see if it may have been a part of the problem.

Extract Files from Windows 7 Installation DVD

 

[seekermeister]

Hmm, even though it shows that I have full control, and I also used Takeownership on the file currentlly in System32, when I try to copy the extracted file there, it says that it can't delete the original.

 

[seekermeister]

Returning to the original issue, when I attempt to use the router's wizard to setup the internet settings, it always says that there is a network problem and aborts. Viewing the network setting in the router's manual settings, all looks okay to me, but since I know so little about this, that doesn't mean much.

When I view the Network Map in Network And Sharing Center, it shows the connection to the gateway as being okay, but the connection to the internet is red Xed, and though it shows my secondary rig as being discovered, it says that it can't add it to the Network Map. The more that I dig, the deeper that I get, and the less light that I see. I really want to fix this issue, without having to reinstall the entire OS, otherwise all that I have spent to equip the secondary rig for the purpose of streaming media will have been for naught. I really hope that someone can spare at least a match.

 

[Gary Wiley]

I have a similar problem, which was caused from a crashed update of Windows 7 Home Premium 64. I have followed the procedures outlined in this thread.

My sfcdetails.txt file shows over 350 files with a hash mismatches. I have tried Windows start up repair, but it shows no problems.

I have 3 Windows 7 64 computers, but no Windows 7 install disk. I have 3 useless restore disks.

It appears that I need to purchase a Windows 7 install disk, but I am unsure which one to purchase, Windows 7 OEM or Upgrade.

All I want is the ability to do an install repair on my system.

Gary

 

[Brink]

Hello Gary, and welcome to Seven Forums.

To do a repair install, you will need a retail (Full or Upgrade) copy of Windows 7 and not a OEM copy.

Hope this helps,
Shawn

 

[Tepid]

Hmm, even though it shows that I have full control, and I also used Takeownership on the file currentlly in System32, when I try to copy the extracted file there, it says that it can't delete the original.

That is because the file may be in use (most likely is) and may need to attempt replacing through safe mode. Or even something like UBCD or BartPE.