[SOLVED] SFC and DISM issues on Server 2019

[Sysnative Windows Update]

Can I see the CBS.log please?

 

[gchq]

Attached

 

[gchq]

This is what I should be seeing with Server 2019, based on the applied settings - so why that one is doing it's own thing is another mystery

 

[Sysnative Windows Update]

I see the problem. There is a missing key in the registry. Can you upload the components hive from one of the healthy Servers so I can extract it?

Retrieve Components Hive
1. Navigate to C:\Windows\System32\Config and locate the COMPONENTS file.
2. Please copy this file to your desktop.
Note: If you receive an error that this file is in-use, simply reboot your computer and try again.
3. Right-click on this file on your desktop and select Send To...Compressed (zipped) folder. This will create a file named COMPONENTS.ZIP on your desktop.
4. The file will likely be too large to upload here so please upload to a file sharing service. Examples of services to upload to are Dropbox or OneDrive or SendSpace and then just provide the link in your reply.

 

[gchq]

Have PM'd the link to you

 

[Sysnative Windows Update]

Did you make sure that the link is not to the hive from the Server we are fixing?

 

[gchq]

Yes - another Server 2019 box that downloads updates only

 

[Sysnative Windows Update]

Okay. Please allow me some time to research.

Thank you.

 

[gchq]

I will check back in the morning
Components.zip was from the problem child
Components1.zip is from the good server

 

[Sysnative Windows Update]

SFCFix Script

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
2. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
3. Save any open documents and close all open windows.
4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
5. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
6. SFCFix will now process the script.
7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.

 

[gchq]

SFCFix version 3.0.2.1 by niemiro.
Start time: 2019-12-19 13:47:44.151
Microsoft Windows Server 10 Build 17763 - amd64
Using .zip script file at C:\Downloads\SysNative\SFCFix.zip [0]


