SFCFix fails to fix "Some" corrupt files - win 8.1

Hello dafaddah, welcome to Sysnative!

Have you run a tool to enable gpedit on your version of Windows? I'm fairly confident you have and this is what's caused the 'corruption'. Windows knows the files are tampered with, but they aren't corrupt in the normal sense and are instead patched (*) to allow gpedit to run on unsupported versions. I assume this is illegal and I can't help you with anything to do with this, but I can help you undo it if you want to.

Tom

(*) Not sure if they're patched or just copied from another version of Windows. I seem to think it's the latter.
 
Tom,
While I never ran any tool to enable GPEdit to the best of my knowledge, GPEDit is installed and has run (been modified) many times since I got the machine (refurbished from Gateway). Evidently it runs every time I set up or modify my HOME network so I can't see how that would be illegal.
dafaddah
 
Hi dafaddah,

Okay, thanks. This is really strange then, maybe it's just coincidence. There are various tools to enable gpedit on unsupported versions of Windows (like this) and the files affected are fd.dll, fdeploy.dll, gptext.dll and gpedit.dll. Your SFCFix log shows three of those four, hence my previous post.

I can't see any errors in the CBS log so I would like to see a new SFC scan before we go ahead and fix this:

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.

Tom
 
Tom,
I have a command prompt shortcut on my desktop so I started it that way as Administrator. Starting sfc the first time returned a message that I needed to restart the PC so I did which installed an update before restarting.
After restart I ran the sfc and it seemed to run without anything unexpected happening. I then did the file copy as you indicated. I've attached the cbs.txt file that showed up on my desktop. There was no message this time that there were no repairs.
I'm still getting slow operation an "Not Responding" sometimes.
I hope this is what you need.
dafaddah
View attachment cbs.txt
 
Tom,
I have been working on my machine and I've installed some 8.1 updates, etc. I have also started to uninstall some stuff I don't need or use very often. SFC is no longer giving me any cannot fix messages.
Thanks for your help but I think I will continue to clean up the machine for a while before I need any assistance again.
All the best,
dafaddah
 
Hi dafaddah,

Sorry for the delay in getting back to you, I've been so busy over the past few days.

The latest SFC run shows that it fixed the 3 files:

Code: 
2015-07-16 09:49:56, Info                  CSI    00000aec Hashes for file member \??\C:\WINDOWS\SysWOW64\gptext.dll do not match actual file [l:20{10}]"gptext.dll" :
  Found: {l:32 b:4R/wpzngnfdc0a94M7qP6Hg+i5N+LV89wlqPbSNLqTs=} Expected: {l:32 b:4w6KwVqXyc0GyUt1Dq0acWODMw0h3KXUqCEb6JuL0Ns=}
2015-07-16 09:49:56, Info                  CSI    00000aed [SR] Repairing corrupted file [ml:48{24},l:46{23}]"\??\C:\WINDOWS\SysWOW64"\[l:20{10}]"gptext.dll" from store
2015-07-16 09:49:56, Info                  CSI    00000aee Hashes for file member \??\C:\WINDOWS\SysWOW64\fdeploy.dll do not match actual file [l:22{11}]"fdeploy.dll" :
  Found: {l:32 b:X2Mxr15BWaSKXy2mybUslwVk9Y/FqInLy5D57coBHZA=} Expected: {l:32 b:hJ0Gf6MDvKCcvs4i3JwCRxIVLK46U3ZDJCQcYaxhbNs=}
2015-07-16 09:49:56, Info                  CSI    00000aef [SR] Repairing corrupted file [ml:48{24},l:46{23}]"\??\C:\WINDOWS\SysWOW64"\[l:22{11}]"fdeploy.dll" from store
2015-07-16 09:49:56, Info                  CSI    00000af0 Hashes for file member \??\C:\WINDOWS\SysWOW64\fde.dll do not match actual file [l:14{7}]"fde.dll" :
  Found: {l:32 b:ofJrYBMvfbcRFAtPFwvTqckgU78Xi+9tWAnhLEg79/w=} Expected: {l:32 b:RDfb9ZHLzHBMXedC6rq+keFnb/6XjEqFneCU8mZgRTM=}
2015-07-16 09:49:56, Info                  CSI    00000af1 [SR] Repairing corrupted file [ml:48{24},l:46{23}]"\??\C:\WINDOWS\SysWOW64"\[l:14{7}]"fde.dll" from store

I can't see any other issues so you should be good to go, but if you run into any more problems feel free to post back here and we can look into them.

Is your computer still running slow?

Tom
 
Tom,
I think that after the clean up I did eliminating several Outlook addons plus other junk, disabling some FireFox stuff, installing a backlog of windows updates and powering off the PC with the plug pulled for a while things have improved 100%.
I think getting rid of iCloud had a lot to do with it, too.
Thanks again for your help.
dafaddah
 
tom982 said:
Have you run a tool to enable gpedit on your version of Windows? I'm fairly confident you have and this is what's caused the 'corruption'. Windows knows the files are tampered with, but they aren't corrupt in the normal sense and are instead patched (*) to allow gpedit to run on unsupported versions. I assume this is illegal and I can't help you with anything to do with this, but I can help you undo it if you want to.

Tom

(*) Not sure if they're patched or just copied from another version of Windows. I seem to think it's the latter.
Click to expand...


Hello Tom,

I have the same issue with 4 "corrupted" files running SFC on Windows 10 Home. I have installed GPEDIT.msc some time ago, probably on Windows 8.1 before upgrading to 10, and I'd like to remove it (it doesn't work anyways).

How can I do?

Here my CBS.log


Checking System Update Readiness.

(p) CSI Payload Corrupt x86_microsoft-windows-grouppolicy-gptext_31bf3856ad364e35_10.0.10586.0_none_67b6c95f81009211\gptext.dll
(p) CSI Payload Corrupt x86_microsoft-windows-g..policy-admin-gpedit_31bf3856ad364e35_10.0.10586.0_none_fe99296a56e12a80\gpedit.dll
(p) CSI Payload Corrupt x86_microsoft-windows-fdeploy_31bf3856ad364e35_10.0.10586.0_none_101c8f1242b816da\fdeploy.dll
(p) CSI Payload Corrupt x86_microsoft-windows-fde_31bf3856ad364e35_10.0.10586.0_none_d872f84b4da4f3d4\fde.dll

Summary:
Operation: Detect only
Operation result: 0x0
Last Successful Step: CSI store detection completes.
Total Detected Corruption: 4
CBS Manifest Corruption: 0
CBS Metadata Corruption: 0
CSI Manifest Corruption: 0
CSI Metadata Corruption: 0
CSI Payload Corruption: 4
Total Repaired Corruption: 0
CBS Manifest Repaired: 0
CSI Manifest Repaired: 0
CSI Payload Repaired: 0
CSI Store Metadata refreshed: True

Total Operation Time: 113 seconds.



Thanks
 
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