[SOLVED] Server 2016 (1607) RestoreHealth missing components

[Maxstar]

I'm fixing these servers as and when I find them. The one I fixed earlier this week went from 63GB WinSxS down to 8GB.

Did you use any (third-party) toolkit/script to clean-up or compress the WinSxS folder?

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.

DISM /online /cleanup-image /RestoreHealth

 

[cavaliersa]

Did you use any (third-party) toolkit/script to clean-up or compress the WinSxS folder?

No, just got SFC clean, DISM scan clean, then StartComponentCleanup followed up with StartComponentCleanup /ResetBase.

 

[cavaliersa]

Here is the latest missing file.

(p) CSI Payload Corrupt amd64_microsoft-windows-s..-servicehostbuilder_31bf3856ad364e35_10.0.14393.0_none_51b695a02ec0d850\Windows.Shell.ServiceHostBuilder.dll
Repair failed: Missing replacement payload.

 

[Maxstar]

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.

DISM /online /cleanup-image /RestoreHealth

 

[cavaliersa]

Thanks, I'm almost thinking of asking for amd64_microsoft-windows-*_31bf3856ad364e35_10.0.14393.0_*
Running this file now.

 

[Maxstar]

What about thinking of format C:

 

[cavaliersa]

haha... true. I would if I could.

 

[Maxstar]

I will see if I can upload a copy of the WinSXS folder of my VM to use as source with DISM, it seems you'll need a number of uncompressed files...

 

[cavaliersa]

That would be brilliant if you could! I was going to ask how and where you are sourcing these from. I had though that if I build a VM and install the same features that it would have all the files I need but this wasn't the case.

Should I hold off posting the next one for now?

 

[Maxstar]

Hi,

I have uploaded a copy of the WinSxS folder to my PCloud drive: WinSxS.7z - Shared with pCloud

Let me know the result of DISM when you use this folder as source and/or if you are still missing uncompressed RTM payloads.

 

[cavaliersa]

Thank you, I'm doing so now

 

[Maxstar]

Let's hope it will speed up some things since DISM reported only 1 or 2 files after each run...

 

[cavaliersa]

I have a suspicion that it is going to take a few runs, but will keep you posted and show the before and after results.
I really appreciate the continued help and things I'm learning about working with these things.

 

[cavaliersa]

So I ended up scripting a loop for this, it took roughly 50 or so RestoreHealth executions to allow StartComponentCleanup to complete as expected.

Function WriteLastLines () {
    param (
        [array] $InputArray
    )
    $lineCount = 0
    [array]::Reverse($InputArray)
    ForEach ($line In $InputArray) {
        If ($line.StartsWith("[")) {Break}
        $lineCount++
    }
    [array]::Reverse($InputArray)
    For ($i=($InputArray.GetUpperBound("") - $lineCount);$i -le ($InputArray.GetUpperBound(""));$i++) {
        Write-Host $InputArray[$i]
    }
}

$clean = "The component store has been corrupted."
$restore = "The restore operation completed successfully."
while ($clean.Contains("The component store has been corrupted.") -And $restore.Contains("The restore operation completed successfully.")) {
    $counter++
    Write-Host "$(Get-Date -Format "yyyy-MM-dd HH:mm:ss") | $counter | Restore"
    $restore = @(dism /online /cleanup-image /restorehealth /Source:E:\winsxs /LimitAccess)
    WriteLastLines $restore
    Write-Host "$(Get-Date -Format "yyyy-MM-dd HH:mm:ss") | $counter | Clean"
    $clean = @(dism /online /cleanup-image /startcomponentcleanup)
    WriteLastLines -InputArray $clean
    PAUSE
}

With this done ResetBase could go through and the repository was suitably reduced.
Before


After


Never mind the space, but the difference this makes to machine performance is huge... I really love getting these machines sorted properly.
Thanks @Maxstar, for the awesome help!
I would really like to learn more about the component based servicing stuff and be more of a contributor to these forums (than a help requestor).

 

[Maxstar]

Hi,

You're welcome. Glad you have managed to resolve the issues with this server...

To learn more about Windows Update and if you want to become a volunteer here you can sign-up for the Windows Update Academy.

I will mark this thread as solved.