Creators update component store shows corruption but unable to repair

reddwarf4ever · 21 Apr 2017

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

TexasBandit · 21 Apr 2017

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.

s0urce · 21 Apr 2017

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

Dyabzhee · 21 Apr 2017

s0urce said:

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.

peterfnet · 21 Apr 2017

Bree said:

That is the safest approach, and the one I'm taking. In the mean time, it's known that an offline repair works, should it be needed.

Bree said:

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.

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\

fdegrove · 21 Apr 2017

Hi,

This is the second time Bree has said this and no one has let it sink in.

That's just one side of the issue really.
Deleting the reg keys or running DISM in safe mode amount to the same.Hence, etc. etc.

Bottom line, most systems do not have the problems DISM suggests they have and yes, MS should have fixed this long ago.
And yes, MS should also not rush out such a major release without resolving this first.

Creators Update also comes with other problems that are much more difficult to resolve.

Cheers,

peterfnet · 21 Apr 2017

I have to disagree. I don't see either of methods as being solutions.
The registry changes were billed by some as a workaround for that specific package. I see it as hiding the problem and not fixing the root cause.

The offline method of running DISM is a workaround for not being able to fix it online, but it does resolve the root cause.

Neither should be considered final resolutions and should still be fixed by Microsoft.

fdegrove · 21 Apr 2017

Hi,

I have to disagree. I don't see either of methods as being solutions.

Actually, you do agree but do not understand why.
Both workarounds achieve the same thing: DISM is being fooled.

I'd like to hear from people claiming running DISM either way actually and factually resolved anything when sfc /scannow did not throw up an error in the first place.

Best and welcome to this Forum

peterfnet · 21 Apr 2017

fdegrove said:

Actually, you do agree but do not understand why.
Both workarounds achieve the same thing: DISM is being fooled.

Been a long-time lurker, decided to actually sign up for this thread. Thank you for the warm welcome.

Can you clarify as to my misunderstanding? How is DISM being fooled when running in an offline capacity?

fdegrove · 21 Apr 2017

Hi,

It ignores the registry entries, that's why.

Cheers,