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

other than opening the apps, no *Smile how am i suppose to get them?

 

Uh just by opening them, if you're not getting them then good. But if anyone else is please respond and if someone finds a solution please post since I wasn't getting these until the creators update.

 

I'm in the same boat as you guys and I'm lucky I found this thread. I'm having an issue with IE 11 crashing on me while I'm doing tests in my university course shell and I'm also running 1703. When I ran sfc it returned no errors so I ran DISM and boom there it was just like for you guys. I tried everything to repair the files but was unsuccessful and did a scan before doing a clean install and found this thread which is a life saver. I'm going to leave well enough alone and look for other sources of IE's issues like the addons.

 

just wanted to say.. i too.. facing the same issue regarding health system report.. and i too also tried multiple attempts on fixing it using the DISM through both elevated PowerShell and CMD.

im glad i found this .. and just wanted to say. im just gonna sit and wait just like most of you here are doing.

 

The only problem i facing is than trying to launch Powershell or CMD in start button with right-click is not working. I need to launch it in other ways.

I dont know if this can be related to some system file corruption.

 

Has anyone tried to see if doing an in-place upgrade corrects the issue? It was to be my next step, but it seems unlikely now since the issue is widespread and seems to have to do with nvidia drivers as well.

 

Yes, kbirger, I did it yesterday, but the issue was still there.

 

There is a way to run DISM successfully in 1703 - do it offline...
Use DISM to Repair Windows 10 Image

As such, it appears there's no real problem with the system as installed, rather with what DISM thinks should be in the system when it's run online. I have no indication other than DISM that there's a 'problem', so I'm not concerned - just waiting for MS to fix it.

 

Apparently there is a serious issue with DISM.....wasted hours and hours trying to get it to work.......

 

Posted in another thread, but applies to this one also. Apparently on my pc, Cortana caused the problem with DISM. I tried to get Cortana to work and suddenly DISM was not able to complete properly. So, I used Macrium Reflect backup image and restored to 2 days ago before I was stupid enough to think Cortana was important - and now all is well with DISM. Lesson learned here!

 

Maybe Microsoft will fix DISM......As Android has now overtaken windows, maybe they will put more resources to solving these problems

 

DISM is broken in the Creators Update. Hopefully, a fix will be out soon. The testing Microsoft performed on the CU was sorely lacking as was the one for the Anniversary Update. This is a big issue Microsoft should be addressing. It is inexcusable to continually distribute packages with errors from a company the size of Microsoft.

 

Apparently this bug was in the last 5 Insider Preview builds before the Creators Update came out. Still, Microsoft managed to not fix it, and launched a major upgrade with this bug. I mean, i love Microsoft, but how can one stand on its side with such situation?

Insider builds exist for some reason.

DISM error code 0x800f081f - how to fix it ? - Windows Central Forums

 

No reason to love them, this new age team is way worse than people in the last decade. They are just working for the sallary without any thinking about customers since their precious windows is still holding monopoly without any real sign of concurrents going strong enough
So, now have windows 10 which is full of phishing bloatwere and unnecessary apps on fresh install which even tend to reinstall themselves if you delete them.
We have cortana which is introduced like it is something major and in fact most users don't even care about it.
Every new build is full of bugs and have stability issues
1703 is the worse. It got release when it clearly wasn't ready for launch but it had to because of the deadline. I am surprised that most off this stuff hasn't been fixed before official launch. Aiming at dism and ICC profiles being ignored by fullscreen games.

 

This is the second time Bree has said this and no one has let it sink in. This is a workaround and it is repeatable/reliable and much better than the idea of modifying the registry.

For those of you that are not understanding what Bree said, most/all installations of Windows 10 have a recovery partition you can boot into.

Procedure:

• You can get to it through Settings > Update & Security > Recovery > Restart Now. This will reboot your machine into the WinPE environment
• You will be greeted with a blue screen that offers options: Continue, Use a device, Usage another operating system, Troubleshoot, Turn off your PC. You can navigate with keyboard and mouse.
  Click Troubleshoot.
• On the Troubleshoot screen, select/click Advanced options.
• On the Advanced options screen, select/click Command Prompt.
• The machine will reboot and enter a recovery console; the screen will include a single command prompt with a working directory of X:. Note: if you have your drive(s) secured with BitLocker, you will need to enter the recovery key. If it is saved to OneDrive, it is able to be seen here: OneDrive BitLocker recovery keys
• In the command prompt run the following commands in order. The first two commands involve navigating to the root of the drive where Windows is installed and creating a scratch directory for DISM. These commands presume your installation of windows is on the C: volume and that Windows is in the subfolder ./windows/; if you have other volumes/directories, modify the commands appropriately. SFC defaults to the settings I entered below, but if you're repairing more than one volume, or are using another PC to repair a drive from another, just change the applicable parts of the command. DISM is all that is really necessary, but might as well run an SFC while you've already gone this far.
  c:
  mkdir scratchdir
  dism /Image:c:\ /Cleanup-Image /RestoreHealth /LimitAccess /ScratchDir:c:\scratchdir\
  sfc /SCANNOW/ OFFBOOTDIR=c:\ /OFFWINDIR=c:\windows\