Windows SFC found errors it can't repair

silasqwerty1

Member
Joined
Sep 1, 2015
Posts
15
Hello! SFC found errors it can't repair on my 64 bit windows 7 home premium desktop, and SFCfix told me that it found "CBS & SFC total detected corruption count: 2" and everything else said 0. Full log from SFCfix:



"SFCFix version 2.4.5.0 by niemiro.
Start time: 2015-09-01 16:10:56.465
Microsoft Windows 7 Service Pack 1 - amd64
Not using a script file.








AutoAnalysis::
SUMMARY: Some corruptions could not be fixed automatically. Seek advice from helper or sysnative.com.
CBS & SFC total detected corruption count: 2
CBS & SFC total unimportant corruption count: 0
CBS & SFC total fixed corruption count: 0
SURT total detected corruption count: 0
SURT total unimportant corruption count: 0
SURT total fixed corruption count: 0
AutoAnalysis:: directive completed successfully.








Successfully processed all directives.
SFCFix version 2.4.5.0 by niemiro has completed.
Currently storing 3 datablocks.
Finish time: 2015-09-01 16:11:17.680
----------------------EOF-----------------------"

Please help.
 
Hello silasqwerty1, welcome to Sysnative!

Let's have a look at your logs:

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. [sfcfixdownload]Download SFCFix[/sfcfixdownload] (by niemiro) and save this to your Desktop.
  2. Download the attached file, SFCFixScript.txt, and save this to your Desktop. Ensure that this file is named SFCFixScript.txt - 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 SFCFixScript.txt.
  5. Drag the file SFCFixScript.txt onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a log should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.

https://dl.dropboxusercontent.com/u...ts/~Generic/Collect/CBS/SFCFixScript.txt?dl=1

Tom
 
Your SFC log wasn't there, it must have been archived. Can you run SFC again please?

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.
 
Woah 0_0 that logbot thing is creepy :p but that's the thing all right! I didn't even have to post it. But just for reference, the logfile it generated on my computer just gave me some stats like program version, computer type etc. and said "Collect:: directive completed successfully. " So I assume it did it's job via logbot. That is mega creepy though.
 
Re: Logfile submission from silasqwerty1

Oops sorry didn't read your thing wait a min. OK I am rerunning SFC.
 
Hi silasqwerty1,

Well here is your only error:

Code:
2015-09-02 12:24:13, Info                  CSI    00000339 [SR] Cannot verify component files for Microsoft.VC80.MFC, Version = 8.0.50727.42, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:1fc8b3b9a1e18e3b}, Type = [l:10{5}]"win32", TypeName neutral, PublicKey neutral, manifest is damaged (FALSE)

Can you download and install the System Update Readiness Tool (SURT) please?

https://www.microsoft.com/en-in/download/details.aspx?id=20858

When it finishes, copy and paste the contents of this log into your next post:

C:\Windows\Logs\CBS\CheckSUR.persist.log

Tom
 
Hi silasqwerty1,

There lies the problem:

Code:
=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2015-09-03 13:50

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store
(f)	CSI Manifest Missing	0x00000002	x86_policy.8.0.microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.42_none_54c11df268b7c6d9.manifest	x86_policy.8.0.microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.42_none_54c11df268b7c6d9	
(f)	CSI Manifest Missing	0x00000002	x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.42_none_db5f52fb98cb24ad.manifest	x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.42_none_db5f52fb98cb24ad	
(f)	CSI Manifest Missing	0x00000002	x86_policy.8.0.microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.42_none_5c4003bc63e949f6.manifest	x86_policy.8.0.microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.42_none_5c4003bc63e949f6	
(f)	CSI Manifest Missing	0x00000002	x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.42_none_d6c3e7af9bae13a2.manifest	x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.42_none_d6c3e7af9bae13a2	

Summary:
Seconds executed: 2096
 Found 4 errors
  CSI Manifest Missing Total count: 4

Unavailable repair files:
	winsxs\manifests\x86_policy.8.0.microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.42_none_54c11df268b7c6d9.manifest
	winsxs\manifests\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.42_none_db5f52fb98cb24ad.manifest
	winsxs\manifests\x86_policy.8.0.microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.42_none_5c4003bc63e949f6.manifest
	winsxs\manifests\x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.42_none_d6c3e7af9bae13a2.manifest

