[SOLVED] [W8.1Upd3 x86] Compon. store corr. err. 14098 reported by DISM /StartComponentCleanup

Canofindit

New member
Joined
Aug 24, 2017
Posts
2
When checking a problem with another computer I checked my own and found error reported in the component store. See cmd window below:
C:\Windows\system32>dism /online /cleanup-image /restorehealth
Deployment Image Servicing and Management tool
Version: 6.3.9600.17031
Image Version: 6.3.9600.17031
[==========================100.0%==========================]
The restore operation completed successfully. The component store corruption was repaired.
The operation completed successfully.
C:\Windows\system32>dism /online /cleanup-image /startcomponentcleanup
Deployment Image Servicing and Management tool
Version: 6.3.9600.17031
Image Version: 6.3.9600.17031
[==========================100.0%==========================]
Error: 14098
The component store has been corrupted.
The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
The computer is a tablet with windows 8.1 and all latest windows update patches. the /RestoreHealth operation says that the store was repaired but the /StartComponentCleanup operation aborts with error 14098.

There are no other obvious symptoms of corruption. I included the SFCFix output and the DISM and CBS logs. I can see that there is at least a baseline error reported. But SFCFix does not find it ?

Can you help, please to solve this issue as I have another tablet where the store does not work but I need to understand this issue first, please. Thanks for your help.
 

Attachments

Re: Component store corruption error 14098 reported by DISM /StartComponentCleanup

Hi and welcome to Sysnative. Sorry for the delay. Are you still in need of assistance?
 
Re: Component store corruption error 14098 reported by DISM /StartComponentCleanup

Thanks for reply. In fact I did manage to fix it, at least I hope I did. I found out that the errors reported in the cbs log pointed to component store files that were somehow not delta compressed. No idea why this could have happened. It is certainly not a user error. I had another computer with exactly the same configuration and copied over the delta compressed files replacing the larger originals in the WinSxS directory. That should be safe since these were all versions no longer in use. And see there, the dism error 14098 was gone. I could do /startcomponentcleanup successfully.

But if you have copies of WinSxS installations on your servers, perhaps the SFCFix tool could have assisten in this situation ?
 

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

Back
Top