A adriantc New member Joined Sep 16, 2016 Posts 1 Sep 16, 2016 #1 Hello. I have been trying to do a component clean (like I always do as part of my cleanup routine), but that fails with error 14098. Then I have tried to scan and weird enough there is no corruption. However if I run restorehealth it seems that the corruption has been fixed. But if I again try to run component clean I get the same error (attached is the log for this series of commands... View attachment dism.log). Also I have tried sfc /scannow and that doesn't return any errors. The same for SFCFix. It doesn't detect anything wrong. Updating seems to work and I don't know for how long this error is happening. Could you help me out?
Hello. I have been trying to do a component clean (like I always do as part of my cleanup routine), but that fails with error 14098. Then I have tried to scan and weird enough there is no corruption. However if I run restorehealth it seems that the corruption has been fixed. But if I again try to run component clean I get the same error (attached is the log for this series of commands... View attachment dism.log). Also I have tried sfc /scannow and that doesn't return any errors. The same for SFCFix. It doesn't detect anything wrong. Updating seems to work and I don't know for how long this error is happening. Could you help me out?
zcomputerwiz Windows Update Expert Joined Jan 10, 2015 Posts 5,185 Location USA Sep 22, 2016 #2 Please try running DISM with the component cleanup options again. When it fails, zip and attach CBS.log with your reply.
Please try running DISM with the component cleanup options again. When it fails, zip and attach CBS.log with your reply.