"All in one Windows Repair v3.2.2 (Pro Version) - Error Msg Confusion.

[Roger...]

There is still a strange Windows 7 Pro OS issue.

 Today's "Windows Repair 3.2.2" system file check generated this error message:
-------------------- Error Msg - START:
Administrator System File Check <-- NotePad Dialog Display

[SC] ChangeServiceConfig SUCCESS
D:\Program Files <x86>\Tweaking.com Windows Repair (All in One) "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 them.
Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log
Please Restart Your Computer When System File Checker is Finished.
Press any key to continue . . .
-------------------- Error Msg - END:

In looking at the CBS.log it reports:
"All files and registry keys listed in this transaction  have been successfully repaired"

With one message indicating a problem exist and the message that all is well, I could use some guidance to understand the context of what each message is telling me.

Is that any chance I could pass along the CBS.log file for you to see if all is well, or not?

Thanks,
Roger...

[Shane]

The system file check is part of the operating system, my program simply calls it.

It is really odd that the cmd window would show it found errors yet the cbs log doesnt, did you do a search in the log for the word error to see if there is anything?

Shane

[Roger...]

I found it confusing to have an error displayed in the console information that Log believed was resolved.

A search for the word: "error" with Notepad++ did find what might have been two errors of the same package. 

Line: 20,945:
2015-06-17 06:27:02, Info                  CBS    Failed to get session package state for package: Package_39_for_KB3040272~31bf3856ad364e35~amd64~~6.1.1.1 [HRESULT = 0x80070490 - ERROR_NOT_FOUND]

Line 21,477:
"2015-06-17 06:27:02, Info                  CBS    Failed to get session package state for package: Package_39_for_KB3040272~31bf3856ad364e35~amd64~~6.1.1.1 [HRESULT = 0x80070490 - ERROR_NOT_FOUND]"

This is the second time where the console reports showed an error, but the log indicated there are no errors.

Thanks for responding.

[Shane]

Ok, since the scan did get an error in the log the cmd.exe window shows that there was an error, while since that error was looking at the packages files, which sfc doesnt fix, it reported no problems at the end of the log. This is why it is doing that, kind of a crap design lol

Does my pre-scan show any missing packages files on your system?

Shane

[Boggin]

The CBS log usually reports that everything has been fixed, but that doesn't seem to apply to any Cannot... entries.

You may be able to copy & paste this command at an elevated command prompt where it will put an icon onto your desktop which will open into Notepad which you can then post - else you will have to enter the command manually.

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

[Roger...]

Does my pre-scan show any missing packages files on your system?

I didn't see anything that indicated files were missing.

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

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:

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/

Instructions on that page were clear and easy to enable.  In the Scan section these results were reported:

Code: [Select]

   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

Second step section applied the SFCFix.exe program.  Its results showed this information:

Code: [Select]

   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 . . .
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: [Select]

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.
ADDED AFTER CONSOLE WINDOWS EXITED:
Notepad displayed this information when the SFCFix Console window was closed with EXIT.

Code: [Select]

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----------------------- 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?

[Boggin]

Do they affect the running of any programs and can you successfully run a manual check for Windows Updates ?

I haven't come across that error before and Google doesn't really have anything definitive on it that I can find.

It may be best to post a new CBS log and then Shane can have a look at it on Monday.

Not sure if a chkdsk /f would report anything on them but you could give that a try to see what it reports.

[Roger...]

Do they affect the running of any programs and can you successfully run a manual check for Windows Updates ?

I don't know.  I do know this OS still has problems that cause a lot of small issues.  About 18-months ago it had a huge amount of problems.  Since finding "All-in-One" running many times since many of the issues have been resolved, but many still exists that still cause a lot of little problems.

One of my biggest issues was unknown accounts that were given a long series of numbers as a names (see attached image).  I've look at hundreds of folders to see in attempt to find them and then find their parent so they could be removed.  None of the "number-series" accounts showed in the Account Management area so there was no way to removed like most account would be removed.  These were removed by reassigned their folders at the level the lower level folders were inheriting these unknown accounts.


I've attached the CBS_20150626.log copied from the main CBS.Log file.  Records are all from today.

ChkDsk w/o the "/F" was run and it showed there aren't any disk issues:

Code: [Select]

   Microsoft Windows [Version 6.1.7601]
   Copyright (c) 2009 Microsoft Corporation.  All rights reserved.
 
   C:\>chkdsk
   The type of the file system is NTFS.
   Volume label is R10_C Boot.
 
   WARNING!  F parameter not specified.
   Running CHKDSK in read-only mode.
 
   CHKDSK is verifying files (stage 1 of 3)...
     309248 file records processed.
   File verification completed.
     1640 large file records processed.
     0 bad file records processed.
     2 EA records processed.
     98 reparse records processed.
   CHKDSK is verifying indexes (stage 2 of 3)...
     387556 index entries processed.
   Index verification completed.
     0 unindexed files scanned.
     0 unindexed files recovered.
   CHKDSK is verifying security descriptors (stage 3 of 3)...
     309248 file SDs/SIDs processed.
   Security descriptor verification completed.
     39155 data files processed.
   CHKDSK is verifying Usn Journal...
     260195128 USN bytes processed.
   Usn Journal verification completed.
   Windows has checked the file system and found no problems.
 
    468848639 KB total disk space.
    194960368 KB in 268846 files.
      156952 KB in 39156 indexes.
          0 KB in bad sectors.
      648199 KB in use by the system.
       65536 KB occupied by the log file.
    273083120 KB available on disk.
 
        4096 bytes in each allocation unit.
    117212159 total allocation units on disk.
     68270780 allocation units available on disk.
Biggest issue appears when a "Blue Crash Screen" appears, and when a shut down generates a Window crash error that suspends shutdown until the dialog is cleared.

Thanks again for helping,
Roger...

[Boggin]

Does the sfc /scannow still report no violations ?

I'll definitely have to leave that last error pop up to Shane, but if you can, can you download Blue Screen View and post its output.

This will analyse the Dump files and will help Shane if he can get back on Monday.

http://www.nirsoft.net/utils/blue_screen_view.html