SFC /Scannow can't fix corrupt files.

[Tweakit]

Every few months I run the SFC and its never reported a problem. Today I ran it and it found problems it can't fix. I attached the sfcdetails file. I've run the SFC /scannow command at least 6 times rebooting between checks but it always returns the same result. My computer seems to be running fine so I'm not even sure if I actually have a problem. Yesterday I installed 29 Microsoft updates which was about 500MB in total but i don't really know if that's when the problem started or not.
I'd like to get some suggestions about the best way to fix this or if I even should fix it.
Thanks for reading.
Also, i do have a repair disk which I made a long time ago.

 

[Ztruker]

Try these from a Elevated Command Prompt:

Dism /Online /Cleanup-Image /StartComponentCleanup
Dism /Online /Cleanup-Image /RestoreHealth
SFC /scannow

 

[Tweakit]

Thank you Ztruker for your suggestion.
Is this running the system update readiness tool from an online location?
If so, is this the same as what is described here: https://support.microsoft.com/en-us/kb/947821 ??
Is this a low risk operation? What does it do?
Thanks again for your help.

 

[Tweakit]

I'd still like to get some help with this as i'm not have any success. Here's what i did since the last post. I ran sfc /scannow from the repair disk booted on the CD Rom. Ran it at least 6 times but it never fixed the problems. Then I ran the System Update Readiness Tool found here: https://support.microsoft.com/en-us/kb/947821. That completed and found no problems!
Then I did a disk cleanup since my windows update backup files had grown to 12GB. That completed and the windows update backup files folder no longer appears in the disk cleanup window. Neither of these solved the problem however as sfc still wont fix problems found.
Next from within the elevated command prompt i ran: "Dism /online /cleanup-image /scanhealth." This found errors also and could not fix them. The log file it produced is attached as "DismLog.txt"
Then I again ran sfc /scannow from the elevated cmd prompt again failing to fix the problems. The log file produced is attached as "sfcdetails7.txt."
Is their anything else to try at this point other then falling back to an old restore point. I may have to try that if there is no other creative way of fixing this. Any help will be appreciated.
Thanks.

 

[AddRAM]

There is a list of about 10 updates that is causing this, I just re installed windows 5 times on 3 different ssd`s saving images along the way. When I got to the updates that say "This resolves issues in Windows" they are near the very end of all the updates, they are the culprits, if you want it right you`ll have to re install windows, unless you have rerstore points, and hide those updates, what a PITA that was

