SFC /Scannow can't fix corrupt files.

Tweakit · 15 May 2015

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 · 16 May 2015

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

Code:

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 · 16 May 2015

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 · 16 May 2015

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 · 16 May 2015

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.