[SOLVED] DISM RestoreHealth fails (missing catalogs)

wvw · Aug 29, 2024

I'll start the component scan. It takes a full day to complete on this server. If the corruption is so extensive it would take forever to fix, I can write it off as unrecoverable/reimage. I appreciate your help tremendously so far.

Maxstar · Aug 29, 2024

The components hive of this server is pretty big, the latest hive you provided was 1,3 GB in size.
Also a number of components / (very) old updates are missing, so I wonder if this server is mainly used in an offline (network) without internet connection?
Normally after each update a scheduled task will cleanup the WinSxS folder, if that task has been removed it may explain the size of the WinSxS folder and the COMPONENTS hive.

We can try to aplly some more fixes to see if we make some more progess.

wvw · Sep 3, 2024

COMPONENTS.zip

Maxstar · Sep 3, 2024

Hi,

Please do the following again for other components and copy - paste the result in your next post.

Code:

dir /s /a %systemroot%\WinSxS\amd64_microsoft-windows-credprovhost-library_31bf3856ad364e35_10.0.14393.206_none_ed81d9bccbea2686
certutil -hashfile %systemroot%\WinSxS\Manifests\amd64_microsoft-windows-credprovhost-library_31bf3856ad364e35_10.0.14393.206_none_ed81d9bccbea2686.manifest SHA256

dir /s /a %systemroot%\WinSxS\amd64_microsoft-windows-credprovhost-library_31bf3856ad364e35_10.0.14393.1378_none_292b24a388bfcd71
certutil -hashfile %systemroot%\WinSxS\Manifests\amd64_microsoft-windows-credprovhost-library_31bf3856ad364e35_10.0.14393.1378_none_292b24a388bfcd71.manifest SHA256

wvw · Sep 3, 2024

C:\Users\Administrator>dir /s /a %systemroot%\WinSxS\amd64_microsoft-windows-credprovhost-library_31bf3856ad364e35_10.0.14393.206_none_ed81d9bccbea2686
Volume in drive C has no label.
Volume Serial Number is 56D6-2AEA

Directory of C:\Windows\WinSxS\amd64_microsoft-windows-credprovhost-library_31bf3856ad364e35_10.0.14393.206_none_ed81d9bccbea2686

08/29/2024 11:09 AM <DIR> .
08/29/2024 11:09 AM <DIR> ..
0 File(s) 0 bytes

Total Files Listed:
0 File(s) 0 bytes
2 Dir(s) 32,458,067,968 bytes free

C:\Users\Administrator>certutil -hashfile %systemroot%\WinSxS\Manifests\amd64_microsoft-windows-credprovhost-library_31bf3856ad364e35_10.0.14393.206_none_ed81d9bccbea2686.manifest SHA256
SHA256 hash of file C:\Windows\WinSxS\Manifests\amd64_microsoft-windows-credprovhost-library_31bf3856ad364e35_10.0.14393.206_none_ed81d9bccbea2686.manifest:
c74a89e5fc763f8715c09c6afa8118f9334161a24003d19926441161b59f1eb6
CertUtil: -hashfile command completed successfully.

C:\Users\Administrator>dir /s /a %systemroot%\WinSxS\amd64_microsoft-windows-credprovhost-library_31bf3856ad364e35_10.0.14393.1378_none_292b24a388bfcd71
Volume in drive C has no label.
Volume Serial Number is 56D6-2AEA

Directory of C:\Windows\WinSxS\amd64_microsoft-windows-credprovhost-library_31bf3856ad364e35_10.0.14393.1378_none_292b24a388bfcd71

08/29/2024 11:09 AM <DIR> .
08/29/2024 11:09 AM <DIR> ..
0 File(s) 0 bytes

Total Files Listed:
0 File(s) 0 bytes
2 Dir(s) 32,454,508,544 bytes free

C:\Users\Administrator>certutil -hashfile %systemroot%\WinSxS\Manifests\amd64_microsoft-windows-credprovhost-library_31bf3856ad364e35_10.0.14393.1378_none_292b24a388bfcd71.manifest SHA256
SHA256 hash of file C:\Windows\WinSxS\Manifests\amd64_microsoft-windows-credprovhost-library_31bf3856ad364e35_10.0.14393.1378_none_292b24a388bfcd71.manifest:
ea052dc533d6ee2c47e6381a3503f9c45986585e28c57dc3b9c1152ee36a191b
CertUtil: -hashfile command completed successfully.

