SFC log lists 4 "corrupted" files, or maybe not - Altering Core Files


  1. Posts : 10
    Windows 7 Home Premium 64bit
       #1

    SFC log lists 4 "corrupted" files, or maybe not - Altering Core Files


    I just ran SFC first time. It reports 4 "corrupted" core files. The machine is one month old, directly from Dell. No apparent previous or current issues. Looking at the report, the "corrupted" files appear related to gpedit. As you see to the left, my machine is 7 x64 home premium, which doesn't come with gpedit, but is compatible, so I downloaded it from MS/installed it last week . (Gpedit works fine and I plan to use it.)

    The SFC issues all look more or less like this:

    2012-12-25 18:10:43, Info CSI 0000026e [SR] Cannot repair member file [l:20{10}]"gpedit.dll" of Microsoft-Windows-GroupPolicy-Admin-Gpedit, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {deleted}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

    The 4 "problem" files are gpedit.dll, gptext.dll, fde.dll, fdeploy.dll. The fdxxx files are apparently client side extensions pf group policy edit, so I'm assuming they were part of the gpedit install. I'm also assuming the "hash mismatch" is because these files aren't in the store, so there's no hash in the store to match them.

    My questions: 1) after installing gpedit, or, for that matter, installing/altering anything in the core files, does sfc then report an "error" as it did in this case? And more importantly, 2) once I reboot, will gpedit be uninstalled, because sfc didn't like it? And most important, 3) if I change ANYTHING in the core, will running sfc change it back/remove the change? For example, on startup, if I change "welcome" on the welcome screen to, for example, "Hi there, big boy!", would sfc return it to "welcome" on reboot?

    This isn't trivial; I'm intending to install an sdk soon. I'm pretty sure it adds files to the core. The sdk is 5 gigs. I don't want to have to reinstall it because SFC doesn't like it.

    The next question, of course, is how to get SFC to accept changes in the core? For example, is there a way to get gpedit into the store so SFC then recognizes it?

    I get the point of SFC, so disabling it to avoid losing intentional core changes isn't a good option, in my opinion. Must be a better solution.
      My Computer

  2.    #2

    Probably because a factory pre-install is inherently corrupt to begin with, larded with bloatware and duplicate utilties which throttle Win7's native state. That's why most tech enthusiasts prefer to Clean Reinstall - Factory OEM Windows 7 without the bloatware. If you follow the steps and stick with the tools and methods given, you'll get and keep a perfect install.

    At the minimum I'd Clean Up Factory Bloatware which requires running sfc /scannow to lean up the corruption caused both by the bloatware and by its uninstall.

    Otherwise if SFC can't fix the system files the next step if you had a normal install (which you don't) is to run Repair Install. In rare cases that can even sort the corruption caused by factory pre-install, but it can also make an even bigger mess trying to set it right, which it isn't at all.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 02:28.
Find Us