Need help with sfc scannow. keeps coming back with corrupted files

darx888

Prominent
May 24, 2017
4
0
510
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 A6-7310 APU 2.00 GHZ, 64 bit processor
AMD Radeon R4 graphics
4 GB RAM
500 GB HDD
Windows 10 home, 64 bit OS


i performed the dism repairs multiple ways. first i did the standard dism online restore.. it says that its completed successfully. then i reboot and run scannow and it comes back corrupted.

then i downloaded a copy of windows 10, mounted it to my desktop, entered the commands to repair. it said it was successful. then i rebooted and scannow and its still corrupted.

this is the website i followed to fix the corruption:

https://www.easytechguides.com/sfc-unable-to-fix-corrupt-files.html

im going to post links to the dism and cbs logs, as well as my dxdiag and msinfo

dxdiag:

http://s000.tinyupload.com/index.php?file_id=78455474865904020799

msinfo:

http://s000.tinyupload.com/index.php?file_id=02438305975106395612

cbs log:

http://s000.tinyupload.com/index.php?file_id=96287359864356038556

dism log:

http://s000.tinyupload.com/index.php?file_id=27853417979712885165

i dont know what else to do. any help would be greatly appreciated. thank you
 
Solution
Hi, a few months back I ran SFC on my system and also came up with an error. I looked it up and was unable to fix it. The only reason I ran SFC was because I was on here helping someone else and I don't ask people to do something on their system that I wouldn't do on mine. DISM didn't help me either.

The fact is, my system has been up and running 7+ years now (upgraded from Win7, haven't reinstalled at all) and I'm having NO problems at all, especially with system files. I'm not worried about the SFC returning that error at all. If it comes down to it and everything is messed up and SFC can't help me, I'll re-install Windows. I also do a monthly (or bi-monthly when lazy) full system backup.

It could be that SFC just isn't working...

Colif

Win 11 Master
Moderator
You were lucky dism source command is working for you, they might have fixed it. They broke it after the creators edition was released. it would keep coming back saying it can't find the source even when you show it where to look.

SFC can find corrupted files on a fresh install, its a common thing and if PC seems to be working fine, I would just ignore it.
 

darx888

Prominent
May 24, 2017
4
0
510


thank you for your response, but what happens when there really are corrupted files that i need to fix, but cant detect them because of this issue? thats what im worried about. i figured this is some kind of bug, but i dont want to be in a position where i later need to scannow and fix corrupted files and not be able to because of this.

windows 10 has been a big disappointment for me
 

gardenman

Splendid
Moderator
Hi, a few months back I ran SFC on my system and also came up with an error. I looked it up and was unable to fix it. The only reason I ran SFC was because I was on here helping someone else and I don't ask people to do something on their system that I wouldn't do on mine. DISM didn't help me either.

The fact is, my system has been up and running 7+ years now (upgraded from Win7, haven't reinstalled at all) and I'm having NO problems at all, especially with system files. I'm not worried about the SFC returning that error at all. If it comes down to it and everything is messed up and SFC can't help me, I'll re-install Windows. I also do a monthly (or bi-monthly when lazy) full system backup.

It could be that SFC just isn't working correctly for everyone. It could be an actual bug in SFC itself, or Windows itself. Either way, if your not having any problems, don't worry about it.

If it ain't broke, don't fix it.
 
Solution

darx888

Prominent
May 24, 2017
4
0
510


Colif thank you for your response and suggestion. ive actually already tried to reinstall my windows 10 twice now. still comes up with the same problems.. at this point im inclined to agree with you. it probably is something wrong on their end. other than these supposed corrupted files, my pc is working fine.

thanks again