Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Saturday, May 27, 2017 8:54 AM
I want to ask, if this output is normal / correct, exactly the sentence "The component store is repairable."
C:\WINDOWS\system32>Dism /Online /Cleanup-Image /ScanHealth
Deployment Image Servicing and Management tool
Version: 10.0.15063.0
Image Version: 10.0.15063.0
[==========================100.0%==========================] The component store is repairable.
The operation completed successfully.
Of course I ran sfc /scannow before and that scan was ok, without any problems.
Thank you for advice.
All replies (3)
Saturday, May 27, 2017 12:09 PM âś…Answered | 1 vote
Wondering why are you running this? For fun \ learning or looking into an issue?
You have used the ScanHealth parameter so that just scans does not repair, reporting it repairable is normal see the same on my system.
System file check (SFC) Scan and Repair System Files & DISM to fix things SFC cannot (guide by Team ZigZag) has info on dism and worth a read.
My dism commands for info
Microsoft Windows [Version 10.0.15063]
(c) 2017 Microsoft Corporation. All rights reserved.
C:\Windows\system32>Dism /Online /Cleanup-Image /ScanHealth
Deployment Image Servicing and Management tool
Version: 10.0.15063.0
Image Version: 10.0.15063.0
[==========================100.0%==========================] The component store is repairable.
The operation completed successfully.
C:\Windows\system32>Dism /Online /Cleanup-Image /RestoreHealth
Deployment Image Servicing and Management tool
Version: 10.0.15063.0
Image Version: 10.0.15063.0
[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.
C:\Windows\system32>
Saturday, May 27, 2017 1:24 PM
Ok thx, so that's normal output. I ran this, because I migrated my os from one ssd to another and wanted to check windows integrity.
On the other hand I run this commands few times per year as my maintenance checks, alongside with other maintenance checks like chkdsk, look at window logs, ...
Thank you for advice ;)
Monday, May 29, 2017 2:39 AM | 1 vote
Hi ,
I can confirm that it is normal output, do not worry. I have tested it on my clean installed machine. It's a good habit to run these commands as maintenance checks.
Best regards
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.