I have done a /RestoreHealth using admin command promptISM /Online /Cleanup-Image /RestoreHealth /source:WIM:f:\Sources\Install.wim:1 /LimitAccess. Install.wim downloaded from Win10_1511_English_x32.iso.
It said it was completed succesfully, but sfc /scannow reports these corrupted files.
Did you reboot after running DISM commands?? you should have rebooted right after running those commands.
Okay....reran the process shown below:
Ran Image_Health command as an admin:
IMAGEHEALTH PROGRAM OPTIONS
===============================================================================
Press 0 - Quit and Exit program
Press 1 - Run Dism /ScanHealth
Press 2 - Run Dism /RestoreHealth
Press 3 - Run Dism /RestoreHealth /Source
Press 4 - Run Dism /AnalyzeComponentStore
Press 5 - Run Dism /StartComponentCleanup
Press 6 - Run Dism /StartComponentCleanup /ResetBase
Press 7 - Run Dism /revertpendingactions
Press 8 - Run SFC /Scannow
Press 9 - Run Extended Disk Cleanup Manager
===============================================================================
> Enter Your Option:
Option 1 – DISM /ScanHealth
===============================================================================
Dism is scanning the online image for health.
Dism will report whether the image is healthy or repairable
This will take several minutes..
===============================================================================
Deployment Image Servicing and Management tool
Version: 10.0.10586.0
Image Version: 10.0.10586.0
[==========================100.0%==========================]
No component store corruption detected.
The operation completed successfully.
Press any key to continue . . .
Option 2 – DISM /RestoreHealth
===============================================================================
Dism is restoring the online image health.
This will take several minutes..
===============================================================================
Deployment Image Servicing and Management tool
Version: 10.0.10586.0
Image Version: 10.0.10586.0
[==========================100.0%==========================]
The restore operation completed successfully.
The operation completed successfully.
Press any key to continue . . .
Option 3 – DISM /RestoreHealth /Source
===============================================================================
Found Source Install.wim on Drive G:
===============================================================================
===============================================================================
MOUNTING THE SOURCE INSTALL.WIM AS THE REPAIR SOURCE
===============================================================================
1 file(s) copied.
Deployment Image Servicing and Management tool
Version: 10.0.10586.0
Mounting image
[==========================100.0%==========================]
The operation completed successfully.
===============================================================================
Dism is restoring the online image health.
This will take several minutes..
===============================================================================
Deployment Image Servicing and Management tool
Version: 10.0.10586.0
Image Version: 10.0.10586.0
[==========================100.0%==========================]
The restore operation completed successfully.
The operation completed successfully.
Deployment Image Servicing and Management tool
Version: 10.0.10586.0
Unmounting image
[==========================100.0%==========================]
The operation completed successfully.
Press any key to continue . . .
ReBooted……………………………………………………….
Option 8 – SFC /SCANNOW
===============================================================================
System File Checker is scanning the online image for corruption.
This will take several minutes
===============================================================================
Beginning system scan. This process will take some time.
Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection found corrupt files but was unable to fix some
of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
supported in offline servicing scenarios.
Press any key to continue . . .
post the cbs.log
Note: SFC has been known to flag perfectly good files as corrupt, although this does not harm anything other, then the user now thinking the system is corrupt, and resulting in false positive confusion about the corruption
reading the CBS.log - it appears you had two mis-matched file hashes..
It also appears they have been repaired..
as the final result is
-----------------------------
Summary:
Operation: Detect and Repair
Operation result: 0x0
Last Successful Step: Entire operation completes.
Total Detected Corruption: 0
CBS Manifest Corruption: 0
CBS Metadata Corruption: 0
CSI Manifest Corruption: 0
CSI Metadata Corruption: 0
CSI Payload Corruption: 0
Total Repaired Corruption: 0
CBS Manifest Repaired: 0
CSI Manifest Repaired: 0
CSI Payload Repaired: 0
CSI Store Metadata refreshed: True
Total Operation Time: 484 seconds.
So I reran sfc /scannow again after erasing the cbs log and it still reported corrupt files:
Microsoft Windows [Version 10.0.10586]
(c) 2015 Microsoft Corporation. All rights reserved.
C:\WINDOWS\system32>sfc /scannow
Beginning system scan. This process will take some time.
Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection found corrupt files but was unable to fix some
of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
supported in offline servicing scenarios.
I attached the CBS log, if it is reporting wrongly, I will just ignore the error......
Attachment 51243
Thanks.....
What are you using for your REPAIR SOURCE ??
10586 setup media download from techbench ??
You now have a lot of mis-matched hashes
Win10_1511_English_x32.iso
Quote