[SOLVED] [Win7SP1] SFCFix not finished

A

AMG61

New member
Joined
Feb 25, 2017
Posts
2
Sorry, not sure where to post this. Have been having some instability issue. Ran SFC SCANNOW which found and fixed some stuff, but not all. So I downloaded and ran SFCFix and all but 4 files seemed to be fixed, I am guessing. I don't have my original Windows 7 DVD, no idea where it is. But here is the SFCFix log. The original scannow cbs log is too big to attach here

SFCFix version 3.0.0.0 by niemiro.
Start time: 2017-02-25 15:49:09.094
Microsoft Windows 7 Service Pack 1 - amd64
Not using a script file.








AutoAnalysis::
CORRUPT: C:\Windows\winsxs\x86_microsoft-windows-fdeploy_31bf3856ad364e35_6.1.7601.17514_none_e1bcfc28af006dea\fdeploy.dll
CORRUPT: C:\Windows\winsxs\x86_microsoft-windows-fde_31bf3856ad364e35_6.1.7601.17514_none_aa136561b9ed4ae4\fde.dll
CORRUPT: C:\Windows\winsxs\x86_microsoft-windows-g..policy-admin-gpedit_31bf3856ad364e35_6.1.7600.16385_none_ce0882b8c63afdf6\gpedit.dll
CORRUPT: C:\Windows\winsxs\x86_microsoft-windows-grouppolicy-gptext_31bf3856ad364e35_6.1.7600.16385_none_372622adf05a6587\gptext.dll




SUMMARY: Some corruptions could not be fixed automatically. Seek advice from helper or sysnative.com.
CBS & SFC total detected corruption count: 4
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.






Failed to generate a complete zip file. Upload aborted.




SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2017-02-25 16:04:21.724
----------------------EOF-----------------------

I can attach it as a txt, and could attach the original scannow log, too that the scnfix worked on. thanks
 

Attachments

Hi and welcome to Sysnative. Please start with the following.

Step#1 - 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. If you still have this on your desktop from downloading previously, you don't need to re-download.
  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
 

Attachments

I did what you said, and before I paste the results, let me say I did a chkdsk which was absolutely normal and also a checksur.log which was ok, too. Is it possible, those 4 "corrupt" files are meaningless and often found in many people's "aberrant" sfcfix logs, etc??? System is running well, and of course, i don't want to make things WORSE, but do want a smooth running machine, though it looks maybe that whatever you suggested might have fixed everything.

Here is the result of your request above:


SFCFix version 3.0.0.0 by niemiro.
Start time: 2017-02-27 21:24:56.064
Microsoft Windows 7 Service Pack 1 - amd64
Using .zip script file at C:\Users\AMG OFFICE 661\Desktop\SFCFix.zip [0]








PowerCopy::
Successfully took permissions for file or folder C:\Windows\Winsxs\x86_microsoft-windows-grouppolicy-gptext_31bf3856ad364e35_6.1.7600.16385_none_372622adf05a6587\gptext.dll
Successfully took permissions for file or folder C:\Windows\Winsxs\x86_microsoft-windows-g..policy-admin-gpedit_31bf3856ad364e35_6.1.7600.16385_none_ce0882b8c63afdf6\gpedit.dll
Successfully took permissions for file or folder C:\Windows\Winsxs\x86_microsoft-windows-fde_31bf3856ad364e35_6.1.7601.17514_none_aa136561b9ed4ae4\fde.dll
Successfully took permissions for file or folder C:\Windows\Winsxs\x86_microsoft-windows-fdeploy_31bf3856ad364e35_6.1.7601.17514_none_e1bcfc28af006dea\fdeploy.dll


