SFC Reports Corruption Issues on all 4 of my PCs (after recent update)

Page 1 of 4 123 ... LastLast
  1. The Pool Man's Avatar
    Posts : 236
    10
       #1

    SFC Reports Corruption Issues on all 4 of my PCs (after recent update)


    Greetings All,

    A recent update (presumably the last Cumulative) caused SFC to uncover corrupted files (and the CBS files stuff) on three computers. On the first two I believed it involved a conflict between Malwarebytes and Windows, but on the third one I believe it's simply the update.

    I run SFC after all major and minor Windows releases. Almost always perfect. This time? 4 for 4.

    Anyone else?

    Oh, the only fix I've managed for the first three was some relentless DISM RestoreHealth sessions. At least 3 times in a row.
      My ComputerSystem Spec

  2. Try3's Avatar
    Posts : 2,476
    Windows 10 Home x64 and Pro x86
       #2

    Lots of us found the same problem after the WD platform was updated.
    [see WD, Settings {in the bottom-left corner}, About - Antimalware client version]
    from
    4.18.1905.4
    to
    4.18.1906.3
    [and some Insiders, users of preliminary updates, have said that it happened again after a further update}

    Since the only effect seems to be the SFC error it is possible to just ignore the problem and wait for MS to fix it.

    - - - - - - - - - - - - - - - - - - - - - - - - - -

    If you want to fix it then look again at SFC - TenForumsTutorials and run the Dism restore health command explained there. Some of us found that an effective sequence was
    1 Restart the computer
    2 Check you are connected to the internet. The Dism command needs to use WU & an online {MS} source for the repair. ***
    3 Open an Admin command window to use for each of the following commands
    4 SFC /scannow
    5 Dism /Online /Cleanup-Image /RestoreHealth
    6 SFC /scannow
    7 SFC /scannow [this final one being just to confirm that there are no remaining faults]

    *** For those of us who have jobbed WU by crippling USOClient - This repair procedure still works despite that.
    - - - - - - - - - - - - - - - - - - - - - - - - - -

    Extracting SFC results from the CBS.log

    You can use findstr commands to extract just the entries in the CBS log that you want.
    - You never need to look through the entire log.
    - SFC entries contain [SR]
    - Other Windows functions, such as Windows installer, also write to the CBS log.
    - Windows does archive the CBS log when it sees fit so you should extract results when you find an SFC problem and not leave it for a rainy day. If you do leave it too long, you might find the data you want in the archive files in %windir%\Logs\CBS [they are called cbsPersist...log].

    To extract all SFC entries into a text file {choose your own path & filename; I include the computer name because I run the same code on several computers}
    Code:
    findstr.exe /c:"[SR]" %windir%\Logs\CBS\CBS.log >D:\Desktop\%ComputerName%-SFCResults.Log

    To extract all SFC repairs into a text file {choose your own path & filename}
    Code:
    findstr.exe /c:"[SR] Repair" %windir%\Logs\CBS\CBS.log >D:\Desktop\%ComputerName%-SFCResults-Repairs.Log

    To extract all SFC "could not reproject" failures into a text file {choose your own path & filename} - I have never found a decent explanation of this type of failure but, because each entry includes "source file in store is also corrupted", I believe that it can serve as an explanation for a corresponding entry in the irrepairables list.
    Code:
    [findstr.exe /c:"[SR] Could not reproject" %windir%\Logs\CBS\CBS.log >D:\Desktop\%ComputerName%-SFCResults-CouldNotReproject.Log

    To extract all SFC failures to repair into a text file {choose your own path & filename}
    Code:
    findstr.exe /c:"[SR] Cannot repair member file" %windir%\Logs\CBS\CBS.log >D:\Desktop\%ComputerName%-SFCResults-Unrepairables.Log"

    Note that every line in the output files has its date-time stamp so if the extracts were very long you could just search for the first instance of today's date to start looking through what it has just been up to.
    - But, by being very well focussed, the extracts are normally short enough to be read easily and to be posted in a forum thread if necessary [unlke the CBS log itself, which is far too long to comprehend or to expect others to review].
    - If you make multiple extractions [such as Irreparables & Could not reproject ones] then you can also use that date-time stamp to compare entries.

    - - - - - - - - - - - - - - - - - - - - - - - - - -

    When this particular problem appears, the irreparables list entries all contain, "Windows-Defender-Management-Powershell" and attribute the problem to a "hash mismatch".
    SFC Reports Corruption Issues on all 4 of my PCs (after recent update)-20190712-142429-tab10-sfcresults-unrepairables.png

    There are several threads on this topic, including
    sfc -scannow failing after this latest Defender Platfom update - TenForums
    weird problem involving corrupted files. please help, i'm stumped. - TenForums
    SFC and DISM error when trying to fix corrupt windows files - TenForums
    sfc -scannow found corrupted file that could not be corrected [a general thread] - TenForums
    System File Checker errors reported - TenForums

    and the MS admission is at
    SFC incorrectly flags WD PowerShell module files as corrupted - MSSupport


    Denis
    Last edited by Try3; 26 Jul 2019 at 13:02.
      My ComputerSystem Spec

  3. EyeInTheSky's Avatar
    Posts : 536
    Windows 10 Home x64 - Version 1903 (OS Build 18362.356)
       #3

    The Pool Man said: View Post
    Greetings All,

    A recent update (presumably the last Cumulative) caused SFC to uncover corrupted files (and the CBS files stuff) on three computers. On the first two I believed it involved a conflict between Malwarebytes and Windows, but on the third one I believe it's simply the update.

    I run SFC after all major and minor Windows releases. Almost always perfect. This time? 4 for 4.

    Anyone else?

    Oh, the only fix I've managed for the first three was some relentless DISM RestoreHealth sessions. At least 3 times in a row.

    I would consider you lucky that it only happened this time. Every single Cumulative Update since Windows 10 was released for public use, I have had to repair SFC Corruption. The corruption usually manifests itself in the .wim file that can only be restored through the Advanced Recovery Environment for me anyways.

    I had mentioned this before on the site, but no one even had any comment about it or they just don't run SFC I guess. Either way, I have got use to picking up the pieces after Cumulative Updates and have lived with it since Windows 10 release. Is it right?

    No.

    Is there a solution?

    I haven't found one yet, (other than my manual restore of the .wim file) since it involves the restoration of a file that cannot be obtained by the Restore Health method (DISM).

    Have I reported it to Microsoft?

    Yes. Ever single Cumulative Update that caused it since Windows 10 release to the public. I even supplied them the Cumulative Update Versions since it started and it was just shrugged off as an older hardware issue. Really? Microsoft is the frigging company that evaluated my machine for upgrade approval through their Upgrade Assistant Tool.
    Last edited by EyeInTheSky; 23 Jul 2019 at 21:39. Reason: Clarification
      My ComputerSystem Spec

  4. AddRAM's Avatar
    Posts : 2,573
    Windows 10 Pro x64
       #4

    Open Command Prompt as an Administrator, copy and paste this command and hit enter, let it do it`s thing until it says "Press an key" and your done. Restart the PC and run a system file check again. It will be perfect.

    The corrupt file comes from a Defender update, it`s no big deal. Credit for the command goes to Cliff.

    fsutil resource setautoreset true c:\&fsutil usn deletejournal /d /n c:&Dism.exe /online /Cleanup-Image /StartComponentCleanup&sfc /scannow&Dism.exe /Online /Cleanup-Image /RestoreHealth&sfc /scannow&Dism.exe /Online /Cleanup-Image /StartComponentCleanup /ResetBase&pause
      My ComputersSystem Spec

  5. The Pool Man's Avatar
    Posts : 236
    10
    Thread Starter
       #5

    EyeInTheSky said: View Post
    I would consider you lucky that it only happened this time. Every single Cumulative Update since Windows 10 was released for public use, I have had to repair SFC Corruption.
    Sorry to hear that. Maybe once or twice before, but not on all four PCs. Like one didn't like it, the other was okay.

    Thanks for replying all. I knew it was infamous once all four did it here.
      My ComputerSystem Spec

  6. The Pool Man's Avatar
    Posts : 236
    10
    Thread Starter
       #6

    By the by, the last PC was stubborn but it finally gave me the A-OK.

    As a former Mac person I'm a little surprised the PC doesn't do this process by itself when no one is looking.
      My ComputerSystem Spec


  7. Steve C's Avatar
    Posts : 4,124
    Windows 10 Pro 64 bit
       #7

    I fail to understand why MS doesn't run sfc /scannow before inflicting their bug prone updates on the public
      My ComputersSystem Spec

  8. The Pool Man's Avatar
    Posts : 236
    10
    Thread Starter
       #8

    AddRAM said: View Post
    The corrupt file comes from a Defender update, it`s no big deal.
    I would disagree with the assessment it's no big deal. The reason why I discovered the problem in the first place was random system janky behavior.

    1. On one PC if you were in the taskbar selecting an app and then attempting to move your pointer up into that app -- the app would go away before you got up there. Each time.
    2. On a different PC I was getting constant messages that a piece of an app was missing and therefore the app couldn't function. Various apps, no rhyme or reason to it.

    Since the two of the four INSTANTLY behaved badly I scrambled to find out what was causing it.
      My ComputerSystem Spec

  9. AddRAM's Avatar
    Posts : 2,573
    Windows 10 Pro x64
       #9

    Hmmm, you seem to have a different problem.
      My ComputersSystem Spec

  10. Try3's Avatar
    Posts : 2,476
    Windows 10 Home x64 and Pro x86
       #10

    I have updated my suggested recovery procedure [post #2 above] in response to new evidence.

    For Dism to repair the defective components, the computer must be connected to the internet.
    - The Dism command needs to use WU & an online {MS} source for the repair.
    - [For those of us who have jobbed WU by crippling USOClient - This repair procedure still works despite that.]

    I can understand the logic of it but it had never occurred to me before.
    - Without any other source being available, there is nowhere for any replacement files to come from given that SFC has already checked the component store.
    - WU & hence the internet acts as a default source when DISM /RestoreHealth /Source:nnnnnnnnnnn is not specified.
    - For this particular situation, given that the fault is in a WD update issued after the ISO, the latest ISO is probably not going to do any good as a /Source:nnnnnnnnnnn.

    Denis
      My ComputerSystem Spec


 
Page 1 of 4 123 ... LastLast

Related Threads
Windows 10 SFC /scannow Can't Fix Corrupted Files After Update This is a question regarding the recent file corruption that occurred after a Windows anti malware update caused Windows Defender Platform errors that are first noticed when running...
If I remember correctly, the scaling issues with non-high-DPI-aware Windows applications being displayed as "blurry" were fixed in 1511 update (or around that time). My laptop has been set for 200% scaling and everything was working perfectly since...
Since W10 (and I do like it) I have had lots of file corruptions (system and “unable to open ...user/desktop/ as location is corrupt or unreadable), and on at least three occassions (in 3 months) the start menu has stopped working (won't pop up)...
Since W10 (and I do like it) I have had multiple BSOD resulting in no longer being able to start windows, with start up repair saying unable to fix errors, lots of file corruptions (system and “unable to open ...user/desktop/ as location is...
it saids is ethernet unidentified network? no internet access sharing option is off. i try restarting the pc:( it use to work fine until the update bridging network cable
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

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