Component store has been corrupted. (0x80073712) and Error: 14098

Intrepid-NY
Intrepid-NY used Ask the Experts™
on
Windows Server 2012R2 Essentials
RE:  StartComponentCleanup Task fails
DISM giving contradictory results  

My StartComponentCleanup task in Tasks Scheduler was failing with the error:
Last Run Result:  The component store has been corrupted. (0x80073712).

The task is located in Task Sheduler under  Microsoft, Windows, Servicing
 
No problem, I thought - over to elevated command prompt and DISM.


>DISM /Online /Cleanup-Image /ScanHealth
Deployment Image Servicing and Management tool
Version: 6.3.9600.17031
Image Version: 6.3.9600.17031
[==========================100.0%==========================]
No component store corruption detected.
The operation completed successfully.


OK Great, should be ready to clean.


>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

Odd, let’s fix that up.

>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.

Let’s be safe and re-scan.

>DISM /Online /Cleanup-Image /ScanHealth
Deployment Image Servicing and Management tool
Version: 6.3.9600.17031
Image Version: 6.3.9600.17031
[==========================100.0%==========================]
No component store corruption detected.
The operation completed successfully.


And on to cleanup


>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


I’m totally at a loss. How can it report as non-corrupted, repaired and corrupted all in quick succession????
Unsure how to fix.    Windows Updates works fine and we have no other symptoms except that the StartComponentCleanup Task always fails as explained above.

Thank You.
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Have you rebooted the server?

Author

Commented:
Yes rebooted.
Then you need to inspect the C:\WINDOWS\Logs\DISM\dism.log to see what it thought was corrupted and it will probably be a third party driver or utility as  the DISM commands you have been running replaced CHECKSUR, using Windows Update to fix any corrupted Windows entries.
Exploring ASP.NET Core: Fundamentals

Learn to build web apps and services, IoT apps, and mobile backends by covering the fundamentals of ASP.NET Core and  exploring the core foundations for app libraries.

Author

Commented:
I don't see an obvious solution it the log files.   Can anyone help analyze these (short) log files?  Thank You!

I have attached:

Fresh Log Files generated after this command with corrupt message:  DISM /Online /Cleanup-Image /StartComponentCleanup
CBS [StartComponentCleanup].log
dism [StartComponentCleanup].og

Fresh Log Files generated after this command with success message:  Dism /Online /Cleanup-Image /RestoreHealth
CBS [RestoreHealth].log
dism [RestoreHealth].log
CBS--StartComponentCleanup-.log
CBS--RestoreHealth-.log
dism--StartComponentCleanup-.log
dism--RestoreHealth-.log
-------------------------------------------------------------------------
SOLUTION:  Antivirus Conflict
It was ESET File Security for Microsoft Windows Server v.6.3.12010.0
Added an exclusion for C:\Windows\WinSxS
Also added an exclusion for process dism.exe
-------------------------------------------------------------------------
Good job! I told you it was a third party problem; though, ESET should have fixed that, long ago.

Author

Commented:
-------------------------------------------------------------------------
SOLUTION:  Antivirus Conflict
It was ESET File Security for Microsoft Windows Server v.6.3.12010.0
Added an exclusion for C:\Windows\WinSxS
Also added an exclusion for process dism.exe
-------------------------------------------------------------------------

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial