[SOLVED] DISM error 14098

axe0

Administrator,
BSOD Academy Instructor,
Security Analyst
Staff member
Joined
May 21, 2015
Posts
3,509
Location
Holland
After I installed the updates from patchday I ran
Code:
sfc /scannow
Dism /online /cleanup-image /scanhealth
Dism /online /cleanup-image /checkhealth
Dism /online /cleanup-image /analyzecomponentstore
Dism /online /cleanup-image /startcomponentcleanup
SFC didn't detect any problems, however after startcomponentcleanup wass finished I get error 14098 with the message that componentstore is damaged.
SFCFix can't find anything after rebooting and SFC again, but as soon as I run startcomponentcleanup again error 14098 shows up and what SFCFix says is shown in the picture

CBS logs will follow soon, DISM logs have been uploaded just in case they're needed
EDIT: haven't been able to upload the CBS log, link to CBS in onedrive: Microsoft service

DISM corruption.png


SFC result
SFCFix version 2.4.9.2 by niemiro.
Start time: 2016-02-10 12:46:55.958
Microsoft Windows 8.1 Update 3 - amd64
Not using a script file.





AutoAnalysis::
SUMMARY: No corruptions were detected.
AutoAnalysis:: directive completed successfully.




Successfully processed all directives.
SFCFix version 2.4.9.2 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2016-02-10 12:48:11.487
----------------------EOF-----------------------

View attachment DISM.zip
 
Hi axe0 :)

According to your DISM.log, DISM must have fixed whatever corruption it reported, because your SURT log is clean.
Code:
=================================
Checking System Update Readiness.


Summary:
Operation: Detect and Repair 
Operation result: 0x0
Last Successful Step: Entire operation completes.
Total Detected Corruption:	0
	CBS Manifest Corruption:	0
	CBS Metadata Corruption:	0
	CSI Manifest Corruption:	0
	CSI Metadata Corruption:	0
	CSI Payload Corruption:	0
Total Repaired Corruption:	0
	CBS Manifest Repaired:	0
	CSI Manifest Repaired:	0
	CSI Payload Repaired:	0
	CSI Store Metadata refreshed:	True

Total Operation Time: 239 seconds.
 
Hi Aura,

Yes, I was getting indeed clean results on all commands but the startcomponentcleanup command.
SFCFix came clean after a reboot (or sfc scan), but when startcomponentcleanup command was finished (took only a few seconds everytime) the corruption was back as the screenshot shows.

I have restored a Macrium image of a few days ago and am currently in the process of installing the updates again to find out what update(s) caused this problem.

I'll update this thread as soon as I find it out or can say it hasn't returned.
 
Thanks for letting us know axe, we'll keep it in mind if we ever encounter the same kind of issue :)
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top