Windows Update Package Replacement

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. Please download the attached file, Packs.zip and save this to your Desktop.
  2. Right-click on the file and select Extract All...
  3. Tick the box labelled Show extracted files when complete then click Extract
  4. A window will open showing two folders, Manifests and Packages
  5. Open the Manifests folder and copy the files into the following folder (if there are any files)

    C:\Windows\Temp\CheckSur\Winsxs\Manifests

  6. Open the Packages folder and copy the files into the following folder (if there are any files)

    C:\Windows\Temp\CheckSur\Servicing\Packages

  7. Run the System Update Readiness Tool (SURT) again.
  8. When the SURT finishes installing, copy (Ctrl + C) and paste (Ctrl + V) the contents of the SURT log into your next post please:

    C:\Windows\Logs\CBS\CheckSUR.persist.log

https://dl.dropboxusercontent.com/u/16537616/Fixes/SURT/silasqwerty1/Packs.zip

Tom
 
Well, the folders you specified don't exist. I don't have C:\Windows\Temp\CheckSur If I rerun SURT will the folder be there? Or is there another place that I can put the files?
 
I decided to rerun the SURT, and although it is still running, I notice the folder you specified is there, BUT I will wait till the program is done before I stick anything in there. I am not too techy but I have a feeling that would not turn out well :p
 
I decided to rerun the SURT, and although it is still running, I notice the folder you specified is there, BUT I will wait till the program is done before I stick anything in there. I am not too techy but I have a feeling that would not turn out well :p

I'm very glad you thought this :p To be honest, I don't know what would happen but I do know that the SURT wouldn't be expecting it.
 
Well, that's nice. It says now that it found 11 errors! It also that it fixed four. Look for yourself:

Code:
[/COLOR]

=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2015-09-04 11:55


Checking Windows Servicing Packages


Checking Package Manifests and Catalogs


Checking Package Watchlist


Checking Component Watchlist


Checking Packages


Checking Component Store
(f)	CSI Manifest Missing	0x00000002	x86_policy.8.0.microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.42_none_54c11df268b7c6d9.manifest	x86_policy.8.0.microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.42_none_54c11df268b7c6d9	
(f)	CSI Manifest Missing	0x00000002	x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.42_none_db5f52fb98cb24ad.manifest	x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.42_none_db5f52fb98cb24ad	
(f)	CSI Manifest Missing	0x00000002	x86_policy.8.0.microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.42_none_5c4003bc63e949f6.manifest	x86_policy.8.0.microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.42_none_5c4003bc63e949f6	
(f)	CSI Manifest Missing	0x00000002	x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.42_none_d6c3e7af9bae13a2.manifest	x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.42_none_d6c3e7af9bae13a2	


Summary:
Seconds executed: 1829
 Found 4 errors
  CSI Manifest Missing Total count: 4


Unavailable repair files:
	winsxs\manifests\x86_policy.8.0.microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.42_none_54c11df268b7c6d9.manifest
	winsxs\manifests\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.42_none_db5f52fb98cb24ad.manifest
	winsxs\manifests\x86_policy.8.0.microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.42_none_5c4003bc63e949f6.manifest
	winsxs\manifests\x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.42_none_d6c3e7af9bae13a2.manifest






=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2015-09-04 12:32


Checking Windows Servicing Packages


Checking Package Manifests and Catalogs


Checking Package Watchlist


Checking Component Watchlist


Checking Packages


