SFC Says All OK, DISM Has Issues!

TexasBandit · 28 Aug 2018

I have a question regarding SFC and DISM. After a whole lot of frustration, I finally have 1803. I checked both SFC and DISM following that. SFC /Scannow ran with an error. I ran it again, and the error was resolved. Then for curiosity, I ran DISM. Low and behold, it had a problem. What gives? I have attached a screen shot of the situation. I just do not understand why one is just fine, and the other has problems. I tried to correct DISM, but the source could not be found (as usual). I don't understand why the source isn't found because the image and my "real" system should be identical at this point. They have the exact same version number!

SFC Says All OK, DISM Has Issues!-screenshot-1-.png

Thanks

Clintlgm · 28 Aug 2018

So check health is reporting the component store can be repaired then you need to run
Dism /Online /Cleanup-Image /RestoreHealth
Dism /Online /Cleanup-Image /StartComponentCleanup

lx07 · 28 Aug 2018

Delete these 2 files - just to drop old attempts and make them smaller to upload:

C:\Windows\Logs\CBS\CBS.log (this is the sfc log)
C:\Windows\Logs\DISM\dism.log (this is the dism log)

Then run DISM (as @Clintlgm said above) and then sfc /scannow and then upload the new version of the 2 files. There is no private information in them.

See here for details : Use DISM to Repair Windows 10 Image | Windows 10 Tutorials

It probably isn't an issue but we would need to see the logs to see what is the cause.

TexasBandit · 28 Aug 2018

The first screen shot is the results in PowerShell. The second attachment is the DISM log. The CBS log was too big. Thanks for taking a look at this for me. I really appreciated it.

lx07 · 28 Aug 2018

Nothing interesting in that log I could see.

Try downloading a ISO from MS (you are on 17134 so latest should be fine). Mount the ISO then try this (changing X to whatever drive.

dism /online /cleanup-Image /restorehealth /source:wim:X:\sources\install.wim:1 /limitaccess

Upload the CBS log (you can zip it if it is big) if it doesn't work.

TexasBandit · 28 Aug 2018

Thanks for taking a look. I'll have to take a look at it tomorrow ... time for social stuff.

EdTittel · 29 Aug 2018

As for the error you're seeing: it simply means that when DISM consults its local sources (your OS image, primarily files in the WinSxS folder hierarchy) it can't find what it's looking for. The reason for supplying an alternate source is to give it someplace else to look. These kinds of errors do come up from time to time (last year we had a run of issues with flight related variables associated with the Microsoft update tracking tools) that took a while for MS to fix (these were outside user control). The CBS.log file should show you which items DISM can't find at which point you can determine if repairs will work or not.
HTH,
--Ed--

TexasBandit · 29 Aug 2018

Thanks for the replies folks. Microsoft is really getting to be a pain!

I am attaching the CBS log to see if you guys can get anything from it. Thanks again ...

EdTittel · 29 Aug 2018

Indeed there are a bunch of elements missing from your component store (search the CBS log file for "missing" and you'll immediately see what I mean). Later on you'll also see a bunch of CSI Manifest Corrupt messages as well. Looks like you will have to download a known good install.wim file to act as a source for your repairs. You MUST match the following characteristics to succeed:
1. Language
2. Bittedness (32- or 64-bit)
3. Edition (Home, Pro, Enterprise, Education, etc.)
4. Version works best if it's the same as your running OS
See section 6 of Brink's excellent tutorial Use DISM to Repair Windows 10 for details on the Source parameter.
HTH,
--Ed--

TexasBandit · 29 Aug 2018

Still no good answers.

I want to know why the DISM command in the attached screen print cannot find the source. Below is a list of the contents of the drive D, which was mounted following an ISO download. And yes, the ISO is the same version as my system. I would really like to know why it cannot find the source when it is clearly mounted as drive D.

Thanks