Use DISM to Repair Windows 10 Image  

Yeap! It is finally working. I have just tried the DISM command line and it got completed successfully to 100%. See screenshot below:



One thing really weird I noticed though while running is that it got to 97% and then rolled back to 90% before completing successfully at 100%. I don't know why. Go figure, but at least it is working..

KB4016871 didn't really fixed the DISM problem. See: Creators update component store shows corruption but unable to repair - Page 11 - Windows 10 Forums

It was still there when 15063.296 rolled out (May 9th). It was fixed internally by Microsoft on last friday, 19th.

As i said, it was done internally by Microsoft. They updated their servers with their fix and once you run the dism command it downloads/interact with whatever it's needed at their end and fixes the problem.

You can read: Creators update component store shows corruption but unable to repair - Page 13 - Windows 10 Forums for a better insight on it.

Also: Use DISM to Repair Windows 10 Image - Page 48 - Windows 10 Performance Maintenance Tutorials where a Microsoft employee replied last friday when the issue was fixed.

EdTittel said:

Thanks, s0urce, but ... Seems to be fixed now. But if KB4016871 isn't what fixed the issue, what else could be responsible? All of my Current Branch installs have now been repaired (6 of them including an Insider Preview for CB on my Surface Pro). Can somebody proffer an alternate explanation, please? See my blog post (referenced above) at for my take on the subject, which I'll be happy to revise if there's a better read on the situation to propound.
Thanks!
--Ed--

As I tested on three PC's after the Cumulative update and it was still not working correctly and then after s0urce posted it was, checked on all three PC's again and it was then working and in view that apparently it still wasn't when offline until after running DISM online, perhaps MS updated a list somewhere removing the problem? Presumably Online will download something if required?
That was a bit of a mouthful but hopefully you get what I meant!

s0urce said:

As i said, it was done internally by Microsoft. They updated their servers with their fix and once you run the dism command it downloads/interact with whatever it's needed at their end and fixes the problem.

You can read: Creators update component store shows corruption but unable to repair - Page 13 - Windows 10 Forums for a better insight on it.

Also: Use DISM to Repair Windows 10 Image - Page 48 - Windows 10 Performance Maintenance Tutorials where a Microsoft employee replied last friday when the issue was fixed.

Yes, the wrong image(s) or maybe placing multiple images on the server and not getting pointed/focused to the correct image one needs.

fwiw... I had removed the 4 keys & 4 files to get Dism working.
Replaced the 4 keys & ran ScanHealth.. showed repairable, ran the RestoreHealth and it downloaded & installed the 4 files.