Checking Component Store
(f)	CSI Manifest Missing	0x00000002	x86_policy.8.0.microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.42_none_54c11df268b7c6d9.manifest	x86_policy.8.0.microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.42_none_54c11df268b7c6d9	
(fix)	CSI Manifest Missing	CSI File Replaced	File: x86_policy.8.0.microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.42_none_54c11df268b7c6d9.manifest From: C:\Windows\CheckSur\v1.0\windows6.1-7601-x64-clientcab4.cab
(f)	CSI Manifest Missing	0x00000002	x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.42_none_db5f52fb98cb24ad.manifest	x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.42_none_db5f52fb98cb24ad	
(fix)	CSI Manifest Missing	CSI File Replaced	File: x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.42_none_db5f52fb98cb24ad.manifest From: C:\Windows\CheckSur\v1.0\windows6.1-7601-x64-clientcab4.cab
(f)	CSI Payload File Missing	0x00000000	msvcr80.dll	x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.42_none_db5f52fb98cb24ad	
(f)	CSI Payload File Missing	0x00000000	msvcp80.dll	x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.42_none_db5f52fb98cb24ad	
(f)	CSI Payload File Missing	0x00000000	msvcm80.dll	x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.42_none_db5f52fb98cb24ad	
(f)	CSI Manifest Missing	0x00000002	x86_policy.8.0.microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.42_none_5c4003bc63e949f6.manifest	x86_policy.8.0.microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.42_none_5c4003bc63e949f6	
(fix)	CSI Manifest Missing	CSI File Replaced	File: x86_policy.8.0.microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.42_none_5c4003bc63e949f6.manifest From: C:\Windows\CheckSur\v1.0\windows6.1-7601-x64-clientcab4.cab
(f)	CSI Manifest Missing	0x00000002	x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.42_none_d6c3e7af9bae13a2.manifest	x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.42_none_d6c3e7af9bae13a2	
(fix)	CSI Manifest Missing	CSI File Replaced	File: x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.42_none_d6c3e7af9bae13a2.manifest From: C:\Windows\CheckSur\v1.0\windows6.1-7601-x64-clientcab4.cab
(f)	CSI Payload File Missing	0x00000000	mfcm80.dll	x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.42_none_d6c3e7af9bae13a2	
(f)	CSI Payload File Missing	0x00000000	mfc80u.dll	x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.42_none_d6c3e7af9bae13a2	
(f)	CSI Payload File Missing	0x00000000	mfc80.dll	x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.42_none_d6c3e7af9bae13a2	
(f)	CSI Payload File Missing	0x00000000	mfcm80u.dll	x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.42_none_d6c3e7af9bae13a2	


Summary:
Seconds executed: 1699
 Found 11 errors
 Fixed 4 errors
  CSI Manifest Missing Total count: 4
  Fixed: CSI Manifest Missing.  Total count: 4
  CSI Payload File Missing Total count: 7