PowerCopy::
Successfully took permissions for file or folder C:\WINDOWS\WinSxS\msil_microsoft.powershell.psreadline_31bf3856ad364e35_10.0.17763.1_none_614e177b40342144\Microsoft.PowerShell.PSReadline.dll
Successfully took permissions for file or folder C:\WINDOWS\WinSxS\msil_microsoft.powershell.psreadline_31bf3856ad364e35_10.0.17763.1_none_614e177b40342144\PSReadLine.format.ps1xml
Successfully took permissions for file or folder C:\WINDOWS\WinSxS\msil_microsoft.powershell.psreadline_31bf3856ad364e35_10.0.17763.1_none_614e177b40342144\PSReadline.psd1
Successfully took permissions for file or folder C:\WINDOWS\WinSxS\msil_microsoft.powershell.psreadline_31bf3856ad364e35_10.0.17763.1_none_614e177b40342144\PSReadline.psm1
Successfully took permissions for file or folder C:\WINDOWS\WinSxS\amd64_microsoft-windows-peertopeerpnrp_31bf3856ad364e35_10.0.17763.1_none_6244ff987a9e0105\pnrpnsp.dll
Successfully copied file C:\Users\Dave\AppData\Local\niemiro\Archive\WinSxS\msil_microsoft.powershell.psreadline_31bf3856ad364e35_10.0.17763.1_none_614e177b40342144\Microsoft.PowerShell.PSReadline.dll to C:\WINDOWS\WinSxS\msil_microsoft.powershell.psreadline_31bf3856ad364e35_10.0.17763.1_none_614e177b40342144\Microsoft.PowerShell.PSReadline.dll.
Successfully copied file C:\Users\Dave\AppData\Local\niemiro\Archive\WinSxS\msil_microsoft.powershell.psreadline_31bf3856ad364e35_10.0.17763.1_none_614e177b40342144\PSReadLine.format.ps1xml to C:\WINDOWS\WinSxS\msil_microsoft.powershell.psreadline_31bf3856ad364e35_10.0.17763.1_none_614e177b40342144\PSReadLine.format.ps1xml.
Successfully copied file C:\Users\Dave\AppData\Local\niemiro\Archive\WinSxS\msil_microsoft.powershell.psreadline_31bf3856ad364e35_10.0.17763.1_none_614e177b40342144\PSReadline.psd1 to C:\WINDOWS\WinSxS\msil_microsoft.powershell.psreadline_31bf3856ad364e35_10.0.17763.1_none_614e177b40342144\PSReadline.psd1.
Successfully copied file C:\Users\Dave\AppData\Local\niemiro\Archive\WinSxS\msil_microsoft.powershell.psreadline_31bf3856ad364e35_10.0.17763.1_none_614e177b40342144\PSReadline.psm1 to C:\WINDOWS\WinSxS\msil_microsoft.powershell.psreadline_31bf3856ad364e35_10.0.17763.1_none_614e177b40342144\PSReadline.psm1.
Successfully copied file C:\Users\Dave\AppData\Local\niemiro\Archive\WinSxS\amd64_microsoft-windows-peertopeerpnrp_31bf3856ad364e35_10.0.17763.1_none_6244ff987a9e0105\pnrpnsp.dll to C:\WINDOWS\WinSxS\amd64_microsoft-windows-peertopeerpnrp_31bf3856ad364e35_10.0.17763.1_none_6244ff987a9e0105\pnrpnsp.dll.
Successfully restored ownership for C:\WINDOWS\WinSxS\msil_microsoft.powershell.psreadline_31bf3856ad364e35_10.0.17763.1_none_614e177b40342144\Microsoft.PowerShell.PSReadline.dll
Successfully restored permissions on C:\WINDOWS\WinSxS\msil_microsoft.powershell.psreadline_31bf3856ad364e35_10.0.17763.1_none_614e177b40342144\Microsoft.PowerShell.PSReadline.dll
Successfully restored ownership for C:\WINDOWS\WinSxS\msil_microsoft.powershell.psreadline_31bf3856ad364e35_10.0.17763.1_none_614e177b40342144\PSReadLine.format.ps1xml
Successfully restored permissions on C:\WINDOWS\WinSxS\msil_microsoft.powershell.psreadline_31bf3856ad364e35_10.0.17763.1_none_614e177b40342144\PSReadLine.format.ps1xml
Successfully restored ownership for C:\WINDOWS\WinSxS\msil_microsoft.powershell.psreadline_31bf3856ad364e35_10.0.17763.1_none_614e177b40342144\PSReadline.psd1
Successfully restored permissions on C:\WINDOWS\WinSxS\msil_microsoft.powershell.psreadline_31bf3856ad364e35_10.0.17763.1_none_614e177b40342144\PSReadline.psd1
Successfully restored ownership for C:\WINDOWS\WinSxS\msil_microsoft.powershell.psreadline_31bf3856ad364e35_10.0.17763.1_none_614e177b40342144\PSReadline.psm1
Successfully restored permissions on C:\WINDOWS\WinSxS\msil_microsoft.powershell.psreadline_31bf3856ad364e35_10.0.17763.1_none_614e177b40342144\PSReadline.psm1
Successfully restored ownership for C:\WINDOWS\WinSxS\amd64_microsoft-windows-peertopeerpnrp_31bf3856ad364e35_10.0.17763.1_none_6244ff987a9e0105\pnrpnsp.dll
Successfully restored permissions on C:\WINDOWS\WinSxS\amd64_microsoft-windows-peertopeerpnrp_31bf3856ad364e35_10.0.17763.1_none_6244ff987a9e0105\pnrpnsp.dll
PowerCopy:: directive completed successfully.


Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 21 datablocks.
Finish time: 2019-12-19 13:47:46.073
Script hash: l93QKeFvkMC+k/pXGpWqCG1bbAz32+EG9Hvr4aBM3zI=
----------------------EOF-----------------------

 

[Sysnative Windows Update]

Thanks. Retry updates.

 

[gchq]

It tells lies



… at least according to the history



… so clicked 'check for updates


… and the result

 

[Sysnative Windows Update]

Okay. Let's see the new CBS.log.

 

[gchq]

Attached

 

[Sysnative Windows Update]

FRST Registry Search
1. Click your Start button and type in cmd.
2.After you find the Command Prompt, right click on it and select Run as Administrator.
3. Copy and paste the following into the Command Prompt:

reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS

4. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
5. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
6. Copy and paste 10.0.17763.253 into the Search box and click the Search Registry button.
7. When the scan is complete a notepad window will open with the results. Please attach this to your next reply. It is saved on your desktop named SearchReg.txt.

 

[gchq]

Is it still confused about what version it is?

 

[Sysnative Windows Update]

There is a very specific key missing and I can't find it on any of the Servers I have, which is strange. Can you please execute the same registry search on the other Server(s) and attach the results for comparison purposes?

 

[gchq]

It probably goes back to the time when it would BSOD at every update attempt - when the in-place upgrade finally resolved the BSOD issues then the annoying 'feature' of automatically installing updates started and various methods to cure that were tried. I seem to remember one was a registry change and prior to the upgrade there was a utility to hide updates.

Let me see if I can find some details, as that might be a clue to all this

 

[Sysnative Windows Update]

Basically, what is happening is, one part (I am only seeing one for now) is missing and once we replace it, the updates should move along. Whether that means to a different error or to a completion, I am not sure yet, but what I do know is there is a registry key missing. If nothing else works, I may be able to bypass it.