BleepingComputer.com: Corrupt files

I performed a sfc /scannow to see if anything thing was wrong and it said that it found some corrupted files
but was unable to fix some of them, I looked in c:\windows\logs\cbs\.... and it was a huge log
When I checked the log I found it confusing but I think I made out that a few of the files that could not be fixed where called "hosts winsock inferstracture..... " or something along those lines.
I performed the scan again and then got the message "Windows Resource Protection did not find any integrity violations" and no log I think was generated.

Is this anything to worry about?, I looked on MS help and it said corrupt files were rare... well I seemed to have alot!
Were all the files fixed seeing as it could not find anything on the second scan?

Quote

I would say that as long as you are able to get online, I wouldn't worry about
A more complete error message would be nice to have

POQ 73 ends.
2009-08-08 14:16:26, Info CSI 00000188 [SR] Verify complete
2009-08-08 14:16:26, Info CSI 00000189 [SR] Repairing 1 components
2009-08-08 14:16:26, Info CSI 0000018a [SR] Beginning Verify and Repair transaction
2009-08-08 14:16:26, Info CSI 0000018b [SR] Cannot repair member file [l:10{5}]"hosts" of Microsoft-Windows-Winsock-Core-Infrastructure-other, Version = 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2009-08-08 14:16:26, Info CSI 0000018c [SR] Repaired file \SystemRoot\WinSxS\Manifests\\[ml:26{13},l:10{5}]"hosts" by copying from backup
2009-08-08 14:16:26, Info CSI 0000018d Repair results created:
POQ 74 starts:
0: Create File: File = [l:246{123}]"\SystemRoot\WinSxS\x86_microsoft-windows-w..nfrastructure-other_31bf3856ad364e35_6.0.6000.16386_none_024e4071fa6fea95\hosts", Attributes = 00000080
1: Move File: Source = [l:154{77}]"\SystemRoot\WinSxS\Temp\PendingRenames\7ac44e6f2a18ca01c71f0000d4041407.hosts", Destination = [l:246{123}]"\SystemRoot\WinSxS\x86_microsoft-windows-w..nfrastructure-other_31bf3856ad364e35_6.0.6000.16386_none_024e4071fa6fea95\hosts"

and this one

POQ 61 ends.
2009-08-08 14:14:13, Info CSI 0000014b [SR] Verify complete
2009-08-08 14:14:13, Info CSI 0000014c [SR] Verifying 100 (0x00000064) components
2009-08-08 14:14:13, Info CSI 0000014d [SR] Beginning Verify and Repair transaction
2009-08-08 14:14:19, Info CSI 0000014e [SR] Cannot repair member file [l:10{5}]"hosts" of Microsoft-Windows-Winsock-Core-Infrastructure-other, Version = 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2009-08-08 14:14:22, Info CSI 0000014f [SR] Repaired file \SystemRoot\WinSxS\Manifests\\[ml:26{13},l:10{5}]"hosts" by copying from backup
2009-08-08 14:14:23, Info CSI 00000150 Ignoring duplicate ownership for directory [l:54{27}]"\??\C:\Windows\System32\WCN" in component Microsoft-Windows-WCN-Config-Registrar-Wizard2.Resources, Version = 6.1.6002.18005, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral

2009-08-08 14:14:23, Info CSI 00000151 Ignoring duplicate ownership for directory [l:66{33}]"\??\C:\Windows\System32\WCN\en-US" in component Microsoft-Windows-WCN-Config-Registrar-Wizard2.Resources, Version = 6.1.6002.18005, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral

something here as well

09-07-29 14:19:40, Info CSI 0000005d ICSITransaction::Commit calling IStorePendingTransaction::Apply - coldpatching=FALSE applyflags=15 (0x0000000f)
2009-07-29 14:19:40, Info CSI 0000005e Creating NT transaction (seq 7), objectname [6]"(null)"
2009-07-29 14:19:40, Info CSI 0000005f Created NT transaction (seq 7) result 0x00000000, handle @0x4674
2009-07-29 14:19:40, Info CSI 00000060 Error STATUS_CANNOT_DELETE while executing operation HardLinkFile on [l:328{164}]"\SystemRoot\WinSxS\x86_microsoft-windows-i..ersandsecurityzones_31bf3856ad364e35_8.0.6001.18813_none_97c46c79ec9c8e1f\urlmon.dll, \??\C:\Windows\System32\urlmon.dll"

2009-07-29 14:19:40, Info CBS Exec: Failed to commit CSI transaction due to file in use or Component reboot required, package changes need to be pended.
2009-07-29 14:19:40, Info CSI 00000061 Creating NT transaction (seq 8), objectname [6]"(null)"
2009-07-29 14:19:40, Info CSI 00000062 Created NT transaction (seq 8) result 0x00000000, handle @0xf64
2009-07-29 14:19:41, Info CSI 00000063@2009/7/29:13:19:41.217 CSI perf trace:
CSIPERF:TXCOMMIT;145010
2009-07-29 14:19:41, Info CBS Failed removing poqexec from Cbs key. hr: 0x80070002
2009-07-29 14:19:41, Info CBS Failed removing impactful-commit disabling value from CCP. hr: 0x80070002
2009-07-29 14:19:41, Info CBS Setting ExecuteState key to 0
2009-07-29 14:19:41, Info CBS Setting RollbackFailed flag to 0
2009-07-29 14:19:41, Info CBS Exec: Pended transaction, changes will be applied during shutdown/startup processing.

and these

