Ran Windows Update and System File Checked detect un-fixable errors...

Discussion in 'Windows 10' started by MonarchX, Apr 29, 2015.

  1. MonarchX

    MonarchX MDL Expert

    May 5, 2007
    1,283
    206
    60
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  2. burfadel

    burfadel MDL EXE>MSP/CAB

    Aug 19, 2009
    2,628
    3,841
    90
    #2 burfadel, Apr 29, 2015
    Last edited by a moderator: Apr 20, 2017
    From an elevated command prompt, run:
    Code:
    dism /online /cleanup-image /restorehealth
    The output from this command is a little confusing, as even if there weren't errors it suggests that there were, and have been fixed. To really know if there were errors, you need to use the /scanhealth instead of /restorehealth option, but that only tells you if there is an issue, not actually resolve it! (and still takes times). Basically, /restorehealth runs /scanhealth, but also fixes any issues found.

    I find that this should be run before sfc, since sfc relies on the information corrected with the /restorehealth option.
     
  3. coleoptere2007

    coleoptere2007 MDL Guru

    Apr 8, 2008
    2,288
    1,175
    90
    Try :
    1. Dism /Online /Cleanup-Image /ScanHealth
    2. Dism /Online /Cleanup-Image /CheckHealth
    3. Dism /Online /Cleanup-Image /RestoreHealth

    :)
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  4. MonarchX

    MonarchX MDL Expert

    May 5, 2007
    1,283
    206
    60
    Thanks! I always forget DISM is an amazing tool that repairs almost everything. I ran RestoreHealth before ScanHealth.., but it told me at the end that issues were solved. However, THEN I ran SFC and it found problems AGAIN, but it fixed them all! I wonder why RestoreHealth hasn't fixed it properly...
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  5. LatinMcG

    LatinMcG Bios Borker

    Feb 27, 2011
    5,382
    1,456
    180
    dism /online /cleanup-image /startcomponentcleanup
     
  6. John Sutherland

    John Sutherland MDL Addicted

    Oct 15, 2014
    581
    810
    30
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  7. MonarchX

    MonarchX MDL Expert

    May 5, 2007
    1,283
    206
    60
    I was wondering whether DISM Cleanup restores original Windows files and does not use updated files. That could create a problem, can't it?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  8. MonarchX

    MonarchX MDL Expert

    May 5, 2007
    1,283
    206
    60
    Anyone know?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  9. John Sutherland

    John Sutherland MDL Addicted

    Oct 15, 2014
    581
    810
    30
    #9 John Sutherland, May 5, 2015
    Last edited: May 5, 2015
    Hello to All - A follow-up: I just ran sfc /scannow this morning and found a repeat of the same problem. In my case, it appears that two files related to Windows Update are somehow being corrupted on a regular basis. Here's a cut & paste from the relevant portion of my CBS.log file:

    CSIPERF:TXCOMMIT;511068
    2015-05-05 14:47:28, Info CSI 000008f1 StoreCorruptionRepair transaction completed.
    2015-05-05 14:47:28, Info CBS Repr: Finished repairing CSI store.
    2015-05-05 14:47:28, Info CBS Ensure CBS corruption flag is clear
    2015-05-05 14:47:28, Info CBS All WCP store corruptions were fixed
    2015-05-05 14:47:28, Info CBS Ensure WCP corruption flag is clear
    2015-05-05 14:47:28, Info CBS
    =================================
    Checking System Update Readiness.
    (p) CSI Payload Corrupt (Fixed) amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.3.9600.17747_none_90df8130dac08ee0\utc.app.json
    (p) CSI Payload Corrupt (Fixed) amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.3.9600.17747_none_90df8130dac08ee0\telemetry.ASM-WindowsDefault.json
    Summary:
    Operation: Detect and Repair
    Operation result: 0x0
    Last Successful Step: Entire operation completes.
    Total Detected Corruption: 2
    CBS Manifest Corruption: 0
    CBS Metadata Corruption: 0
    CSI Manifest Corruption: 0
    CSI Metadata Corruption: 0
    CSI Payload Corruption: 2
    Total Repaired Corruption: 2
    CBS Manifest Repaired: 0
    CSI Manifest Repaired: 0
    CSI Payload Repaired: 2

    Store Metadata refreshed: True
    Total Operation Time: 1018 seconds.

    I'm going to do some Google searches and see what I can find. In the meantime, does anyone else have any ideas on what is causing this problem?

    EDIT: I did a search inside the Windows SxS folder. These are two of the seven .json files found in the folder and both are timestamped 5-5-2015 1:46PM, which coincides with when they were repaired by running dism.exe.

    244f4bef6387d00166bd0000d009580d.utc.app.json

    244f4bef6387d00168bd0000d009580d.telemetry.ASM-WindowsDefault.json
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  10. John Sutherland

    John Sutherland MDL Addicted

    Oct 15, 2014
    581
    810
    30
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  11. coleoptere2007

    coleoptere2007 MDL Guru

    Apr 8, 2008
    2,288
    1,175
    90
    You can hide this KB as many users are facing problems to install it (errors) and m$ did not find any solution.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  12. John Sutherland

    John Sutherland MDL Addicted

    Oct 15, 2014
    581
    810
    30
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  13. abbodi1406

    abbodi1406 MDL KB0000001

    Feb 19, 2011
    7,662
    24,592
    240
    The collected data is for upgrading to Windows 10, not the stability of Windows 8.1 :D

    nonetheless, sfc is overrated
    and three "faulty" files isn't a big deal
     
  14. burfadel

    burfadel MDL EXE>MSP/CAB

    Aug 19, 2009
    2,628
    3,841
    90
    They do different functions, although realistically the dism command for restorehealth should be run before SFC on Windows 8.1 onwards anyway. To put it in basic terms, what SFC does is make sure the active files are correct, using a type of database. What DISM /online /cleanup-image /restorehealth does is makes sure that database is correct. Any errors in the database will mean a restore function on SFC will fail. This is why the dism command should be run first IMO.

    DON'T ever run that unless SFC completes successfully. If there is an error like you had with SFC, startcomponentcleanup will most likely fail, but at worst you could end up with an unstable, potentially unbootable system (worst case).
     
  15. burfadel

    burfadel MDL EXE>MSP/CAB

    Aug 19, 2009
    2,628
    3,841
    90
    That depends on the files which are 'faulty', and the reason on which they are appearing as 'faulty' :).
     
  16. MonarchX

    MonarchX MDL Expert

    May 5, 2007
    1,283
    206
    60
    I installed 2 updates this last Tuesday and the same issue occurred again, but the update that caused it was different from the earlier update that caused it. I had to use DISM and use System File Check 2x times to completely resolve the problem. This is getting on my nerves. I mean MS releases OS-corrupting updates and expects people to pay for their OS! It should be a privilege for MS to have world population "beta-test" their OS on daily basis. People should be paid money to use it!

    In all honesty, it seems like the best way to update Windows 8.1 is to download an ISO with all updates integrated, format drive, and clean-install OS from that updated ISO. Running individual updates lately causes more problems than it fixes.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...