[SOLVED] paradox: sfc /scannow and SFCFix.exe resolve problem which remains

Nuno

Member
Joined
Jul 23, 2015
Posts
9
Hello everyone!

I have been experiencing some problems with my PC for some time. After much trial and error, getting all updates up to date, etc, I finally got it almost right but not quite. Running sfc /scannow gives me the "Windows Resource Protection found corrupt files but was unable to fix some of them," so I run the DISM /Online/Cleanup-Image/RestoreHealth, which, after running its cycle, tells me that everything was repaired. But things are still not quite right so I run the WRP and the same thing: there are corrupt files..., I run the DISM, everything is fine, and back to square one. Note that I have done this process over several times, and have taken care to run the WRP at least three times turning the PC off between each run, and again before and after running DISM. In looking for further solutions I came across your SFCFix.exe and your great help page (thanks Go To Power) but when I run it the same thing happens: it tells me that it has located the problem, it fixes it, but then it is right back when I again run the WRP. I have no idea what to do so I've followed your instructions and come looking for rescue. I couldn't get the auto analysis in the form of a SFCFix.txt file because running the program doesn't produce one (maybe I have missed some essential setting) (please note from my introduction on signing up to Sysnative that I know nothing, though I like to try to figure it out). I have taken a snapshot of the SFCFix tool to illustrate
1oF8CvjUkdDAAAAAElFTkSuQmCC


Next I will try to load up the CBS file. Didn't work. I will try your large file tool. Hope I'm doing this right. If not please give me a heads up, and do remember that I'm going to need a lot of guidance as I really know nothing.

I don't see the snapshot of the SFCFix on the post, though I saw it when I was writing it. Can you tell em how to post it if in fact it doesn't show. Thanks.
 
Hi,

Using windows 8.1. Yes, specially for me; very complicated. Any other suggestions?

Thank you
 
Copy the CBS.log file from C:\Windows\Logs\CBS\CBS.log to your Desktop, then right click on it and choose Send To -> Compressed (zipped) Folder
Try to attach the CBS.zip file on your Desktop with your reply.

Do you have a OneDrive, DropBox, or other file sharing service account that you could use to share the CBS file if it is too large to attach?
 
The files that are reported as corrupt are false positives and shouldn't cause any trouble.

I would like a fresh log to confirm.

SFC Scan

  1. Swipe in from the right edge of the screen, and then tap Search.
    (If you're using a mouse, point to the upper-right corner of the screen, move the mouse pointer down, and then click Search.)
  2. Type cmd in the search box, and then right-click or press and hold on Command Prompt.
  3. Tap or click Run as administrator.
  4. 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
  5. This will create a file, cbs.txt on your Desktop. Please right click on it and choose Send To -> Compressed (zipped) Folder then attach the zip to your next post.
 
View attachment cbs.zipView attachment cbs.zip, I think I messed this up a bit, but hopefully you will be able to access the zip. Thanks a lot for checking this out. Let me ask though, why would I be getting false positives? I thought that was a problem with Windows 10, not 8.1. In any case, if these false positives keep on being repeated how do I know when there is an actual problem?
 
The logs look good.

The false positives are telemetry.ASM-WindowsDefault.json and utc.app.json, they will be detected as corrupt on Windows 7, 8, and 8.1.

This is what Microsoft says: https://support.microsoft.com/en-us/kb/3022345
This update contains the following files that are occasionally updated by the Diagnostic Tracking Service:
  • telemetry.ASM-WindowsDefault.json
  • utc.app.json
The two files are marked as static files in the update. When an advanced user runs the System File Checker Tool (sfc.exe), the files are unintentionally flagged as corrupted. There is no impact or actual corruption on a device running this update, and a later service update will resolve this issue.

Do you have any Windows Updates that are not installing?
 
That is great news. Thanks for the help. As to the updates, I just checked, there is one update, Definition Update for windows Defender-KB2267602 (Definition 1.203.69.0) which failed to install on 22/07/2015. I have also just installed all optionals, but that still shows on Windows Update History as a failed install. As an aside, as I ran updates (I have my PC set to check for and install updates automatically), Upgrade to Windows 10 Home failed to install (Perhaps this is because there is something else that needs to come out for it to install?).
What might be the reason for these failed installs? And the install that shows as failed in the history, will it continue to show as failed even if a later update covering the same code is installed - that is, how do I know if the update was successfully installed at some point? By the way, I don't see anything telling me that any updates are pending, should I if there were an unsuccessful install?
 
Yes, the update history records the success or failure of any update installation attempt.
On a healthy Windows installation if for some reason an update fails to install, it will still be listed as available in Windows Update on the next check for updates until it is superseded by a newer version of the update or is successfully installed.

If Windows Update says your system is up to date, you should be good to go :)

Upgrade to Windows 10 Home failed to install
What is the KB# for this update, if available?

If you review your update history you can right click on an update and choose details to show more information about the failure, such as the error code.
 
Can't find KB#. there were two update attempts, these are the details Upgrade to Windows 10 Home

Installation date: ‎28/‎07/‎2015 19:47

Installation status: Failed

Error details: Code 80240020

Update type: Important

Install the next version of Windows.

More information:
Before you install Windows 10 Insider Preview - Microsoft Windows

Help and Support:
Windows Insider Program - Microsoft Community

and prior


Upgrade to Windows 10 Home

Installation date: ‎28/‎07/‎2015 19:26

Installation status: Failed

Error details: Code 80240020

Update type: Important

Install the next version of Windows.

More information:
Before you install Windows 10 Insider Preview - Microsoft Windows

Help and Support:
Windows Insider Program - Microsoft Community


The help page seems to indicate that this is a preview. Do I have a problem with the update install?
 
I see a few other posts with the same update name and error code, I think it's safe to ignore for now.
 
OK Zcomputerwiz, thanks a lot for all the help. You guys do a great job. I'm sure to return the next time I screw something up.

Best,
Nuno
 

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

Back
Top