How to make SFC work again so that system files can be repaired (Build 10041)

Discussion in 'Windows 10' started by Jackalito, Mar 21, 2015.

  1. Jackalito

    Jackalito MDL Novice

    Mar 21, 2015
    22
    25
    0
    Hey everyone,

    I'm new to this forum, but I managed to make SFC work on Windows 10 build 10041, and I would like to share it with you guys.

    So, I've created a thread on Windows Insider's forums explaining the necessary steps to make SFC work in build 10041 and repair a bunch of system corrupted files after a fresh installation. By doing so, I've been able to make it work more stable. Here's the link to the aforementioned thread in case you want to have a look at it: (EDIT: I cannot post links or images yet).

    Anyway, here are the steps:

    Note: you will need the ISO for build 10041

    1. Mount the .ISO file by double clicking on it.

    2. Open 'Windows Powershell' or 'Command Prompt' with Admin privileges (right click -> Run as Administrator)

    3. Let's check the System Health first, by running these commands:

    3.1 dism /online /cleanup-image /scanhealth

    3.2 dism /online /cleanup-image /checkhealth

    3.3 dism /online /cleanup-image /restorehealth

    4. I'm sure that 3.3 will give you an error stating that it could not perform the task. And now it's when the mounted ISO comes into play. Let's specify the file from the ISO so that we can fix it. Run the following command: (Notice that X must be the drive letter on which your system has mounted the ISO)

    4.1 DISM /Online /Cleanup-Image /RestoreHealth /source:WIM:X:\Sources\Install.wim:1 /LimitAccess

    5. Now let's repair any damage in the system files, shall we?

    5.1 sfc /scannow

    Now it should work for you, guys! I hope this will help. My system seems more responsive since then. Please report if you encounter any problems following these instructions.
    I don't know if this solution will work on previous builds such as 9926, but I have the feeling it may.

    Regards! :biggrin:

    PS: This is a screenshot I took after running sfc/scannow for the second time in order to check everything was fine:
     

    Attached Files:

  2. WildByDesign

    WildByDesign MDL Addicted

    Sep 8, 2013
    654
    312
    30
    #2 WildByDesign, Mar 21, 2015
    Last edited by a moderator: Apr 20, 2017
    Welcome to MDL community, Jackalito. Thank you for joining the community and sharing this valuable information. This is something that has clearly plagued the Windows 10 Tech Preview builds for quite some time and it's fantastic to have a solution, particularly great that it is using legitimate Microsoft tools and techniques. I am still going through the steps of this process, but so far so good. Cheers!


    EDIT: Unfortunately, this method does not work for everyone.


    - dism /online /cleanup-image /scanhealth:
    This went through fully and completed.

    - dism /online /cleanup-image /checkhealth:
    This went through fully and completed.

    - dism /online /cleanup-image /restorehealth:
    This failed, giving error as expected.

    - DISM /Online /Cleanup-Image /RestoreHealth /source:WIM:E:\Sources\Install.wim:1 /LimitAccess:
    This went through fully and completed.

    - sfc /scannow:
    This failed with the error message in the code box below.

    Code:
    Beginning system scan.  This process will take some time.
    
    Beginning verification phase of system scan.
    Verification 8% complete.
    
    
    Windows Resource Protection could not perform the requested operation.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. fardeen

    fardeen MDL Member

    May 11, 2010
    182
    10
    10
    thanks worked fine for me :D :clap: :worthy:
     
  4. agent268

    agent268 MDL Junior Member

    Feb 20, 2012
    83
    24
    0
    So what was broken that required you to resort to SFC and DISM Image Repair? What did these tools end up repairing? Maybe knowing that will help shine light on the real problems and alternate ways to avoid it from the get go.
     
  5. Jackalito

    Jackalito MDL Novice

    Mar 21, 2015
    22
    25
    0
    #5 Jackalito, Mar 21, 2015
    Last edited by a moderator: Apr 20, 2017
    (OP)
    That's why I wanted to read some feedback. Too bad it may still be a non-go for some of you. Question: did you try using both Command Prompt and Windows Powershell? I used the latter and had no issues.

    Anyway, you could also follow the instructions of another forum user from Windows Insiders (colakid) I believe this is what you need to do if you do not have the file install.wim. Let me copy-paste here what he wrote in the thread I opened there:

    I have the feeling that some key windows system files get corrupted upon the installation process, hence the necessity of using the install.wim located inside the ISO instead of the one already sitting in our system after Windows has been installed.

    Thanks for the welcoming, guys! :biggrin:
     
  6. marek848

    marek848 MDL Junior Member

    Dec 26, 2014
    65
    19
    0
    Perfect 100% successful :clap:
     
  7. Jackalito

    Jackalito MDL Novice

    Mar 21, 2015
    22
    25
    0
    Guys, I've just learned something else. After a fresh reboot of Windows 10, I decided to give 'sfc /scannow' another go, just for the sake of it and guess what? The process got interrupted multiple times after roughly 5%. I managed to make it work again by running
    dism /online /cleanup-image /restorehealth

    orDISM /Online /Cleanup-Image /RestoreHealth /source:WIM:X:\Sources\Install.wim:1 /LimitAccess

    again. Then 'sfc /scannow' worked again flawlessly.

    I don't understand what's wrong with these builds. Are Microsoft guys changing something really elementary? Will this have anything to do with those changes I read about system compression?

    What do you guys think?
     
  8. SAM-R

    SAM-R MDL Guru

    Mar 21, 2015
    2,576
    1,636
    90
    Thank you. It worked 100% It found and fixed all of the corrupt files.
     
  9. agent268

    agent268 MDL Junior Member

    Feb 20, 2012
    83
    24
    0
    I think it would be beneficial to look at the CBS.log file and DISM.log file to see what's going on. That will tell us what SFC and DISM are repairing and why. Plus if they fail, a more detailed error code should be there for us to further diagnose this.
     
  10. ZaForD

    ZaForD MDL Expert

    Jan 26, 2008
    1,180
    176
    60
    Thanks gonna give a try now, see if it fixes my Metro app issues. ;)

    Could be down to the Debugging software that may still be running on the system.
    My guess is MS would class that running as a higher priority than if sfc works.
     
  11. Jackalito

    Jackalito MDL Novice

    Mar 21, 2015
    22
    25
    0
    You're right, but I don't think I posses enough knowledge to understand what I read at those log files. I'm still learning a lot of this stuff, to be honest.

    Maybe you're right. I honestly don't know.
     
  12. dudeluv

    dudeluv MDL Member

    Aug 7, 2012
    214
    43
    10
    Worked great for me, ran the commands in cmd admin mode :clap::clap:
     
  13. The Chief

    The Chief MDL Novice

    Nov 9, 2008
    35
    1
    0
    i did the same thing to mine repeated step 4.1 after mounting iso again after reboot then scannow worked again
     
  14. agent268

    agent268 MDL Junior Member

    Feb 20, 2012
    83
    24
    0
    If you can post up those log files, I would be more than happy to help look them over and explain what they say.
     
  15. sh4dow_cr4ft

    sh4dow_cr4ft MDL Novice

    Dec 21, 2009
    20
    3
    0
    #15 sh4dow_cr4ft, Mar 22, 2015
    Last edited: Mar 22, 2015
    I just looked over the logs on a fresh install, seems a lot of folders don't have the proper security settings... lol

    there are a lot like this :


    "000089c2 [DIRSD OWNER WARNING] Directory [ml:72{36},l:70{35}]"\??\C:\Windows\SysWOW64\DriverStore" is not owned but specifies SDDL in component Microsoft-Windows-DrvStore, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf345dad364e35}, Type neutral, TypeName neutral"

    after following the instructions here , sfc was able to complete the scan and repair the errors, thanks!
     
  16. geordiemark

    geordiemark MDL Junior Member

    Jan 28, 2009
    53
    1
    0
    this worked a treat thanks very much :)
     
  17. Andrw0830

    Andrw0830 MDL Novice

    Aug 28, 2013
    30
    1
    0
    Worked great for me too! First time without running the dism command, the sfc /scannow ran to 100% without stopping, but gave couldn't repair errors. Once I ran the dism command, it said it repaired the errors. Thanks again.
     
  18. Jackalito

    Jackalito MDL Novice

    Mar 21, 2015
    22
    25
    0
    But, they're kind of huge to examine. If you want, I can PM you the files DISM.log and CBS.log and have a look patiently, because trust me, you'll have to be patient to read them through :p

    I'm happy seeing more people being able to repair their system files :biggrin:

    Regards.
     
  19. abbodi1406

    abbodi1406 MDL KB0000001

    Feb 19, 2011
    7,668
    24,644
    240
    #19 abbodi1406, Mar 22, 2015
    Last edited by a moderator: Apr 20, 2017
    Code:
    findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >sfcdetails.txt
    findstr /c:"(F) STATUS" %windir%\Logs\CBS\CBS.log >>sfcdetails.txt
    
     
  20. nexus76

    nexus76 MDL Addicted

    Jan 25, 2009
    788
    296
    30
    #20 nexus76, Mar 22, 2015
    Last edited by a moderator: Apr 20, 2017
    it repaired

    Code:
    0000236a [SR] Beginning Verify and Repair transaction
    0000236c [SR] Cannot repair member file [l:24{12}]"utc.app.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 10.0.10041.0, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral in the store, hash mismatch
    0000236e [SR] Cannot repair member file [l:66{33}]"telemetry.ASM-WindowsDefault.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 10.0.10041.0, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral in the store, hash mismatch
    0000239c [SR] Cannot repair member file [l:24{12}]"utc.app.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 10.0.10041.0, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral in the store, hash mismatch
    0000239d [SR] This component was referenced by [l:222{111}]"Microsoft-OneCore-TroubleShooting-Package~31bf3856ad364e35~amd64~~10.0.10041.0.5ef5ae9c8532246b66b34a31cc451340"
    0000239f [SR] Cannot repair member file [l:66{33}]"telemetry.ASM-WindowsDefault.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 10.0.10041.0, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral in the store, hash mismatch
    000023a0 [SR] This component was referenced by [l:222{111}]"Microsoft-OneCore-TroubleShooting-Package~31bf3856ad364e35~amd64~~10.0.10041.0.5ef5ae9c8532246b66b34a31cc451340"
    000023a3 [SR] Could not reproject corrupted file [ml:116{58},l:114{57}]"\??\C:\ProgramData\Microsoft\Diagnosis\DownloadedSettings"\[l:24{12}]"utc.app.json"; source file in store is also corrupted
    000023a6 [SR] Could not reproject corrupted file [ml:116{58},l:114{57}]"\??\C:\ProgramData\Microsoft\Diagnosis\DownloadedSettings"\[l:66{33}]"telemetry.ASM-WindowsDefault.json"; source file in store is also corrupted
    000023e5 [SR] Verify complete
    000023e6 [SR] Verifying 100 (0x0000000000000064) components
    
    
    00004d8d [SR] Repairing 1 components
    00004d8e [SR] Beginning Verify and Repair transaction
    00004d90 [SR] Cannot repair member file [l:24{12}]"utc.app.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 10.0.10041.0, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral in the store, hash mismatch
    00004d92 [SR] Cannot repair member file [l:66{33}]"telemetry.ASM-WindowsDefault.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 10.0.10041.0, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral in the store, hash mismatch
    00004d95 [SR] Cannot repair member file [l:24{12}]"utc.app.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 10.0.10041.0, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral in the store, hash mismatch
    00004d96 [SR] This component was referenced by [l:222{111}]"Microsoft-OneCore-TroubleShooting-Package~31bf3856ad364e35~amd64~~10.0.10041.0.5ef5ae9c8532246b66b34a31cc451340"
    00004d98 [SR] Cannot repair member file [l:66{33}]"telemetry.ASM-WindowsDefault.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 10.0.10041.0, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral in the store, hash mismatch
    00004d99 [SR] This component was referenced by [l:222{111}]"Microsoft-OneCore-TroubleShooting-Package~31bf3856ad364e35~amd64~~10.0.10041.0.5ef5ae9c8532246b66b34a31cc451340"
    00004d9c [SR] Could not reproject corrupted file [ml:116{58},l:114{57}]"\??\C:\ProgramData\Microsoft\Diagnosis\DownloadedSettings"\[l:24{12}]"utc.app.json"; source file in store is also corrupted
    00004d9f [SR] Could not reproject corrupted file [ml:116{58},l:114{57}]"\??\C:\ProgramData\Microsoft\Diagnosis\DownloadedSettings"\[l:66{33}]"telemetry.ASM-WindowsDefault.json"; source file in store is also corrupted
    00004da1 [SR] Repair complete
    00004da2 [SR] Committing transaction
    00004da7 [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction  have been successfully repaired
    for me
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...