Main Forum > General Computer Support
"All in one Windows Repair v3.2.2 (Pro Version) - Error Msg Confusion.
Roger...:
--- Quote ---Does my pre-scan show any missing packages files on your system?
--- End quote ---
I didn't see anything that indicated files were missing.
--- Quote ---findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt"
--- End quote ---
Posted findstr command surfaced and icon for: sfcdetails.txt
File attached shows many "Cannot repair member file" items than the CBS.Log file.
Thanks for responding.
Boggin:
I wouldn't worry about those - run a chkdsk /f and that should come up clean.
KB3068708 is responsible for those errors just as its May's predecessor KB3022345 was causing sfc to incorrectly report Diagnostic Tracking Service errors.
KB3068708 was supposed to have countered that but has caused similar problems for some as this article explains. http://www.sevenforums.com/performance-maintenance/371653-sfc-scannow-found-corrupt-files-but-could-not-delete-rectify-them.html
I don't know if your restore points go back to before this month's WUs but uninstalling that update may stop those errors or you could run SFCFix.exe which may clear them. http://thetechcookbook.com/automatic-sfc-corruption-repair-sfcfix-exe/
Roger...:
I believe we are making progress.
Following this advice:
--- Quote ---I don't know if your restore points go back to before this month's WUs but uninstalling that update may stop those errors or you could run SFCFix.exe which may clear them. http://thetechcookbook.com/automatic-sfc-corruption-repair-sfcfix-exe/
--- End quote ---
Instructions on that page were clear and easy to enable. In the Scan section these results were reported:
--- Code: --- Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\>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 them.
Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example
C:\Windows\Logs\CBS\CBS.log
--- End code ---
Second step section applied the SFCFix.exe program. Its results showed this information:
--- Code: --- Welcome to SFCFix by niemiro and sysnative.com.
Checking for updates . . .
No new update is available at this time.
Processing directive 1 of 1 (AutoAnalysis::)
Checking store directories . . .
Checking CBS.log . . .
Checking CheckSUR.log . . .
Checking CheckSUR.persist.log . . .
Attempting repair . . .
Stage 1
Stage 2
Stage 3
Stage 4a
Stage 4b
Stage 4c
Stage 4d
Stage 9
SUMMARY:
CBS & SFC total detected corruption count: 2
CBS & SFC total unimportant corruption count: 0
CBS & SFC total fixed corruption count: 2
SURT total detected corruption count: 0
SURT total unimportant corruption count: 0
SURT total fixed corruption count: 0
Press any key to continue to explanation of summary . . .
--- End code ---
I looked for the file: SFCFix.txt but various search methods couldn't find it on either of my two disk.
Results from SFCFix.exe program felt promising. A second SFC /SCANNOW was executed to see if Windows SFC would agree. It did when it reported:
--- Code: ---Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\>SFC /SCANNOW
Beginning system scan. This process will take some time.
Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection did not find any integrity violations.
--- End code ---
ADDED AFTER CONSOLE WINDOWS EXITED:
Notepad displayed this information when the SFCFix Console window was closed with EXIT.
--- Code: ---SFCFix version 2.4.5.0 by niemiro.
Start time: 2015-06-26 09:49:15.680
Microsoft Windows 7 Service Pack 1 - amd64
Not using a script file.
AutoAnalysis::
FIXED: Corruption at C:\WINDOWS\winsxs\amd64_microsoft-windows-u..ed-telemetry-
client_31bf3856ad364e35_6.1.7601.18869_none_fde7d5f71db043ad\utc.app.json has been
successfully repaired from C:\Windows\winsxs\amd64_microsoft-windows-u..ed-telemetry-
client_31bf3856ad364e35_6.1.7601.23040_none_fe7de82236c5fac8\utc.app.json.
FIXED: Corruption at C:\WINDOWS\winsxs\amd64_microsoft-windows-u..ed-telemetry-
client_31bf3856ad364e35_6.1.7601.18869_none_fde7d5f71db043ad\telemetry.ASM-
WindowsDefault.json has been successfully repaired from C:\Windows\winsxs
\amd64_microsoft-windows-u..ed-telemetry-
client_31bf3856ad364e35_6.1.7601.23040_none_fe7de82236c5fac8\telemetry.ASM-
WindowsDefault.json.
SUMMARY: All detected corruptions were successfully repaired.
AutoAnalysis:: directive completed successfully.
Successfully processed all directives.
SFCFix version 2.4.5.0 by niemiro has completed.
Currently storing 2 datablocks.
Finish time: 2015-06-26 10:24:24.264
----------------------EOF-----------------------
--- End code ---
I think this resolves the confusion between the different earlier test results.
Is above a safe assumption?
Boggin:
When you read the CBS Log, the [SR] entries show that it has checked a particular file and run a check repair on it and when nothing is found to be wrong or it was able to fix something, it classes that as a successful repair but the Cannots remain which it then reports as not being able to repair some files.
I forgot that SFCFix.exe puts its report onto the Desktop, but it now looks as if it's good to go.
I recently factory reset this machine and I let that KB install but running a sfc /scannow later reported that it had repaired all files.
I don't know if they were related to this KB or if something else had gone awry but subsequent sfc /scannows have come back clean.
If you don't intend to upgrade that machine to Win 10 then you don't need that update as it's a MS spy.
Roger...:
I do plan on upgrading to Windows 10.
Thank you for showing how to resolve this KB issue. I've learned a lot by working through the solution steps you sent.
After your CBS.LOG comment above the earlier problems no longer appear. There are warning messages in today's section of the log that were there before but I did give them much weight before.
For example, in the CBS log none of the previous errors are there in today's section of the report. However there are a lot of these warning messages: CBS_E_MANIFEST_INVALID_ITEM. This message appears 1,201 times in today's section that covers 12,491 lines.
Do you know if this warning message is something that needs to be resolved?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version