[SPLIT] Re: SFC /scannow cannot repair files

[DonB]

Same here Thanks for looking into this and helping me understand what is happening and how to fix it so it won't reoccur.
I look forward to your answer soon.
Regards, DonB

OS: Win7 x64 Pro (OEM) System Build re: Tigerdirect.com

 

[DonB]

Here is my DISM Log. I get an Error 87
*DISM.exe /Online /Cleanup-image /Restorehealth*
Error 87
dism error 87 win 7x64 - Bing

 

[tom982]

Hello Don,

Please don't post the same issue at multiple forums as it only confuses the helpers when things start changing in the background and they haven't done anything which could cause that.

I would prefer to work with your issue here rather than at SF because one of the members here, niemiro, has developed fantastic back end features at our disposal. So could you answer the question I asked at SF here please?

All of your corruptions are related to Windows Games, have you done anything that could potentially have cause this? It's too much of a coincidence for all of these to be corrupt by chance. I can fix it, I just want to establish any potential cause before I do so that it isn't reverted to the corrupt state.

Tom

 

[DonB]

Thank you all guys:

I am indebted to you guys to help me understand the workings of my Win7 x64 PC and how to fix it, rather than the drastic responses I read on Win File corruption at answers.microsoft.com
who say that userrs should do a Repair Install.See Run Win Setup while in Windows so the user File and programs are 'merged' with Current user Programs and Files.

QUOTE:
Dear DonB,

Tekno Venus has just replied to a thread you have subscribed to entitled - SFC /scannow cannot repair files - in the Windows Update forum of Sysnative Forums.

This thread is located at:
https://www.sysnative.com/forums/wi...ker-scannow-cannot-repair-files-new-post.html

Here is the message that has just been posted:
***************
A huge thanks to **tom982** (View Profile: tom982 - Sysnative Forums) and **niemiro** (View Profile: niemiro - Sysnative Forums) who helped me out on this one Basically, your corruptions were not being fixed because of the way windows compresses files. To help save space, some of the files in the winsxs folder are compressed. However, on some systems, the files are not compressed. It depends on the exact configuration and hotfixes installed on the computer.

All
of your corruptions are related to Windows Games, have you done
anything that could potentially have cause this? It's too much of a
coincidence for all of these to be corrupt by chance. I can fix it, I
just want to establish any potential cause before I do so that it isn't
reverted to the corrupt state.


Tom

Answer Stephen
***************
It seems that the files in my winsxs folder are compressed, and the ones in your folder are uncompressed. Hence when I replaced the files, I was giving you compressed ones, which SFC was not expecting, and therefore still producing errors that they were corrupt. I have now obtained the uncompressed versions from tom982, so here is the fix.
Thanks again. DonB/dbseven

 

[DonB]

So you all know, I ran a final sfc /scannow and got no corruptions. All OK.

BTW: What does this do: DISM.exe /Online /Cleanup-image /Restorehealth

Thanks, Don

 

[Tekno Venus]

BTW: What does this do: DISM.exe /Online /Cleanup-image /Restorehealth

That is a Windows 8 command, that replaces SURT. Instead of using the SURT tool, which requires a hefty download and is updated monthly, Windows 8 introduced a built in tool as part of the DISM - Deployment Image Servicing and Management - tool. This tool has a number of advantages over the old SURT, apart from the fact it is pre-installed. Whilst SURT only came with a small(ish) selection of files packaged with it to perform repairs with, DISM can access and download replacement files. This means that if it detects a corruption, it can attempt to download a replacement copy from the internet, which SURT could never do. SURT had to make do with the replacement files bundled with it (which is why it was such a large download) DISM isn't always successful, but it often is.

The reason you received an error when running it is because the restorehealth command wasn't introduced until Windows 8, and therefore it does not work on Windows 7.

Stephen