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

Wouldn't it be better just to wait for Microsoft to fix it eventually, I know they are bad about this but they usually fix the issue.

 

Initially, I have deleted the wrong keys. Those I have restored.

Then I deleted the right keys (see post #39). Those I have not restored. Those I have deleted from my system.

I have not faced any issue. I am not facing any issue, and I will not face any issue -- that is my belief.

- Can you prove to me that the keys I have deleted from my Registry and from my system, completely, will provoke any problem to me? Please use facts. Otherwise, please do not bother. All I did was to prove with screenshots that in my system DISM works, the way it works. I have NOT suggested this to anyone!

As for waiting for Microsoft to fix this.... I think that this issue has been reported a lot and it is present for quite some time now... Not sure...

I AM SURE about another issue though: after each upgrade the NVIDIA driver has to be re-installed or clean-installed, due to the crippled openCL.dll files, in System32 and SysWoW64! I have shown this, very recently, with screenshots!

Use DISM to Repair Windows 10 Image - Page 40 - Windows 10 Performance Maintenance Tutorials


Do you know for HOW LONG this issue exists?? Personally, I have reported this MONTHS ago! In my Feedback Hub I have this report, and others reported it as well, and we are all upvoting, and reporting, and an Engineer from Microsoft has been informed or something like that and NVIDIA has also released a Creators Update driver!

And still, I needed to clean install the driver...

So, yeah, thanks for your patience.

 

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.

 

Hi,

My main point is that DISM isnt working properly leading people into believing there's something wrong when there isn't.
Provided SFC /SCANNOW is not returning any error then all is fine.
Dism actually does find the source, it just does not find the refrence it's told to look for, that's all.

Cheers, *Wink

 

what do u mean by browser does not work?

 

Same here I would only use DISM if there was a problem that affected my use of my PC's and as I have images to restore from, I'm not going to burst a blood vessel over this.

 

Could this also be in relation in to Even ID 6281 an audit failure? I had made a topic on the discussion forum I'll post the text here.

" Code Integrity determined that the page hashes of an image file are not valid. The file could be improperly signed without page hashes or corrupt due to unauthorized modification. The invalid hashes could indicate a potential disk device error.File Name: \Device\HarddiskVolume2\Windows\System32\WinMetadata\Windows.Graphics.winmd

Code Integrity determined that the page hashes of an image file are not valid. The file could be improperly signed without page hashes or corrupt due to unauthorized modification. The invalid hashes could indicate a potential disk device error.File Name: \Device\HarddiskVolume2\Windows\System32\Windows.UI.dll"

I had later found out that if I open the Netflix or Hulu app, it will give me the audit failure. Now I can use the apps with usually no problems, though oddly Netflix gives me an error when I first try to open it while opening it the first time, but then it will work fine. Hulu opens fine too, as well as Edge browser. Yet it stills gives me the audit failure even when I watch Netflix through Edge browser. Also deleting Edge browser history gives an audit failure too, Event ID 5061.

I can still use the store and download apps and use them, but I may avoid them for now. I don't any problems but its still very annoying.

 

Creator update is the worst upgrade by MS ever. Except for a few measly and intangible improvements (if there is any! and if it is ever noticeable by average user!) the rest is a total failure. I repair installed Windows four times because I thought something might have messed up in my Windows since DISM started to give the same error. This was until I reviewed the log, googled the error and found this thread. I was about to fresh install Windows and lose all my programs and settings. Why they had to remove 'Control Panel' item from 'Start' right click menu? or Why replacing Program and features in the same menu with Apps and Features? Also 'Scheduled disk checking' of system drive at boot (via command prompt) doesn't work. Why they had to take something that was already working as expected and break it? Just for the sake of doing something? Whoever was in charge of this upgrade project was a total idiot, period. Interesting part is not only they didn't test DISM for themselves before releasing to public at least, still they are silent about the mess they've made.

 

Could you check to see if you have any audit failures such as Event ID 6281, usually they are caused by opening the Netflix or Hulu app and will appear in the event viewer

 

Is there any way to search event viewer by event ID? otherwise on my system there are too many events which makes it virtually impossible to search one by one.

 

Just check on event viewer for audit failures if you have any Audit Failures, they appear under Audit success, if you don't test by opening Hulu app or Netflix app, if you don't have them download them from the Windows store and then test.

 

Yes. It's in the Actions pane to the right, click on 'Filter Current Log...'

 

No failure so far... all success

 

Thanks for the tip

 

Hmm did you test to see if you could get them