Solved Windows Update wont download... SFC finds corrupt cant fix

I guess persistence pays off...SFC /SCANNOW still says there are Corrupt files, but that was after one run NOT IN SAFE MODE!! I will rerun it again after seeing this!!! Now I dont know what to do with myself... HA!

Capture.JPG
 

Attachments

  • Capture.PNG
    Capture.PNG
    5.6 KB · Views: 238
David
thanks again for all your time and efforts to help. I truly appreciate it and in today's world, its nice to know there are still people like you that help others, and don't expect anything in return! A++ for your kindness and knowledge...you have forgotten more about computers that I will ever know!
:thumbsup:
 
David
thanks again for all your time and efforts to help. I truly appreciate it and in today's world, its nice to know there are still people like you that help others, and don't expect anything in return! A++ for your kindness and knowledge...you have forgotten more about computers that I will ever know!
:thumbsup:

You are very welcome. :)

I do have short term memory loss. :(
 
Here is a tutorial on making a batch file to run dism & sfc.


Open Notepad & Type in the 2 commands.
See pictures:

screenshot_107.png

screenshot_109.png

screenshot_110.png

screenshot_111.png

screenshot_112.png

screenshot_113.png

screenshot_114.png

screenshot_115.png

One more picture to come...

Last picture.
You should see this when the scans finish:

screenshot_116.png

That's all.
I hope you find this tutorial useful. :)
 
Last edited:
I noticed a lot of people recently having this very same file corruption when running SFC/ scannow. For me, I noticed it after Windows Update wasn't able to download some Definition updates for Defender which led me to run SFC and notice the corruption.

See this link for more people suffering from the problem: Hash mismatch - Microsoft Community


Are there any hints yet as to where the cause may lie??
 
I noticed a lot of people recently having this very same file corruption when running SFC/ scannow. For me, I noticed it after Windows Update wasn't able to download some Definition updates for Defender which led me to run SFC and notice the corruption.

See this link for more people suffering from the problem: Hash mismatch - Microsoft Community


Are there any hints yet as to where the cause may lie??

The component store sfc uses to fix things gets corrupted somehow.

Therefore it can't get the stuff it needs to fix certain problems.

Running dism fixes the component store.
It can download needed stuff from Windows Update or another service {in a screen shot on page one of this thread}.

Once the store is repaired SFC runs good.

I hope that answers you question. :)
 
What I was wondering is what exactly causes the component store to get corrupted. Your answer did clear things up for me nonetheless so thanks ;)

Anyone else notices that the DISM command changes the SYSTEM security settings of the file CNBJ2530.DBP seen in its Properties box? Unlike all the other DPB files in the same folder, this file doesn't seem to let SYSTEM have full access to it anymore (only "read" and "execute" are checked). I'm not sure this could lead to any potential problems later on...

CNBJ2530.DPB.jpg Random File.jpg
 
The ONLY entity that *needs* anything other than read/execute privileges to anything in the winsxs folder is TrustedInstaller - therefore anything else should not be allowed any other access.
It really is that simple.
 
@NoelDP: I checked the security settings privileges of that file before using the DISM command and it clearly showed that SYSTEM had more priviliges than only read/execute (just like the rest of the DPB files in the folder). That's why I just wanted to mention this and was wondering if there could be any problems because of this when future updates (i.e. windows 8.2?) would come out that needs the SYSTEM to modify or renew files.
 
It's TrustedInstaller that does the work of installing updates, not SYSTEM - that's why System doesn't need anything other than read/execute privileges.
 
Windows Modules Installer *is* TrustedInstaller - by another name :)
TrustedInstaller is the executable and also the service name in Windows 6.x
WMI.png
 
Back
Top