SFC SCANNOW and DISM RESTOREHEALTH - Repair Corrupt Files

KYHI
Thank you for the DISM information and keeping the link updated. It is much appreciated.
Peter
 
I have used "Image Health" to solve all my DISM/SFC SCANNOW errors on the rare occasions they cropped up over the last few months. I cannot rate this simple tool high enough. It never fails and I would be lost without it, magnificent stuff Kyhi :)
 
Last edited by a moderator:
Already looked at the topic hours ago...
your cbs.rar upload is a blank file and you are not using the image health program..
 
[FONT=&quot]Readme says to run it from a Root Folder C:\Image_Health - [/FONT]
[FONT=&quot]Can I instead put it into C:\APPS\Image_Health\ - [/FONT]
[FONT=&quot]I keep a lot of portable/ maintenance special apps in there. [/FONT]
[FONT=&quot]That way this also stays in my little Toolbox.

[/FONT]
 
You can find the Download link on the First Page (First Post)
 
[FONT=&amp]I found the serious BUG which affect wide range of Windows systems, from Vista to 10, including Windows Server.[/FONT]
[FONT=&amp]I've found that standard "defrag.exe" can cause file corruption under some circumstances.
The mentioned file corruption can happen during automatic maintenance (which compresses some files with NTFS compression and runs defrag.exe) and scheduled/manual defragmentation on system volumes with compressed (NTFS compression) files.

During investigation i've found some interesting facts:
1. The file corruption is always happen with compressed (NTFS compression) files hardlinked to WinSxS file repository
2. The file corruption is always happen only with some specific files
3. This specific files should be fragmented (NTFS compression causes file fragmentation)
4. The file corruption does not change the file size
5. The file corruption is always resides at the end of the file, look like the data and the end of the corrupted files is just overriten with some garbage
6. The data written by the "defrag.exe" to the end of each corrupted file is random, but the data pattern is the same for each particular file

On my test system (Windows 8.1 Enterprise with Update) only those files was corrupted by the "defrag.exe":

