[SOLVED] SFC Corrupt Files Found but SFCFix looks good?

Poking around in the SFC log file I found a corrupt file:

2015-10-16 20:30:29, Info CSI 0000f60c Hashes for file member \??\C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Accessories\Tablet PC\Windows Journal.lnk do not match actual file [l:38{19}]"Windows Journal.lnk" :
Found: {l:32 b:Rn0ijVEFoR1dxu3z3s/+cax7d5jGzDJoBYLXPemTPxI=} Expected: {l:32 b:MZg2KqMnHh+iyhodplgMB7y35LaRMt4yIz1PaJqPuwo=}

Tried:

dism /online /cleanup-image /scanhealth

dism /online /cleanup-image /checkhealth

dism /online /cleanup-image /restorehealth

But still have errors after SFC /scannow.
 
SFCFix Script

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. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
  5. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.

View attachment SFCFix.zip

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 zip and attach this to your next post.
 
Hi Zcomputerwiz,

I ran sfc /scannow and it came up clear with "Windows Resource Protection did not find any integrity violations."


I think this problem is fixed.

Fixing problems like this is pretty much beyond the scope of most users?

Attached is my cbs.zip as requested. Thanks for your help.

Scott


View attachment cbs.zip
 
Looks good :thumbsup2:

I'll mark the thread solved.

Fixing problems like this is pretty much beyond the scope of most users?
Click to expand...
Microsoft has some instructions on how to read the CBS (created by SFC) and SURT/DISM logs for which files are being detected and then collect files from another known good installation and replace them manually.
Here's the page with instructions for SFC and CBS: https://support.microsoft.com/en-us/kb/929833
Here's the page with instructions for SURT and CheckSUR.log: https://support.microsoft.com/en-us/kb/2700601

DISM is like SURT, but logs the results in the CBS log and automates some of the file replacement by downloading the updates, if possible.

Hopefully that answers your question :)
 
Hi Zcomputerwiz,

I had checked out similar links in an effort to fix my problem. I backed up my system first, so if I screwed things up I could always go back, So...to locate a "good" uncorrupted file you have to extract from the Windows .iso image and replace it into your system? I extracted the correct file, but ran into file ownership problems with the winsxs folder permissions trying to copy over. I pretty much stopped there.

Is there a tutorial on how to make your own SFCFix.zip file and use SFCFix.exe to fix things yourself....or is this just for internal Sysnative internal use? Just curious, but I am sure users can get into serious problems if used incorrectly.

Scott
 
Yes, you can get a good replacement file from either another known good computer running the same version of Windows, the original installation media (if it is that version of file that is missing) or whichever Windows update had installed the file on the system in the first place.
At that point you would need to use the command line tools takeown and icacls or the Windows file properties GUI to take ownership and grant write permissions for the files, then return them once the replacement is performed.

SFCFix automates the process of taking permissions and ownership for the files, replacing them, and returning the permissions to the previous state among other things. As you suspected, there is a lot that could go wrong if SFCFix was used incorrectly.
It is a very powerful tool that requires training to use properly, so instructions are not provided to the general public at this time.

Sysnative does have a Windows Update Academy if you would be interested in learning the process of sourcing replacement files and how to use tools (including SFCFix) to make your own fixes :)
 
You must log in or register to reply here.
Back
Top