Main Forum > General Computer Support
i got error in pre scan (solved)
mrkill:
this is the file in C:\Windows\Logs\CBS\CBS.Log
my computer is : windows 7 ultimate 32bit
Tone111:
Hi, check out my reply in another thread http://www.tweaking.com/forums/index.php/topic,3107.0.html - I had a similar issue after doing a Repair install and then updating Windows, the SFC scan went from clear to finding corrupt files, some of which couldn't be repaired. I can only assume it was caused by one (or more) of the updates being installed/configured incorrectly...
I used the SFCFix.exe file from the link in the above thread and it cleared my corrupt SFC scan so give it a go if you get a minute (or maybe an hour or more - it took a good while to run on my Win7 64 bit Home Premium but did the job well after that!) :smiley:
Shane:
Looking at the cbs log you will see things like this
--- Quote ---Hashes for file member \SystemRoot\WinSxS\x86_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18839_none_a1e9aa37653a7ea4\telemetry.ASM-WindowsDefault.json do not match actual file [l:66{33}]"telemetry.ASM-WindowsDefault.json" :
Found: {l:32 b:ddW/ziH5iRGiXQCN1UI4xhGYdCmRBwYaMf/LZiyKogk=} Expected: {l:32 b:EeQJzlVPvq9GNIcA2FEwrOjEeuDam1G+ol3x61gKasQ=}
--- End quote ---
Notice this part
Found: {l:32 b:ddW/ziH5iRGiXQCN1UI4xhGYdCmRBwYaMf/LZiyKogk=}
Expected: {l:32 b:EeQJzlVPvq9GNIcA2FEwrOjEeuDam1G+ol3x61gKasQ=}
What this is saying is the found one is the hash of the file and windows looks at the cat file to pull what the hash of the file should be and as you can see they dont match. If a file is changed even by 1 byte the hash changes.
So either the file is corrupted or the cat file is. Problem is we dont know which and the log doesnt give us much to go on. Sometimes the system readiness tool from MS can help but if it doesnt and there is file corruption in the winsxs folder you may have no option other than doing a repair install of windows because MS has no way of rebuilding the winsxs folder.
Depending how many files are found to be bad we could just manually replace the files from a good machine, but if there is a LOT of files then a repair install is going to be needed.
In this case you also had a mum file that was shown as bad, mainly because it was modified somehow and so the hash didnt match. Well now I am seeing that in a lot of other places, this doesnt normally happen unless something went and messed with them OR the hard drive has bad sectors and those files are on the bad sectors and so are getting corrupt.
Have you done a bad sector check on the drive yet?
The command for it is to open a cmd.exe window as administrator and put it
chkdsk C: /r
It will say the drive is in use and would you like to do it at next boot, hit Y and have it do it and then reboot and let the scan go, it will take a while but lets see what it shows.
Shane
mrkill:
hi, i did a fresh clean install of windows 7 utimate 32bit and same problem is exist when i run sfc/SCANNOW in cmd
C:\Windows\system32>sfc/SCANNOW
Beginning system scan. This process will take some time.
Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection found corrupt files but was unable to fix some of th
em.
Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example
C:\Windows\Logs\CBS\CBS.log
C:\Windows\system32>
also i have checked my disk for bad sectors. i will attach the cbs file. so is it normal ? or something wrong with my machine.
thanks for help. :smiley:
Shane:
You are still getting corrupt files after a fresh install? Was it a fresh as in delete the file system and start fresh install or was it a repair install?
Also when you did a chkdsk on the drive for bad sectors what was the results?
Shane
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version