Successfully copied file C:\Users\AMG OFFICE 661\AppData\Local\niemiro\Archive\Winsxs\x86_microsoft-windows-grouppolicy-gptext_31bf3856ad364e35_6.1.7600.16385_none_372622adf05a6587\gptext.dll to C:\Windows\Winsxs\x86_microsoft-windows-grouppolicy-gptext_31bf3856ad364e35_6.1.7600.16385_none_372622adf05a6587\gptext.dll.
Successfully copied file C:\Users\AMG OFFICE 661\AppData\Local\niemiro\Archive\Winsxs\x86_microsoft-windows-g..policy-admin-gpedit_31bf3856ad364e35_6.1.7600.16385_none_ce0882b8c63afdf6\gpedit.dll to C:\Windows\Winsxs\x86_microsoft-windows-g..policy-admin-gpedit_31bf3856ad364e35_6.1.7600.16385_none_ce0882b8c63afdf6\gpedit.dll.
Successfully copied file C:\Users\AMG OFFICE 661\AppData\Local\niemiro\Archive\Winsxs\x86_microsoft-windows-fde_31bf3856ad364e35_6.1.7601.17514_none_aa136561b9ed4ae4\fde.dll to C:\Windows\Winsxs\x86_microsoft-windows-fde_31bf3856ad364e35_6.1.7601.17514_none_aa136561b9ed4ae4\fde.dll.
Successfully copied file C:\Users\AMG OFFICE 661\AppData\Local\niemiro\Archive\Winsxs\x86_microsoft-windows-fdeploy_31bf3856ad364e35_6.1.7601.17514_none_e1bcfc28af006dea\fdeploy.dll to C:\Windows\Winsxs\x86_microsoft-windows-fdeploy_31bf3856ad364e35_6.1.7601.17514_none_e1bcfc28af006dea\fdeploy.dll.


Successfully restored ownership for C:\Windows\Winsxs\x86_microsoft-windows-grouppolicy-gptext_31bf3856ad364e35_6.1.7600.16385_none_372622adf05a6587\gptext.dll
Successfully restored permissions on C:\Windows\Winsxs\x86_microsoft-windows-grouppolicy-gptext_31bf3856ad364e35_6.1.7600.16385_none_372622adf05a6587\gptext.dll
Successfully restored ownership for C:\Windows\Winsxs\x86_microsoft-windows-g..policy-admin-gpedit_31bf3856ad364e35_6.1.7600.16385_none_ce0882b8c63afdf6\gpedit.dll
Successfully restored permissions on C:\Windows\Winsxs\x86_microsoft-windows-g..policy-admin-gpedit_31bf3856ad364e35_6.1.7600.16385_none_ce0882b8c63afdf6\gpedit.dll
Successfully restored ownership for C:\Windows\Winsxs\x86_microsoft-windows-fde_31bf3856ad364e35_6.1.7601.17514_none_aa136561b9ed4ae4\fde.dll
Successfully restored permissions on C:\Windows\Winsxs\x86_microsoft-windows-fde_31bf3856ad364e35_6.1.7601.17514_none_aa136561b9ed4ae4\fde.dll
Successfully restored ownership for C:\Windows\Winsxs\x86_microsoft-windows-fdeploy_31bf3856ad364e35_6.1.7601.17514_none_e1bcfc28af006dea\fdeploy.dll
Successfully restored permissions on C:\Windows\Winsxs\x86_microsoft-windows-fdeploy_31bf3856ad364e35_6.1.7601.17514_none_e1bcfc28af006dea\fdeploy.dll
PowerCopy:: directive completed successfully.








Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 4 datablocks.
Finish time: 2017-02-27 21:24:58.023
Script hash: jcjuPh+/acIPLC8kUgVCFeUxciz7+tUL5aitBtcCsSM=
----------------------EOF-----------------------
 
Is it possible, those 4 "corrupt" files are meaningless and often found in many people's "aberrant" sfcfix logs, etc???
Click to expand...
It's not normal to see any corruption in the logs. Now saying that I have seen these particular files show in a handful of logs so you are correct that it likely wasn't impacting your machine.

So at this point you should be good to go with no corruption. Take care.
 
You must log in or register to reply here.

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

Back
Top