2009-07-14 18:52:25, Info CSI 000000ea ICSITransaction::Commit calling IStorePendingTransaction::Apply - coldpatching=FALSE applyflags=15 (0x0000000f)
2009-07-14 18:52:25, Info CSI 000000eb Creating NT transaction (seq 11), objectname [6]"(null)"
2009-07-14 18:52:25, Info CSI 000000ec Created NT transaction (seq 11) result 0x00000000, handle @0x3f0
2009-07-14 18:52:25, Info CSI 000000ed Error STATUS_CANNOT_DELETE while executing operation HardLinkFile on [l:298{149}]"\SystemRoot\WinSxS\x86_microsoft-windows-gdi_31bf3856ad364e35_6.0.6002.18051_none_ab8480c057d44ef1\dciman32.dll, \??\C:\Windows\System32\dciman32.dll"

2009-07-14 18:52:25, Info CBS Exec: Failed to commit CSI transaction due to file in use or Component reboot required, package changes need to be pended.
2009-07-14 18:52:25, Info CSI 000000ee Creating NT transaction (seq 12), objectname [6]"(null)"
2009-07-14 18:52:25, Info CSI 000000ef Created NT transaction (seq 12) result 0x00000000, handle @0x498
2009-07-14 18:52:25, Info CSI 000000f0@2009/7/14:17:52:25.606 CSI perf trace:
CSIPERF:TXCOMMIT;180388
2009-07-14 18:52:25, Info CBS Failed removing poqexec from Cbs key. hr: 0x80070002
2009-07-14 18:52:25, Info CBS Failed removing impactful-commit disabling value from CCP. hr: 0x80070002
2009-07-14 18:52:25, Info CBS Setting ExecuteState key to 0
2009-07-14 18:52:25, Info CBS Setting RollbackFailed flag to 0
2009-07-14 18:52:25, Info CBS Exec: Pended transaction, changes will be applied during shutdown/startup processing.

and this

2009-06-11 21:05:47, Info CSI 00000049 Error STATUS_CANNOT_DELETE while executing operation HardLinkFile on [l:302{151}]"\SystemRoot\WinSxS\x86_microsoft-windows-rpc-local_31bf3856ad364e35_6.0.6002.18024_none_b5cf780142473936\rpcrt4.dll, \??\C:\Windows\System32\rpcrt4.dll"

2009-06-11 21:05:48, Info CBS Exec: Failed to commit CSI transaction due to file in use or Component reboot required, package changes need to be pended.
2009-06-11 21:05:48, Info CSI 0000004a Creating NT transaction (seq 6), objectname [6]"(null)"
2009-06-11 21:05:48, Info CSI 0000004b Created NT transaction (seq 6) result 0x00000000, handle @0x748
2009-06-11 21:05:56, Info CSI 0000004c@2009/6/11:20:05:56.636 CSI perf trace:
CSIPERF:TXCOMMIT;8421858
2009-06-11 21:05:56, Info CBS Failed removing poqexec from Cbs key. hr: 0x80070002
2009-06-11 21:05:56, Info CBS Failed removing impactful-commit disabling value from CCP. hr: 0x80070002
2009-06-11 21:05:56, Info CBS Setting ExecuteState key to 0
2009-06-11 21:05:56, Info CBS Setting RollbackFailed flag to 0
2009-06-11 21:05:56, Info CBS Exec: Pended transaction, changes will be applied during shutdown/startup processing.

not sure if these are helpful to you, I found them quickly from just using "find" and the word "cannot"

Thank you for your help.

Whoops wrong thread sorry?

Can anyone take a look at the parts that I posted and comment?
I can If needed post the entire thing.

Bumping this in hope that someone will take a look at it please.

Will no one take a look at it for me?

If all is fine now you should probably move on. Cant remember the tool but I think there is one to present stupid log in a more readable form. Dont waste time since all is ok.

But check every now and then. Sfc drove me nuts once. I could run it 10 times in a row and every time errors - log showed it was random. Was close to reinstall. During that I was doing some minor tweaking of memory modules and bios, a little issue with 4x1gb on a certain chipset. Computer was stable enough, memtest86 ok - but some problems with better test programs. No bsod or nothing but 99% approved is not good enough. So I gave up on bios and did what everyone else was doing, lowered ram speed 1 notch since 4 modules just could not be made 100% stable. You can guess what happend to SFC, now perfect, no endless error-loops. Going back to old settings made them come back - so reproducible even. Gained some respect for sfc, must task computer heavily. Strange incident but could be important since computer appeared stable. More likely to be relevant if you build your own or lets hope that for HP, Dell etc.

If more errors pop up think creatively. Much like with minidump files you can get mislead. Keep an eye on which files are "corrupted". If random there could be other problem, mine was hardware but why not software?. I think MS is right though, errors are not normal but always keep door open for strange events.

Thanks for replying.
There was nothing that I could see wrong with the scan I just thought I would run it and see what happened so I was shocked at all the errors, but as it is now fine I think it is probably best to move on as I will never know what caused the errors in the first place.
Just weird that they all seem to be from a few months ago and I hve had the computer over 2 1/2 years now.
My computer is just a Dell not custom made and I know very little about computers in general so anything that goes wrong worrys me a bit.

Some errors could be result of MS updates perhaps. Like some actions always trigger an error/warning in Event viewer - while being completely harmless. Think Vista has had one about Security Center for ages, and their new antivirus also give error. Will be fixed they say. Well you run sfc and not afraid to look at logs so will be suspicious if repairs have impact outside sfc-world. I dont have much clue about how it works, may be so sensitive a few registry modifications by other programs sets off a repair. Annoying to see errors right? And the other way around. That and chkdsk are comforting to run, like basic maintenance. Dont think it is waste of time.

I ran chkdsk twice, one day it took like 3+ hours and a week later it took 5 minutes!
I had alot on errors in event viewer also but as windows is updating fine and my internet is ok, what ever caused those errors must have been fixed in the sfc I think.