Creators update component store shows corruption but unable to repair

EdTittel said:

More interesting data: reading up on using DISM I learned that it sometimes has more difficulty with esd files than with wim files. The install file in the Media Creation Tool version of 1703 is install.esd. So I hied me off to MSDN and downloaded the latest and greatest ISO file from there and found exactly the same repair issue from that supposedly more usable, DISM friendly version:

I'll be blogging about this tomorrow, but it seems pretty clear that whatever is causing the issue with component store corruption is (a) coming from Microsoft and (b) not currently fixable through ordinary DISM measures. I've now tried both the ESD file from the media I used to upgrade my OS and the WIM file from the MSDN ISO, both with the same failure.
Very interesting!
--Ed--

Yeah. Could you also check administrative event viewer errors If it is not a problem? I keep getting them on every install

No change after today's Cumulative Update KB4015583 Windows 10 v1703 Build 15063.138

Code:

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
[===========================98.7%========================= ]
Error: 0x800f081f
The source files could not be found.

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::ProcessCmdLine_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?

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.