SHA1 checksum before defragmentation:
Code:
[COLOR=#222222][FONT=inherit]25afca7b7d459eae47359691c7f54133d79b3892 *Windows\System32\DriverStore\FileRepository\prncacla.inf_amd64_19fbb18075fefb90\Amd64\CNBJ2530.DPB[/FONT][/COLOR]
[COLOR=#222222][FONT=inherit]25afca7b7d459eae47359691c7f54133d79b3892 *Windows\WinSxS\amd64_prncacla.inf_31bf3856ad364e35_6.3.9600.17415_none_95dd5540d57f8c01\Amd64\CNBJ2530.DPB[/FONT][/COLOR]
[COLOR=#222222][FONT=inherit]f97cea19c3dd45ff153d88fc6852172d4750c178 *Windows\System32\NL7Models0404.dll[/FONT][/COLOR]
[COLOR=#222222][FONT=inherit]f97cea19c3dd45ff153d88fc6852172d4750c178 *Windows\WinSxS\amd64_microsoft-windows-w..chinese_traditional_31bf3856ad364e35_6.3.9600.16384_none_da1970df8c4dae3f\NL7Models0404.dll[/FONT][/COLOR]
[COLOR=#222222][FONT=inherit]60a7c773083b2f39a7564d6d2e78f0c73a339739 *Windows\SysWOW64\NlsData0414.dll[/FONT][/COLOR]
[COLOR=#222222][FONT=inherit]60a7c773083b2f39a7564d6d2e78f0c73a339739 *Windows\WinSxS\x86_microsoft-windows-naturallanguage6-0414_31bf3856ad364e35_6.3.9600.17415_none_d48386f27bb83f5d\NlsData0414.dll[/FONT][/COLOR]
[COLOR=#222222][FONT=inherit]e2de8a477c4cf0ee859b23e961b2cf3b981c2283 *Windows\SysWOW64\wbemcomn.dll[/FONT][/COLOR]
[COLOR=#222222][FONT=inherit]e2de8a477c4cf0ee859b23e961b2cf3b981c2283 *Windows\WinSxS\wow64_microsoft-windows-wmi-core-wbemcomn-dll_31bf3856ad364e35_6.3.9600.17415_none_fedad3362b50a192\wbemcomn.dll[/FONT][/COLOR]
[COLOR=#222222][FONT=inherit]1155fcc96a4b690fde73ee949abd5a467b5fcc97 *Windows\WinSxS\x86_microsoft-windows-store-runtime_31bf3856ad364e35_6.3.9600.17415_none_85d0e5ba5abd52cc\WSShared.dll[/FONT][/COLOR]

SHA1 checksum after defragmentation:
Code:
[COLOR=#222222][FONT=inherit]ef3e85c9217f063f34f641185dc581f3e10977df *Windows\System32\DriverStore\FileRepository\prncacla.inf_amd64_19fbb18075fefb90\Amd64\CNBJ2530.DPB[/FONT][/COLOR]
[COLOR=#222222][FONT=inherit]ef3e85c9217f063f34f641185dc581f3e10977df *Windows\WinSxS\amd64_prncacla.inf_31bf3856ad364e35_6.3.9600.17415_none_95dd5540d57f8c01\Amd64\CNBJ2530.DPB[/FONT][/COLOR]
[COLOR=#222222][FONT=inherit]0f7dda1fdf64a56e94fccede01c8f281e27e9f26 *Windows\System32\NL7Models0404.dll[/FONT][/COLOR]
[COLOR=#222222][FONT=inherit]0f7dda1fdf64a56e94fccede01c8f281e27e9f26 *Windows\WinSxS\amd64_microsoft-windows-w..chinese_traditional_31bf3856ad364e35_6.3.9600.16384_none_da1970df8c4dae3f\NL7Models0404.dll[/FONT][/COLOR]
[COLOR=#222222][FONT=inherit]b90e6467ac4e45b63afe16288051135a84531d43 *Windows\SysWOW64\NlsData0414.dll[/FONT][/COLOR]
[COLOR=#222222][FONT=inherit]b90e6467ac4e45b63afe16288051135a84531d43 *Windows\WinSxS\x86_microsoft-windows-naturallanguage6-0414_31bf3856ad364e35_6.3.9600.17415_none_d48386f27bb83f5d\NlsData0414.dll[/FONT][/COLOR]
[COLOR=#222222][FONT=inherit]384cd54e920ae6c41f8937f7419a07621cdc7fdc *Windows\SysWOW64\wbemcomn.dll[/FONT][/COLOR]
[COLOR=#222222][FONT=inherit]384cd54e920ae6c41f8937f7419a07621cdc7fdc *Windows\WinSxS\wow64_microsoft-windows-wmi-core-wbemcomn-dll_31bf3856ad364e35_6.3.9600.17415_none_fedad3362b50a192\wbemcomn.dll[/FONT][/COLOR]
[COLOR=#222222][FONT=inherit]8fe2945539080bc6e1b29849ca10baf6a318a905 *Windows\WinSxS\x86_microsoft-windows-store-runtime_31bf3856ad364e35_6.3.9600.17415_none_85d0e5ba5abd52cc\WSShared.dll[/FONT][/COLOR]
[/FONT]

[FONT=&amp]Checksums of corrupted files can vary due to the random nature of corruption.
[/FONT]

https://social.technet.microsoft.co...range-of-windows-systems?forum=w8itprogeneral
 
Wanted to understand in more detail what this option means:

Option 9 > will run Disk Cleanup Manager in Extended Mode

You can find the Download link on the First Page (First Post)
How are you doing buddy? Hope you're feeling a little better?
 
It runs MS Disk Cleanup with extended options that you can select...

Run option 9 to see the additional disk cleanup options..

I'm Good... Thanks for asking...
 
KYHI friend we cannot thank you enough for giving us this great image repair tool. Indeed it has rid many of us of the need to reinstall corrupted windows repeatedly, and the extended cleanup option does make windows keep running without any hitches. But I was wondering if you might be able to include an option in this tool for removing foreign bodies in windows such as some of the malwares that so commonly attack its internet explorer. Then the cleanup tool will no doubt delete the explorer as well, but it will hopefully be replaced from the source file that we subsequently use to repair the image. It is just a thought, I hope you won't mind.
 
Back
Top