Maxstar · Sep 3, 2024

Here's the next fix...

Step 1.
Warning: This fix was written specifically for this system. Do not run this fix on another system.

Save any work you have open, and close all programs.
Download the attachment SFCFix.zip and save it to your desktop.
Drag the SFCFix.zip file over the SFCFix.exe executable and release it.

SFCFix will launch, let it complete.
Once done, a file will appear on your desktop, called SFCFix.txt.
Post the logfile (SFCFix.txt) as attachment in your next reply.

Step 2. Run the following DISM command and post the result. If it fails attach a new copy of the CBS log.

Code:

DISM /online /cleanup-image /StartComponentCleanup

wvw · Sep 3, 2024

Deployment Image Servicing and Management tool
Version: 10.0.14393.4169

Image Version: 10.0.14393.4169

[============= 23.8% ]

Error: 14098

The component store has been corrupted.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

Maxstar · Sep 3, 2024

Here's the next fix...

Step 1.
Warning: This fix was written specifically for this system. Do not run this fix on another system.

Save any work you have open, and close all programs.
Download the attachment SFCFix.zip and save it to your desktop.
Drag the SFCFix.zip file over the SFCFix.exe executable and release it.

SFCFix will launch, let it complete.
Once done, a file will appear on your desktop, called SFCFix.txt.
Post the logfile (SFCFix.txt) as attachment in your next reply.

Step 2. Run the following DISM command and post the result. If it fails attach a new copy of the CBS log.

Code:

DISM /online /cleanup-image /StartComponentCleanup

wvw · Sep 3, 2024

Still failing

Maxstar · Sep 3, 2024

Sadly yes, and the previous log shows us:

Rich (BB code):

The following actions will be performed:
    Regeneration Candidates: 2520
    Removal Candidates: 104876
    Superseded/LDR (Delta Compression) Candidates: 6974
    Null-Delta Compression Candidates:
        Mutable file Candidates: 52
        Boot-Recovery Candidates: 602
    Deletion Candidates (Non Driver): 0
    Driver Deletion Candidates: 45
    WinSxS Orphaned Objects Candidates: 1
    Manifests Orphaned Objects Candidates: 0

The latest logs shows:

Rich (BB code):

The following actions will be performed:
    Regeneration Candidates: 2518
    Removal Candidates: 104876
    Superseded/LDR (Delta Compression) Candidates: 6973
    Null-Delta Compression Candidates:
        Mutable file Candidates: 52
        Boot-Recovery Candidates: 602
    Deletion Candidates (Non Driver): 0
    Driver Deletion Candidates: 45
    WinSxS Orphaned Objects Candidates: 1
    Manifests Orphaned Objects Candidates: 0

So we are not making any progress and just for two components each time like post #40.

wvw · Sep 3, 2024

I take it the best solution now is just to reinstall Windows?

Maxstar · Sep 3, 2024

Looking at this case it should be the best solution, such as scheduling regular maintenance and creating backups.

1. The current COMPONENTS hive is 1.4GB and pretty big!
2. And he WinSxS folder ~ 80GB is pretty big too as mentioned in post #5.

Normally Windows will cleanup the WinSXS folder using a scheduled task! Seen the size of the WinSxS folder and HIVE file it seems that this task is missing or never has been fully executed?

wvw · Sep 3, 2024

The task exists but it doesn't have any triggers associated. I'm not sure how long the components store has been broken and growing. Thanks for your efforts anyway Max. I will try to get this server replaced.

Maxstar · Sep 4, 2024

It seems the components store is broken for many years seen the very old updates which are reported, and many of them are already pulled from the update catalog. Replacing / reinstalling this server should be the best option.

Search

Search

[SOLVED] DISM RestoreHealth fails (missing catalogs)

wvw

Active member

Maxstar

Windows Update Moderator, Security Analyst

wvw

Active member

Attachments

Maxstar

Windows Update Moderator, Security Analyst

wvw

Active member

Maxstar

Windows Update Moderator, Security Analyst

Attachments

wvw

Active member

Attachments

Maxstar

Windows Update Moderator, Security Analyst

Attachments

wvw

Active member

Attachments

Maxstar

Windows Update Moderator, Security Analyst

wvw

Active member

Maxstar

Windows Update Moderator, Security Analyst

wvw

Active member

Maxstar

Windows Update Moderator, Security Analyst