Windows 10: Creators update component store shows corruption but unable to repair

Thanks, Bree: good to know. This could be a while, then...
--Ed--

 

Thanks, Bree: good to know. This could be a while, then...
--Ed--

 

Hey guys. I also have this issue as well. I have installed numerous windows 10 creator update os installations (4 total) and every single one has exhibited the exact same issue. It was a major pain that ate up 2 days (because Microsoft scheduling is just crap like that and every customer support rep has to walk you through troubleshooting steps you have already tried so they can figure out for themselves that it is not an issue that they can fix), but I was able to actually speak to a level 2 tech at Microsoft who (after also going through the exact same troubleshooting steps myself and every other tech before her had already tried, while I am ripping my hair out), gathered the dism logs concerning the issue to send off to the software engineers. It shocks me just how incompetent a level 2 engineer from Microsoft can be concerning not a single one of the technicians or level 2 ever actually looked at the DISM log files for information as to the cause of the issue and I was forced to verbally re communicate the contents of the log files, since they were unable to read. But I digress, what I find most interesting is, if you download Tweaking.com's Windows all in one repair tool (Tweaking.com - Windows Repair Free/Pro), and perform a pre-scan of the operating system (which entails scanning for missing or corrupt packaging files, scanning the environment variables, and the reparse points for the operating system), in every single operating system that the Creators update Version of Windows 10, the following result is returned by the scan: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.Interesting right? The aspect that I find even MORE interesting is that even when I extracted the exact same file from the Creators update installation iso "install.wim" and replace the supposed corrupt file with the brand new one, when I re-run the scan, no change at all. This may explain the cause of DISM failing, considering that DISM (if no source is specified) downloads the files it needs from Windows update. Also, looking at the log file (I deleted the old log file and ran the scan so that I would have only the errors associated with a single run), the following are the warnings and errors that were reported:2017-04-11 12:36:01, Warning DISM DISM OS Provider: PID=23072 TID=24252 Unable to set the DLL search path to the servicing stack folder. C:\Windows may not point to a valid Windows folder. - CDISMOSServiceManager::Final_OnConnect2017-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)

2017-04-11 12:42:37, Info DISM DISM Package Manager: PID=23072 TID=25464 Error in operation: source for package or file not found, ResolveSource() unsuccessful. (CBS HRESULT=0x800f081f) - CCbsConUIHandler::Error

2017-04-11 12:42:37, Error DISM DISM Package Manager: PID=23072 TID=24252 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x800f081f)

2017-04-11 12:42:37, Error DISM DISM Package Manager: PID=23072 TID=24252 Failed processing package changes with session option CbsSessionOptionRepairStoreCorruption - CDISMPackageManager::RestoreHealth(hr:0x800f081f)

2017-04-11 12:42:37, Error DISM DISM Package Manager: PID=23072 TID=24252 The source files could not be found; their location must be specified using the /source option to restore the feature. - GetCbsErrorMsg

2017-04-11 12:42:37, Error DISM DISM Package Manager: PID=23072 TID=24252 Failed to restore the image health. - CPackageManagerCLIHandler:rocessCmdLine_CleanupImage(hr:0x800f081f)

2017-04-11 12:42:37, Error DISM DISM Package Manager: PID=23072 TID=24252 Failed while processing command cleanup-image. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800f081f)

Now I don't know what a provider is, but I find it odd that DISM is looking for it in the temporary directory of the current user. I also find it odd how it is unable to recognize C:\windows as a folder. Any thoughts?

 

I blogged about this further this morning (Creators Update Image Integrity Gotcha - Windows Enterprise Desktop). The only machines I have that manifest this problem have Nvidia graphics cards, and the error centers around the inability to find the Nvidia sound driver (NVIDIA High Definition Audio). This is highly reminiscent of last year's troubles with elements of the Nvidia graphics driver environment. Hopefully, MS and Nvidia will be able to synch up for the next cumulative update and get this fixed.
--Ed--

PS: I'm not sure this has any bearing on the preceding post. In particular the error message about C:\Windows is entirely different from what I'm seeing, and FWIW, I agree that this oversight or omission is cause for consternation if not concern. It also diagnoses like a Microsoft problem, however, just like the error I ran to ground on my local machines.

 

My Surface Pro 3 is exhibiting this same behavior. Reinstalling Edge through the delete and powershell does not fix the issue. I do not have an NVidia card, just integrated graphics.

When I open Edge, it shows a blank white page and force quits eventually (or I kill it in task manager). Tried off the domain, new user, deleting edge folder in safe mode. Nothing seems to work. SFC comes out clean, DISM is exhibiting the same behavior trying to repair from ESD file (ISO and Media Creation Tool USB).

 

All in all, it has been really buggy update for me.

Dism is broken.

Games ignore nvidia color profiles.

Also, I have worse performance overall on benchmarks with random microstutters.. Made multiple clean installs. My only guess is that drivers are still not compatible with Creators update.

Lots of event viewer errors.

 

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.

 

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 *Smile

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.

 

I explored the install.wim with 7zip and did find all the files in both the index 1 and index 2 folders.

The files are also installed on my system.

Paths where I found the files reference index 1 but like i said before index 2 had them as well.

install.wim\1\Windows\System32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}







install.wim\1\Windows\servicing\Packages