I`m all good, now I just have to put the image from the Intel onto the Samsung, sheeeeesh

 

[GokAy]

Hey, before reinstalling check to see if KB3022345 is installed. It causes corruption. If so uninstall and scan again if there will be any corruption. Or just follow this thread and apply the fix

http://www.sevenforums.com/windows-...7-update-kb3022345-causing-corrupt-files.html

post #24

 

[Ztruker]

Thank you Ztruker for your suggestion.
Is this running the system update readiness tool from an online location?
If so, is this the same as what is described here: https://support.microsoft.com/en-us/kb/947821 ??
Is this a low risk operation? What does it do?
Thanks again for your help.

Rats, you're right. SURT is for Windows 7, DISM is for 8 and up.
What is the System Update Readiness Tool? - Windows Help

 

[Tweakit]

GokAy,
Thanks much sir!! I just uninstalled KB3022345 and sfc worked fine! I didn't run the fix tool.
GokAy and Ztruker: I still may have a problem though. The SURT runs fine and finds no issues but the command "Dism /online /cleanup-image /scanhealth" still results in the same issue i described in the 4th post from the top. The resulting log file is attached and shows problems. Apparently this command is valid for windows 7 since you can find information in the cmd prompt by entering "DISM /online /?"
Can anyone help me understand if I still have a problem as shown by the DISM? I'm not sure if its real or there is some phantom explanation.

 

[GokAy]

Unfortunately I am not knowledgeable about the issue in your last post. Hopefully Ztruker will answer when he is online.

 

[Ztruker]

DISM doesn't have that support in Windows 7, only Windows 8 and above. SURT in WIn 7 does mostly what DISM does in WIn 8.

 

[Tweakit]

Ztruker,
Thanks for your reply. While i suspect you are correct, I am confused. I attached the /? response from my Windows 7 machine. The last line shows the very command that i used. i think this means the system is telling me that it is a supported command and in fact it runs and produces a log albeit showing corruption. Am I missing something or is the system incorrectly representing that this DISM feature is supported when in fact it is not?? Why do you think it is not supported? Thanks for your comments.

 

[Ztruker]

Interesting, that's not whart I see when I enter dism /? on my Win 7 Pro X64 system with SP1 and all updates:

Deployment Image Servicing and Management tool
Version: 6.1.7600.16385


DISM.exe [dism_options] {WIM_command} [<WIM_arguments>]
DISM.exe {/Image:<path_to_offline_image> | /Online} [dism_options] 
         {servicing_command} [<servicing_arguments>]

DESCRIPTION:

  DISM enumerates, installs, uninstalls, configures, and updates features
  and packages in Windows images. The commands that are available depend 
  on the image being serviced and whether the image is offline or running.

WIM COMMANDS:

  /Get-MountedWimInfo     - Displays information about mounted WIM images.
  /Get-WimInfo            - Displays information about images in a WIM file.
  /Commit-Wim             - Saves changes to a mounted WIM image.
  /Unmount-Wim            - Unmounts a mounted WIM image.
  /Mount-Wim              - Mounts an image from a WIM file.
  /Remount-Wim            - Recovers an orphaned WIM mount directory.
  /Cleanup-Wim            - Deletes resources associated with mounted WIM
                            images that are corrupt.

IMAGE SPECIFICATIONS:

  /Online                 - Targets the running operating system.
  /Image                  - Specifies the path to the root directory of an
                            offline Windows image.

DISM OPTIONS:

  /English                - Displays command line output in English.
  /Format                 - Specifies the report output format.
  /WinDir                 - Specifies the path to the Windows directory.
  /SysDriveDir            - Specifies the path to the system-loader file named
                            BootMgr.
  /LogPath                - Specifies the logfile path.
  /LogLevel               - Specifies the output level shown in the log (1-4).
  /NoRestart              - Suppresses automatic reboots and reboot prompts.
  /Quiet                  - Suppresses all output except for error messages.
  /ScratchDir             - Specifies the path to a scratch directory.

For more information about these DISM options and their arguments, specify an
option immediately before /?.

  Examples:     
    DISM.exe /Mount-Wim /?
    DISM.exe /ScratchDir /?
    DISM.exe /Image:C:\test\offline /?
    DISM.exe /Online /?

When I try to run it I get this:

>Dism /Online /Cleanup-Image /RestoreHealth

Deployment Image Servicing and Management tool
Version 6.1.7600.16385

Image Version 6.1.7601.18489


Error 87

The restorehealth option is not recognized in this context.
For more information, refer to the help.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log1

 

[Tweakit]

Ztruker,
I was a little hasty in my entry above. What I actually entered from the prompt was:
Dism /online /cleanup-image /?
If you enter that on your win 7 machine I think you will see the screen I posted in Post #11 above.
To run the command for store corruption, you need to run the last line in the screen shot repeated below:
Dism /online /cleanup-image /scanhealth
You entered:
Dism /online /cleanup-image /restoreHealth
That one is not listed in the help query which is why you get the error 87.
So, it continues to look like the command is supported but yet it produces a log file that shows corruption (see DismLog.txt attached in Post #4). This is what I’d like to get resolved.
Thanks again for any help you might provide.

 

[PaulSoebekti]

Tweakit: GokAy in post #6 had the answer spelled out for you.

I experienced the very same problem as you had - on three machines.
I recovered one from a backup image and installed ALL the May 12th updates EXCEPT for KB 3022345.
That solved the negative SFC scans.

Then I just went to the installed windows updates - uninstalled KB 3022345 - restart and all is well.
The last two repairs were quick as I don't have to re-image the hard drive ...

Hope this helps.

Paul

 

[Tweakit]

Paul,
I am aware of post #6. I mentioned earlier that my SFC scans have been clean since I uninstalled KB3022345 per GoKAy’s instruction in post #6. The question I posed in posts #8, #11 and #13 relates to the DISM command, the corruption it flags and it’s application to the Windows 7 environment. Have you tried running the command below after you solved the KB3022345 problem?
"Dism /online /cleanup-image /scanhealth"
If so, please let us know what it found. The log file will be found here:
C:\Windows\Logs\CBS\CheckSUR.log
Thanks for your comments.