Creators update component store shows corruption but unable to repair

This DISM problem is now on his 9th build and counting without getting fixed...

Redbatman said:

Damn, other that this has anyone else getting other issues with Creators Update, just curious.

One other issue that seems to have affected all on the Creators Update appears to have been fixed in 15063.296
Chkdsk not working?

I'm still wondering why certain Apps like Hulu and Netflix give me an Audit failure with event id 6281. Is it possible that this issue with the component store corruption is the reason why I'm getting the audit failure?

Worked perfectly! I had been trying to figure out how to fix this problem for the past month. Eagle51's solution did the trick. So happy now that it's resolved.

Eagle51 said:

Home x64 Creators Edition - Updated with Windows 10 Update Assistant
Version 1703 Build 15063.138

I'm NOT recommending this as a fix, just my observation and what I did...Do at your own risk :)

I was having the same issue with DISM (component store corrupt, repairable) and getting the
"Error: 0x800f081f The source files could not be found, etc.

In ScanHealth Details - CBS Corrupt MUM - Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.15063.0

I mounted the install.wim and did a search for it, no results found.
I did a search on my C: drive for it, no results found:
I did a search in the Registry and found it at the following 2 locations:

1st Loction:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageIndex\Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~0.0.0.0]

2nd Location:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.15063.0]

Exported, then Deleted the 2 Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.15063.0 KEYS ONLY
Note: They were already owned by Administrators, but I had to give Administrators Full Control to be able to delete them.

No More DISM issues and I have NOT seen any side effects (ie ... event warnings,errors,etc)

Should we just revert back from creators update? And wait until later to reinstall it?

1st Loction: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Package[COLOR=#ff0000 said:

Index[/COLOR]\Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~0.0.0.0]

2nd Location: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.15063.0].

I deleted the Reg key of the 2nd option, because I couldn't find the string with the word "Index".
Instead I have this key:
Microsoft-Windows-TestRoot-and-FlightSigning-WOW64-Package~31bf3856ad364e35~amd64~~10.0.15063.0

Left it as it were, deleted the 2nd option and then ran /RestoreHealth and DISM reported that the operation completed.

Gonna leave it at that because sfc/scannow doesn't find any problems... for now LOL

Thanks to everyone who participated in this thread!

Dism /online /cleanup-image /restorehealth worked today on version 1703 build 15063.296

Windows PowerShell
Copyright (C) 2016 Microsoft Corporation. All rights reserved.

PS 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 did not find any integrity violations.
PS C:\Windows\system32> dism /online /cleanup-image /checkhealth

Deployment Image Servicing and Management tool
Version: 10.0.15063.0

Image Version: 10.0.15063.0

The component store is repairable.
The operation completed successfully.
PS 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.
PS 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.
PS C:\Windows\system32>

So it's fixed now?

Redbatman said:

So it's fixed now?

Just checked on two PC's 1703 build 15063.296 one Home and one Pro and in both cases it completed successfully, so it seems to have been fixed, not sure how or when as I tried it after the last cumulative update and it wasn't then.

Yes, it is fixed now. Finally.