[SOLVED] [Win7SP1Pro x64] SFC quirk

B

bnk87

Member
Joined
Aug 6, 2017
Posts
15
Intro:
- Acquired Win 7 Pro Computer that I intend to use in my office. No obvious problems with it, but doing preventative diagnostics before using.
- sfc /scannow reports there are problems it cannot fix.
- The ONLY unusual thing I see in CBS.log (filtered for "[SR]" and "Error" entries) is "Repairing 0 components" prior to last POQ pass
- Malwarebytes sees no rootkit or virus
- chkdsk /r -- no problems
- running sfc in offline mode from Win 7 repair disk sees no problems
- DISM sees no problems
- Have run sfc /scannow about 4 times and symptom persists.
- SFCFix sees no problems.

Should I be worried about this odd sfc error with no other symptoms?
 
Re: SFC quirk

Hi. . .

In my opinion, anytime one receives a used computer, you really should start fresh by reinstalling Windows. You never know what the shape of the OS is or what the other user(s) left behind for you.

If you don't want to reinstall Windows, but want the SFC errors addressed, please follow these instructions -

Windows Update Forum Posting Instructions

Attach the output to your next post in THIS thread - no need to create a new thread.

Regards. . .

jcgriff2
 
Re: SFC quirk

Thank you for replying to my thread. I will reinstall windows only as a last resort, based on a proprietary program where I have a permanent license, but would have to go through customer support to reinstall, and they would want a service subscription.... would like to avoid that.

Start time: 2017-08-06 07:37:35.658
Microsoft Windows 7 Service Pack 1 - amd64
Not using a script file.
AutoAnalysis::
SUMMARY: No corruptions were detected.
AutoAnalysis:: directive completed successfully.
Successfully processed all directives.
Failed to generate a complete zip file. Upload aborted.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2017-08-06 07:45:38.526
----------------------EOF-----------------------
 

Attachments

Re: SFC quirk

I would be very grateful if a Windows Wizard could help me crack this puzzle.
 
Re: SFC quirk

Hello and welcome

Due to the precise nature of your corruption, you will receive help from a user named softwaremaniac. He's one of our senior trainees here who's in his final phase of his studies and needs to gain some real world experience in specific areas of Windows Update. This means that he'll be assisting you, but that I will first need to double check and approve his fixes before he posts them to you. If anything this is a good thing for you because it means that you've got at least two of us watching over your thread, but it will unfortunately add a slight delay between each reply. I hope that you understand and can accept the need for us to train up new members in this way in order to carry on doing what we do here, however, if for any reason you object to this setup, I will happily take on your thread myself.

Thank you very much for your understanding. We'll be with you very shortly.
 
Re: SFC quirk

Step#1 - System Update Readiness Tool (SUR)
 1. Download and run the following file.
2. When it asks you if you wish to install, please answer yes. Note: It could take 15 minutes or more to run. Please don't cancel.
3. You will get an Installation Complete screen when it's done running.
4. Please attach the log from the following location. C:\Windows\Logs\CBS\CheckSUR.log
Please Note:: if the file is too big to upload to your next post please upload via a service such as Dropbox or One Drive or SendSpace and just provide the link.
 
Re: SFC quirk

Thanks for your help, softwaremaniac.

I made a mistake in my original post. I ran SUR, not DISM. Here is the log output:

=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2017-08-05 10:37
Checking Windows Servicing Packages
Checking Package Manifests and Catalogs
Checking Package Watchlist
Checking Component Watchlist
Checking Packages
Checking Component Store
Summary:
Seconds executed: 895
No errors detected
 
Re: SFC quirk

SFC Scan


  1. Click on the Start
    Start%20Orb.jpg
    button and in the search box, type Command Prompt
  2. When you see Command Prompt on the list, right-click on it and select Run as administrator
  3. When command prompt opens, copy and paste the following commands into it, press enter after each

    sfc /scannow

    Wait for this to finish before you continue

    copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
  4. This will create a file, cbs.txt on your Desktop. Please attach this to your next post.
 
Re: SFC quirk

Please see the CBS.log file attached to my 2nd post in this thread. Note the dates and times on the SUR log and the CBS log -- I did the last sfc /scannow after the SUR check.
 
Re: SFC quirk

If you need me to repeat these steps, which I anticipated and performed before my original post, I will. Just let me know. Thanks again for helping.
 
Re: SFC quirk

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

View attachment cbs2.zip
 
Re: SFC quirk

The standalone installer tells me:

"Update for windows (KB2966583) is already installed on this computer."

Add/remove programs shows it being installed 7/11/2014.
 
Re: SFC quirk

Step#1 - DISM /ScanHealth
Warning:this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.


  1. Click on the Start button and in the search box, type Command Prompt
  2. When you see Command Prompt on the list, right-click on it and select Run as administrator
  3. When command prompt opens, copy and paste the following command into it, press enter
    Dism /Online /Cleanup-Image /ScanHealth
  4. Once it finishes, attach the following log.
    C:\Windows\Logs\CBS\CheckSUR.log
 
Re: SFC quirk

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\SVR1>Dism /Online /Cleanup-Image /ScanHealth
Deployment Image Servicing and Management tool
Version: 6.1.7600.16385
Image Version: 6.1.7601.18489
................................................................................
................................................................................
................................................................................
................................................................................
................................................................................
...................Completed running scanhealth, check logs at %windir%\logs\CBS
\Checksur.log
The operation completed successfully.

=================================
Checking System Update Readiness.
Binary Version 6.1.7601.23471
2017-08-19 09:29
Checking Windows Servicing Packages
Checking Package Manifests and Catalogs
Checking Package Watchlist
Checking Component Watchlist
Checking Packages
Checking Component Store
Summary:
Seconds executed: 874
No errors detected
 
Re: SFC quirk

Step#1 - Capture Process Monitor Trace
 1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Open an elevated Command Prompt and run sfc /scannowjust like you have in the past.
3. Stop Process Monitor as soon as sfc reports the failure message. You can simply do this by clicking the magnifying glass on the toolbar as shown below.
11908d1430506241-windows-updates-fail-repeatedly-stop-jpg


4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine.
5. Zip up and attach the LogFile.PML file as well as your CBS.log.
 
Re: SFC quirk

1. The link in the latest post did not work, so I downloaded process monitor from SysInternals directly.
2. Done.
3. I have never gotten an error from sfc. Simply a message that corrupt files couldn't be fixed. So I did the capture just as sfc completed.
4. Logfile.PML is 3.5 GB. compressed, it's close to 300 MB. How should I upload?
 
You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top