Creators update component store shows corruption but unable to repair

I just wanted to add that since my previous posts I have clean installed 10 and the issues I was having are gone. The creators update no longer generates DISM errors when performing a scan so my issues cleared up with a clean installation.

HRPuffnstuff said:

The creators update no longer generates DISM errors when performing a scan so my issues cleared up with a clean installation.

You may not have needed the clean install. Mine works today without having done anything at my end.

As @s0urce says, Microsoft appear to have done something at their end.
Use DISM to Repair Windows 10 Image

Bree said:

You may not have needed the clean install. Mine works today without having done anything at my end.

As @s0urce says, Microsoft appear to have done something at their end.
Use DISM to Repair Windows 10 Image

I was having other issues that precipitated the clean install. To be honest it doesn't take me very long to put it back together as I cloud as much as I can along with backups. My biggest issue is deauthorizing the software on the machine that requires it so I don't run into activation issues when I reinstall it.

I actually prefer to do a clean install periodically and since this build was over a year old combined with the other software induced issues I was having it only made sense to do it now. If I am able to build a new machine later this year I will do it again.

Obviously I know about the registry hack but not gonna do it, what if DISM starts making errors because of the deleted keys? Anyway, at this point, dism's producing 0x800f081f on my build if you restrict internet access wih /limitaccess, like the previous poster wrote.

oh microsoft said:

Obviously I know about the registry hack but not gonna do it, what if DISM starts making errors because of the deleted keys? Anyway, at this point, dism's producing 0x800f081f on my build if you restrict internet access wih /limitaccess, like the previous poster wrote.

Yes, I have avoided the temptation to hack the registry too, and for the same reasons as you..

It was @s0urce who very helpfully tested with and without internet access to help diagnose why mine was still failing, despite Microsoft apparently had done something at their download servers to fix this problem. Seems I just had to wait a little longer for the fix to ripple out across all MS's servers.

I can report that, following successfully running DISM with internet access downloading and completing repairs, It now runs successfully without internet access. This command previously failed with the 0x800f081f error, it now runs to 100% without error.

Bree said:

Yes, I have avoided the temptation to hack the registry too, and for the same reasons as you..

It was @s0urce who very helpfully tested with and without internet access to help diagnose why mine was still failing, despite Microsoft apparently had done something at their download servers to fix this problem. Seems I just had to wait a little longer for the fix to ripple out across all MS's servers.

I can report that, following successfully running DISM with internet access downloading and completing repairs, It now runs successfully without internet access. This command previously failed with the 0x800f081f error, it now runs to 100% without error.

Did the same just right now. Yep, I can confirm that as of build 15063.296 to fix DISM error 0x800f081f you need first to run DISM in online mode, without /limitedaccess flag. Then, you can run it offline if you want, you'll get your 100%. Now, lets make bets: how many builds the situation will hold till it's broken again, heh?

EdTittel said:

Seems to be fixed now. But if KB4016871 isn't what fixed the issue, what else could be responsible?

Hi @EdTittel. Up to 19th May DISM's restorehealth failed on my 15063.296. After the 19th it worked - without any new update to my system, or anything that I did at my end.

It would seem that the 'source not found' error was not just referring to finding the source on the local PC, but also to a failure to find a valid download for the package on MS's servers. This would appear to be what @s0urce says MS have fixed 'internally'.

Whether or not KB4016871 is a prerequisite is a moot point (I suspect not). What is essential is to run DISM once more now that MS have fixed things at their server end so that the working packages can be downloaded and the repair completed to 100%.

CBS.log shows...

Code:

2017-05-20 10:08:53, Info                  CBS    DWLD: Windows update server URL: http://download.windowsupdate.com/d/msdownload/update/software/tool/2013/08/dummyrepairpackage_cd97f5d6cb54bf63a4e4adc376edadf6f2b8352c.cab
 2017-05-20 10:08:53, Info                  CBS    DWLD:Content is Full-Cab package.
 2017-05-20 10:08:53, Info                  CBS    DWLD: Windows update server URL: http://download.windowsupdate.com/c/msdownload/update/software/tool/2017/05/kb3089227-amd64-neutral-neu-10_2bbf7b24607be526c98e5c7ee3a4fe70e3f42df6.cab
 2017-05-20 10:08:53, Info                  CBS    DWLD:Content is Express package.
 2017-05-20 10:08:53, Info                  CBS    DWLD: Windows update server URL: http://download.windowsupdate.com/c/msdownload/update/software/tool/2017/05/kb3089227-amd64-neutral-neu-10_4a5ac2e79762e347df4df15d435db8eef8abb084.psf
 2017-05-20 10:08:53, Info                  CBS    DWLD:Content is Express package.

...I've just manually downloaded the .cab file for that kb3089227. It does contain, amongst (many) other things...
microsoft-windows-testroot-and-flightsigning-package~31bf3856ad364e35~amd64~~10.0.15063.0

Creators update component store shows corruption but unable to repair

All credits go to @s0urce for spotting on Reddit where a Microsoft employee said they had fixed it.
Use DISM to Repair Windows 10 Image

Its fixed for me too.