sfc /scannow found corrupted file that could not be corrected. Solved

Page 5 of 5 FirstFirst ... 345
  1. Try3's Avatar
    Posts : 2,085
    Windows 10 Home x64 and Pro x86
       #41

    I do not know. As I said before, I did not update this way. You might be able to find out by downloading all three then seeing if their file properties yield anything interesting.

    Denis
    Last edited by Try3; 3 Days Ago at 18:56.
      My ComputerSystem Spec

  2. Farvatten's Avatar
    Posts : 102
    Windows 10 Pro 64bit 1903 18362.239
       #42

    EdTittel said: View Post
    I *know* it's something to do with Windows Defender. Haven't yet figured out if it's the Defender Updates or the Antimalware Platform Updates. How did you make this determination? Curious to understand, so please explain. Thanks!
    --Ed--
    Try3 said: View Post
    Ed,

    Nobody has reported running the updates in a manner that would distinguish between the two. I updated my platform by running the update from the WD UI and that, as normal, combined platform & definition updates.
    My platform version went from 4.18.1905.4 to 4.18.1906.3
    My definitions went from 1.297.653.0 to 1.297.830.0
    So I cannot distinguish between the two changes.

    Now I'm confused, I thought this statement from MS Support answered the question by tying it to any platform updates 4.18.1906.3 and higher 2 days ago?

    https://support.microsoft.com/en-us/...s-as-corrupted


    Click image for larger version. 

Name:	WindowsSupportAnnouncement.jpg 
Views:	2 
Size:	161.0 KB 
ID:	240705
    Last edited by Farvatten; 3 Days Ago at 20:57.
      My ComputersSystem Spec

  3.    #43

    EdTittel said: View Post
    @sportsfan148:
    I *know* it's something to do with Windows Defender. Haven't yet figured out if it's the Defender Updates or the Antimalware Platform Updates. How did you make this determination? Curious to understand, so please explain. Thanks!
    --Ed--
    Sorry Ed. It sounds like Ive probably over simplified my thinking. I hadn't had any issues after running sfc /scannow immediately after any WD definitions updates. But in my case on the two separate occasions that the Antimalware platform updates were pushed (after DISM fixing the first lot)..on each of those occasions I did a sfc /scannow immediately afterwards and got the same errors each time. In my case the updates came directly through Windows Update and not after checking through the Defender App
      My ComputerSystem Spec

  4.    #44

    @sportsfan148: thanks for sharing your experiences. Just yesterday, on Insider Preview Fast Ring PCs, I experienced recurrences of the phenomenon each time I updated the Windows Defender virus definitions myself. Just one case that points me toward "something" in Defender. As far as my update history goes, the waters are muddied by the installation of the latest Insider Preview feature upgrade (Build 18941.1001) as well as Defn updates. For all I know, a new version of Win10 IP could also mean a new version of the antimalware engine as well. Thus, I still can't tell for sure what's causing this. Sigh.
    --Ed--
      My ComputersSystem Spec

  5.    #45

    EdTittel said: View Post
    @sportsfan148: thanks for sharing your experiences. Just yesterday, on Insider Preview Fast Ring PCs, I experienced recurrences of the phenomenon each time I updated the Windows Defender virus definitions myself. Just one case that points me toward "something" in Defender. As far as my update history goes, the waters are muddied by the installation of the latest Insider Preview feature upgrade (Build 18941.1001) as well as Defn updates. For all I know, a new version of Win10 IP could also mean a new version of the antimalware engine as well. Thus, I still can't tell for sure what's causing this. Sigh.
    --Ed--
    No problem at all Ed. As I described earlier I'm on Antimalware Platform version 4.18.1907.4 which was pushed through Windows Update and as I described sfc /scannow shows the errors again. The only difference in my case this time is Ive left well alone and haven't fixed them with DISM. Is that OK or should I perform a repair with DISM again?
      My ComputerSystem Spec

  6.    #46

    @sportsfan148: I'm pretty sure the hash mismatch error is about as benign as "file corruption" gets in SFC. MS will have to fix this, sooner or later. And it's looking like "increasingly later" is the approximate timeframe!
    --Ed--
      My ComputersSystem Spec


  7. f14tomcat's Avatar
    Posts : 42,184
    Triple boot - Win 10 Pro, Win 10 Pro Insider (2) - (and a sprinkling of VMs)
       #47

    EdTittel said: View Post
    @sportsfan148: I'm pretty sure the hash mismatch error is about as benign as "file corruption" gets in SFC. MS will have to fix this, sooner or later. And it's looking like "increasingly later" is the approximate timeframe!
    --Ed--
    Just one comment. Hashes are benign, as you state, like a mosquito bite....just irritating. But, But one time last week, near the beginning of all this, I had reason to do a full series of DISM to clean up component store, and it failed on last one listed here. Don't know for sure if it was just a one-off here, or symptomatic. After repairing the hashes, all ran fine.

    fsutil resource setautoreset true c:\&fsutil usn deletejournal /d /n c:


    Dism.exe /online /Cleanup-Image /StartComponentCleanup

    Dism.exe /Online /Cleanup-Image /RestoreHealth

    Dism.exe /Online /Cleanup-Image /StartComponentCleanup /ResetBase
      My ComputersSystem Spec


 
Page 5 of 5 FirstFirst ... 345

Related Threads
Im at my wits end with what to do about this. I have a brand new pc that is turning up with corrupted files when i run the scannow.. ive dism restored it multiple times and re-scanned and it keeps coming back with errors. pc specs: AMD...
Custom build for a friend. OS: Windows 10 Pro, 64-bit MB: MSI Z170-A Pro Graphics Card: GeForce GTX 680 CPU: Intel i5 6600K @ 3.50GHz RAM: 8g Installed OS through bootable USB, as the build has no CD drive. On completion of build I had...
Solved SFC /scannow with corrupted files in Performance & Maintenance
Hi Roomies, After a clean install and running Win 10-pro-64-10586.36 I'm getting this error. 58062 Any quick help will be appreciated. I don't know what other test or fixer to run. Thank you.
Hello. For quite a while, my computer had slow boot up and shutdown times and I searched online that sfc /scannow could probably help. I've tried every method regarding sfc /scannow and nothing worked. I've also included a CBS Log file to help me...
Solved sfc /scannow found errors in Performance & Maintenance
I ran "sfc /scannow" just for the heck of it and it found the following errors. 32091 32090 Can anyone decipher the issue(s) it's pointing to? And perhaps know how to resolve it?
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 21:59.
Find Us