[COLOR=#000000]
 

Attachments

Now, to understand this better, I'll assume these payload errors are lesser errors? I mean that they are secondary, and are essentially suberrors to the original four manifest file errors? And also, where did you get the manifest files from? Did they come from your computer, or from an official microsoft source (I know there is a similar source for windows updates that you can download them directly from MS)?
 
Well, that's nice. It says now that it found 11 errors! It also that it fixed four. Look for yourself:

Code:
[/COLOR]

=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2015-09-04 11:55


Checking Windows Servicing Packages


Checking Package Manifests and Catalogs


Checking Package Watchlist


Checking Component Watchlist


Checking Packages


Checking Component Store
(f)	CSI Manifest Missing	0x00000002	x86_policy.8.0.microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.42_none_54c11df268b7c6d9.manifest	x86_policy.8.0.microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.42_none_54c11df268b7c6d9	
(f)	CSI Manifest Missing	0x00000002	x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.42_none_db5f52fb98cb24ad.manifest	x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.42_none_db5f52fb98cb24ad	
(f)	CSI Manifest Missing	0x00000002	x86_policy.8.0.microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.42_none_5c4003bc63e949f6.manifest	x86_policy.8.0.microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.42_none_5c4003bc63e949f6	
(f)	CSI Manifest Missing	0x00000002	x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.42_none_d6c3e7af9bae13a2.manifest	x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.42_none_d6c3e7af9bae13a2	


Summary:
Seconds executed: 1829
 Found 4 errors
  CSI Manifest Missing Total count: 4


Unavailable repair files:
	winsxs\manifests\x86_policy.8.0.microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.42_none_54c11df268b7c6d9.manifest
	winsxs\manifests\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.42_none_db5f52fb98cb24ad.manifest
	winsxs\manifests\x86_policy.8.0.microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.42_none_5c4003bc63e949f6.manifest
	winsxs\manifests\x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.42_none_d6c3e7af9bae13a2.manifest






=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2015-09-04 12:32


Checking Windows Servicing Packages


Checking Package Manifests and Catalogs


Checking Package Watchlist


Checking Component Watchlist


Checking Packages


Checking Component Store
(f)	CSI Manifest Missing	0x00000002	x86_policy.8.0.microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.42_none_54c11df268b7c6d9.manifest	x86_policy.8.0.microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.42_none_54c11df268b7c6d9	
(fix)	CSI Manifest Missing	CSI File Replaced	File: x86_policy.8.0.microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.42_none_54c11df268b7c6d9.manifest From: C:\Windows\CheckSur\v1.0\windows6.1-7601-x64-clientcab4.cab
(f)	CSI Manifest Missing	0x00000002	x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.42_none_db5f52fb98cb24ad.manifest	x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.42_none_db5f52fb98cb24ad	
(fix)	CSI Manifest Missing	CSI File Replaced	File: x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.42_none_db5f52fb98cb24ad.manifest From: C:\Windows\CheckSur\v1.0\windows6.1-7601-x64-clientcab4.cab
(f)	CSI Payload File Missing	0x00000000	msvcr80.dll	x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.42_none_db5f52fb98cb24ad	
(f)	CSI Payload File Missing	0x00000000	msvcp80.dll	x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.42_none_db5f52fb98cb24ad	
(f)	CSI Payload File Missing	0x00000000	msvcm80.dll	x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.42_none_db5f52fb98cb24ad	
(f)	CSI Manifest Missing	0x00000002	x86_policy.8.0.microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.42_none_5c4003bc63e949f6.manifest	x86_policy.8.0.microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.42_none_5c4003bc63e949f6	
(fix)	CSI Manifest Missing	CSI File Replaced	File: x86_policy.8.0.microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.42_none_5c4003bc63e949f6.manifest From: C:\Windows\CheckSur\v1.0\windows6.1-7601-x64-clientcab4.cab
(f)	CSI Manifest Missing	0x00000002	x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.42_none_d6c3e7af9bae13a2.manifest	x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.42_none_d6c3e7af9bae13a2	
(fix)	CSI Manifest Missing	CSI File Replaced	File: x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.42_none_d6c3e7af9bae13a2.manifest From: C:\Windows\CheckSur\v1.0\windows6.1-7601-x64-clientcab4.cab
(f)	CSI Payload File Missing	0x00000000	mfcm80.dll	x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.42_none_d6c3e7af9bae13a2	
(f)	CSI Payload File Missing	0x00000000	mfc80u.dll	x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.42_none_d6c3e7af9bae13a2	
(f)	CSI Payload File Missing	0x00000000	mfc80.dll	x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.42_none_d6c3e7af9bae13a2	
(f)	CSI Payload File Missing	0x00000000	mfcm80u.dll	x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.42_none_d6c3e7af9bae13a2	


Summary:
Seconds executed: 1699
 Found 11 errors
 Fixed 4 errors
  CSI Manifest Missing Total count: 4
  Fixed: CSI Manifest Missing.  Total count: 4
  CSI Payload File Missing Total count: 7


[COLOR=#000000]

Now, to understand this better, I'll assume these payload errors are lesser errors? I mean that they are secondary, and are essentially suberrors to the original four manifest file errors? And also, where did you get the manifest files from? Did they come from your computer, or from an official microsoft source (I know there is a similar source for windows updates that you can download them directly from MS)?

Correct, the manifests contain hashes of those files and without the manifests, SFC is unable to verify the file. Now we have replaced the manifests, SFC and SURT are able to 'see' these files and know that they are missing. Notice how the filenames of the manifests that we replaced are the same as the directory names of the files SURT has just flagged:

Code:
	winsxs\manifests\x86_policy.8.0.microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.42_none_54c11df268b7c6d9.manifest
	winsxs\manifests\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.42_none_db5f52fb98cb24ad.manifest
	winsxs\manifests\x86_policy.8.0.microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.42_none_5c4003bc63e949f6.manifest
	winsxs\manifests\x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.42_none_d6c3e7af9bae13a2.manifest

Code:
(f)	CSI Payload File Missing	0x00000000	msvcr80.dll	x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.42_none_db5f52fb98cb24ad	
(f)	CSI Payload File Missing	0x00000000	msvcp80.dll	x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.42_none_db5f52fb98cb24ad	
(f)	CSI Payload File Missing	0x00000000	msvcm80.dll	x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.42_none_db5f52fb98cb24ad	
(f)	CSI Payload File Missing	0x00000000	mfcm80.dll	x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.42_none_d6c3e7af9bae13a2	
(f)	CSI Payload File Missing	0x00000000	mfc80u.dll	x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.42_none_d6c3e7af9bae13a2	
(f)	CSI Payload File Missing	0x00000000	mfc80.dll	x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.42_none_d6c3e7af9bae13a2	
(f)	CSI Payload File Missing	0x00000000	mfcm80u.dll	x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.42_none_d6c3e7af9bae13a2

It's all very interconnected, but this is the end of the chain so to speak and fixing these files should be the last thing we have to do.

Those manifests were extracted from an update: https://www.microsoft.com/en-in/download/details.aspx?id=3387

All of the helpers here, including me, have huge collections of these files so we don't have to extract them every time but I'm current abroad and working from my laptop so I had to extract these again.

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.

https://dl.dropboxusercontent.com/u/16537616/Fixes/SFCFix/Scripts/silasqwerty1/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 attach this to your next post.

I would also like you to run the SURT and post the CheckSUR.persist.log again please.

Tom
 
OK due to time limitations, I think I can only the SFCFIX and the SFC for now. Here is the log for the SFCfix:
Code:
SFCFix version 2.4.5.0 by niemiro.Start time: 2015-09-05 09:08:57.016
Microsoft Windows 7 Service Pack 1 - amd64
Using .zip script file at C:\Users\Angelica\Desktop\SFCFix.zip [0]








PowerCopy::
Successfully took permissions for file or folder C:\Windows\winsxs\x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.42_none_d6c3e7af9bae13a2
Successfully took permissions for file or folder C:\Windows\winsxs\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.42_none_db5f52fb98cb24ad


Successfully copied file C:\Users\Angelica\AppData\Local\niemiro\Archive\winsxs\x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.42_none_d6c3e7af9bae13a2\mfc80.dll to C:\Windows\winsxs\x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.42_none_d6c3e7af9bae13a2\mfc80.dll.
Successfully copied file C:\Users\Angelica\AppData\Local\niemiro\Archive\winsxs\x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.42_none_d6c3e7af9bae13a2\mfc80u.dll to C:\Windows\winsxs\x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.42_none_d6c3e7af9bae13a2\mfc80u.dll.
Successfully copied file C:\Users\Angelica\AppData\Local\niemiro\Archive\winsxs\x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.42_none_d6c3e7af9bae13a2\mfcm80.dll to C:\Windows\winsxs\x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.42_none_d6c3e7af9bae13a2\mfcm80.dll.
Successfully copied file C:\Users\Angelica\AppData\Local\niemiro\Archive\winsxs\x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.42_none_d6c3e7af9bae13a2\mfcm80u.dll to C:\Windows\winsxs\x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.42_none_d6c3e7af9bae13a2\mfcm80u.dll.
Successfully copied file C:\Users\Angelica\AppData\Local\niemiro\Archive\winsxs\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.42_none_db5f52fb98cb24ad\msvcm80.dll to C:\Windows\winsxs\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.42_none_db5f52fb98cb24ad\msvcm80.dll.
Successfully copied file C:\Users\Angelica\AppData\Local\niemiro\Archive\winsxs\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.42_none_db5f52fb98cb24ad\msvcp80.dll to C:\Windows\winsxs\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.42_none_db5f52fb98cb24ad\msvcp80.dll.
Successfully copied file C:\Users\Angelica\AppData\Local\niemiro\Archive\winsxs\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.42_none_db5f52fb98cb24ad\msvcr80.dll to C:\Windows\winsxs\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.42_none_db5f52fb98cb24ad\msvcr80.dll.


Successfully restored ownership for C:\Windows\winsxs\x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.42_none_d6c3e7af9bae13a2
Successfully restored permissions on C:\Windows\winsxs\x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.42_none_d6c3e7af9bae13a2
Successfully restored ownership for C:\Windows\winsxs\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.42_none_db5f52fb98cb24ad
Successfully restored permissions on C:\Windows\winsxs\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.42_none_db5f52fb98cb24ad
PowerCopy:: directive completed successfully.








Successfully processed all directives.
SFCFix version 2.4.5.0 by niemiro has completed.
Currently storing 5 datablocks.
Finish time: 2015-09-05 09:10:07.980
Script hash: V6HooVg8mWDSvAVQK1ZT1kwVOiahgUj6sYYCj94KKMs=
----------------------EOF-----------------------[COLOR=#161616]

Running SFC now.[/COLOR]
 
No integrity violations found!!!!! WOOP! But the log was too big for uploading. I'm hoping we don't need it now though :p And even though it's fixed I'll try and run SURT anyway. But assuming that finds no issues, we are in the clear! I'll give you the status report in a good couple hours, but I think it's safe to say you don't have to worry about this anymore! Thanks slightly in advance for fixing my problem!
 

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

Back
Top