Creators update component store shows corruption but unable to repair

EdTittel. While I appreciate the response, I don't think you fully looked at the log entries I posted in my original post. While my laptop does indeed have a nvidea graphics card, if you look at the log file entries, none of the errors that it returns are associated with oem0.inf (which I realize is a nvidea driver file), or any inf file for that matter. Other than the error concerning not being able to set the DLL search path to the servicing stack folder (which should be C:\windows i suppose), the only other two errors which are encountered during the DISM operation have to do with failing to load "providers" (whatever providers are), and they are dll files. The two log entries are as follows:

2017-04-11 12:36:01, Warning DISM DISM Provider Store: PID=23072 TID=24252 Failed to Load the provider: C:\Users\whiggs\AppData\Local\Temp\BB4A7318-151D-4606-9F4A-81DB7ED04B5D\PEProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

2017-04-11 12:36:01, Warning DISM DISM Provider Store: PID=23072 TID=24252 Failed to Load the provider: C:\Users\whiggs\AppData\Local\Temp\BB4A7318-151D-4606-9F4A-81DB7ED04B5D\EmbeddedProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

Furthermore, the whole issue concerning the Windows package file with the invalid digital signature (even when pulled from the install media) is concerning as well:

These Files Are Possibly Corrupt (Bad Digital Signature): (Total: 1)C:\Windows\servicing\Packages\Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.15063.0.mum¦ 1 Combined Problems were found with the packages files, these files need to be replaced (These mainly only effect installing Windows Updates.)¦ The SFC (System File Checker) doesn't scan and replace some of these files, so you may need to replace them manually.

I fail to see how any of these issues have anything to do with the nvidea driver. Please re-read my previous post, as the blog you sent me to is not in any way relevant to my issue. The only similarity is the error message. Also, I would highly recommend downloading and running the Windows all in one repair pre-scan for yourself so you can verify the corrupt windows package. Seeing firsthand is believing.

One computer I've completely upgraded from windows 10 1607 to windows 10 version 1703 build 15063.138. I'm checking sfc /scannow and the 3 DISM commands.

I got the same display that the source files could not be found.

If you use a windows 10 iso that is the same version and build it is supposed to be able to use the iso as the source files. I have not yet tried to see if that works to display that the restorehealth completed successfully.

I've viewed the DISM log file and there were lots of failed to load the provider as well as a lot of failed entries.

zbook said:

If you use a windows 10 iso that is the same version and build it is supposed to be able to use the iso as the source files. I have not yet tried to see if that works to display that the restorehealth completed successfully.

I have - it fails. See Post #6 in this thread.

At last! A way to run DISM successfully has been found for the Creators Update.
Use DISM to Repair Windows 10 Image

Same shit started to happen to me today too. Funny after I saw this topic I did a dism check after creators update installed and everything came back fine, but today same error as everybody else, sigh Microsoft.

Do you guys have any problem checking for updates (does it take too long)?

I'm also getting "The component store is repairable." and when i check for updates it takes ages for it to report back.

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)

I have found on two computers that the in C:/Program Files/WindowsApps the data for the app gets corrupted and that prevents the app from updating of not working properly. I have not had the problem with the Store app but with the Money app and the Camera app. I needed to delete the data pertaining to the app to correct the problem and then I was successfully able to reinstall the app. Microsoft protects this folder and I could not figure out how to access it in Windows, so I booted from the Windows install disk and used the DOS repair function to go into this folder and delete the app files.

1. I followed the procedure explained by Eagle51 and found it successfull. After doing that, everything was perfect: CheckHealth, ScanHealth, Restore Health, sfc ... everything related with DISM. So, many thanks and congratulations to Eagle51!!!.
2. Just to make a double-check, I imported back to the registry the two keys mentioned by him:

• [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageIndex\Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~0.0.0.0]
  
  
• [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.15063.0]
  

and previously exported to my Desktop, as Eagle51 explained ... and the DISM RestoreHealth error was again there.

But, what I would like to know is if someone has found a definitive solution (without having to edit the registry) until MSFT decide to repair this problem in any way.