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


  1. Posts : 108
    Win10
       #1

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


    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.


    =========================

    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 Attachment 133651
    dism [StartComponentCleanup].og Attachment 133653

    Fresh Log Files generated after this command with success message: Dism /Online /Cleanup-Image /RestoreHealth
    CBS [RestoreHealth].log Attachment 133650
    dism [RestoreHealth].log Attachment 133652
      My Computer


  2. WOT
    Posts : 471
    Win 10 Pro 15063.332 (ex-Insider)
       #2

    Hi Intrepid1,

    I see you have posted your issue in a multitude of online forums so I am hoping someone can help you; however, I do not think I can personally help you; however, even though you presented your issue very well, I don't see where you posted the specific issue it was causing (if any). With that said, have you considered trying to run the component store cleanup with the /ResetBase switch?:

    Dism.exe /online /Cleanup-Image /StartComponentCleanup /ResetBase

    Please understand I am not advising you to do that. I was just curious if you tried it with the same result.

    Good luck,

    WOT

      My Computers


  3. Posts : 108
    Win10
    Thread Starter
       #3

    Thanks for responding. I see you get around.

    This is the only symptom:

    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 Scheduler under Microsoft, Windows, Servicing.

    Yes, I have considered /ResetBase If I do try it, I will need to do it over a weekend after a full server backup image is completed. However, I expect it won't complete and will result in the same error as the command: DISM /Online /Cleanup-Image /StartComponentCleanup

    The fact that the ComponentCleanup task won't work anymore doesn't appear to be serious. The WinSxS folder will grow over the years - not a big deal. Older Windows didn't even have ComponentCleanup tasks. Just concerned this issue could get worse. Microsoft reports that Error 0x80073712 means "The component store is in an inconsistent state." However, the log after the command DISM /Online /Cleanup-Image /RestoreHealth shows no errors found!

    Just trying to see if there is a solution to this issue. I have found others with the same exact issue (not necessarily same cause of course).

      My Computer


  4. WOT
    Posts : 471
    Win 10 Pro 15063.332 (ex-Insider)
       #4

    OK, thanks for identify the task scheduler failure as the reason for your concern. Who knows, with that additional information, maybe someone here can help you. Good luck with the /resetbase if you try it.

    regards,

    WOT
      My Computers


  5. Posts : 108
    Win10
    Thread Starter
       #5

    -------------------------------------------------------------------------
    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
    -------------------------------------------------------------------------
      My Computer


  6. WOT
    Posts : 471
    Win 10 Pro 15063.332 (ex-Insider)
       #6

    Intrepid1 said:
    -------------------------------------------------------------------------
    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
    -------------------------------------------------------------------------
    WOW, nice work! Glad you got it sorted.

    Regards,

    WOT
      My Computers


  7. Posts : 108
    Win10
    Thread Starter
       #7

    Thanks WOT.
      My Computer


  8. Posts : 102
    Windows 10 Pro 64bits
       #8

    I'm using Windows Security Defender, how to exclude WinSxS folder, because it only excludes files.

    Intrepid1 said:
    -------------------------------------------------------------------------
    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
    -------------------------------------------------------------------------
      My Computer


  9. Posts : 108
    Win10
    Thread Starter
       #9

    Even with the Antivirus exclusions, the issue would come and go. I left the task disabled. Once a month after every windows update and about a half hour after a fresh boot, I would run the following commands from an elevated (administrator) command prompt. Most of the time it works, especially after a reboot. This really only needs to be run a few times a year as it just keeps your Component Store smaller and clean of obsolete updates. In fact, Component Cleanup didn't even exist as an automated task before Server 2012 / Windows 8.

    Dism /Online /Cleanup-Image /RestoreHealth

    And then Run Cleanup:

    DISM /Online /Cleanup-Image /StartComponentCleanup

    If Cleanup fails with a corruptoin message, run this again:
    Dism /Online /Cleanup-Image /RestoreHealth

    And try the whole process again after the next windows update and reboot.

    UPDATE: New version of my AV (ESET File Security for Windows Server) fixed this issue.
    Last edited by Intrepid1; 19 Jan 2019 at 19:24.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 11:16.
Find Us




Windows 10 Forums