[SOLVED] Windows Server 2016 - Windows Update broken for years on domain controller

D

Durando

Active member
Joined
Aug 18, 2023
Posts
30
A client has decided it's finally time to update their servers. Great! Except Windows Update has been broken for years on this DC and I'm not even certain how to get Windows Update working again.

I've tried my best to fix all the corruptions in WinSXS on this server by compiling multiple Server 2016 install WIM files and feeding them through DISM. There are two files that I can't track down, though. One happens to be "amd64_microsoft-windows-s..rdatacenter-license_31bf3856ad364e35_10.0.14393.2938_none_0f8e3c3d8f\ServerDatacenter-ppdlic.xrm-ms"; the other's in the same folder but I forget its name. SFC dies at about 36%. Also upon seeing corruption in the Components hive using ComponentsScanner, I've decided it would be in my best interest to be posting here.

Please note that the attached "CBS.zip" also includes the DISM folder as well.
 

Attachments

Update: The other file I was looking for is probably "amd64_microsoft-windows-s..rdatacenter-license_31bf3856ad364e35_10.0.14393.2938_none_0f8e3c3d8f\DefaultPpd-ServerDatacenter-ppdlic.xrm-ms"
 
Bumping. Please let me know if there's anything else I can do to assist the helpers.
 
Hi and welcome to Sysnative,

Step 1. Download
56f31e53c97da-SFCFix.PNG
SFCFix and save it to your desktop.

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.
6190d993a26f3-SFCFix-Zip-Eng.gif

  • 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 /RestoreHealth
 

Attachments

Thanks kindly for the files. The SFCFix operation completed, as well as the DISM command, but SFC still dies at the same place (36%). See attachments.

The last error reported during the SFC scan was:
2023-08-24 11:22:10, Error CSI 000030f0@2023/8/24:16:22:10.122 (F) onecore\base\wcp\componentstore\deltastore.cpp(2483): Error STATUS_INVALID_PARAMETER originated in function ComponentStore::CRawStoreLayout:: DecompressFile expression: Parameter check failed
 

Attachments

Hi,

Step 1. Upload your COMPONENTS hive.
  • Navigate to C:\Windows\System32\Config and locate the COMPONENTS file.
  • 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.
  • 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.
  • If the file is too large to upload here, upload the file to www.wetransfer.com and post the link in your next reply.


Step 2. Please run the SFC again with Process Monitor running.
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Run the System File Checker just like you have in the past. But wait 30 seconds > 1 minute to stop te trace.
3. Then Stop Process Monitor You can simply do this by clicking the square (CTRL +E) on the toolbar as shown below.



4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine.
5. Zip up the LogFile.PML and upload it to WeTransfer - Send Large Files & Share Photos Online - Up to 2GB Free and provide the link.
 
Hi,

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 SFCFixScript.txt and save it to your desktop.
  • Drag the SFCFixScript.txt file over the SFCFix.exe executable and release it.
62151e1bebac4-SFCFix-Txt-Eng.gif

  • 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 System File Checker Again with Process Monitor running and post the result. If it fails attach a new copy of the *.PML file.
Code: 
SFC /Scannow
 

Attachments

I am happy to report that SFC completed its scan without any problems.

I am going to attempt to install the August 2023 cumulative update for Windows Server 2016.
 

Attachments

KB5029242 is in the Staged state and I will report back after the restart, after close of business.
 
Thank you kindly Maxstar, the server now has KB5029242 installed on it (wmic qfe reports it as installed, and it's in Windows Update's Update History).
 
Hi,

You're welcome. Glad KB5029242 installed without any issues, could you please run ComponentsScanner again? Just to see if earlier issues/warnings are still reported.

Download
61f7aba7309a1-ComponentsScanner_Icon.png
ComponentsScanner and save it to your desktop.
  • Right-click ComponentsScanner.exe and select "Run as administrator", click Yes on the UAC (User Account Control) prompt which appears.
  • Follow the on-screen instructions.
  • Once complete, a report will be saved to your desktop called ComponentsScanner.txt.
  • Post the logfile ComponentsScanner.txt as attachment into your next reply.
 
Please provide a new copy of the COMPONENTS hive to look at the corrupt (RTM) key.

Upload your COMPONENTS hive.
  • Navigate to C:\Windows\System32\Config and locate the COMPONENTS file.
  • 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.
  • 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.
  • If the file is too large to upload here, upload the file to www.wetransfer.com and post the link in your next reply.
 
Hi,

Here's the fix to repair the corrupt key, the warnings are related to older updates so we can ignore them.

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 SFCFixScript.txt and save it to your desktop.
  • Drag the SFCFixScript.txt file over the SFCFix.exe executable and release it.
62151e1bebac4-SFCFix-Txt-Eng.gif

  • 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
61f7aba7309a1-ComponentsScanner_Icon.png
ComponentsScanner again.
  • Right-click ComponentsScanner.exe and select "Run as administrator", click Yes on the UAC (User Account Control) prompt which appears.
  • Follow the on-screen instructions.
  • Once complete, a report will be saved to your desktop called ComponentsScanner.txt.
  • Post the logfile ComponentsScanner.txt as attachment into your next reply.
 

Attachments

Please try the following script with FRST.

Download the
577bf0efb8088-FRST.png
Farbar Recovery Scan Tool and save it to your Desktop:

Download the 64 bit version: - Farbar Recovery Scan Tool Link

Warning: This script was written specifically for this system. Do not run this script on another system.

  • Download the attachment fixlist.txt and save it to your desktop.
  • Right-click on FRST.exe and select "Run as administrator".
  • Press the Fix button.
  • If for some reason the tool needs a restart, please make sure you let the system restart normally.
  • When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
  • Post the logfile Fixlog.txt as attachment in your next reply.

Run
61f7aba7309a1-ComponentsScanner_Icon.png
ComponentsScanner again.
  • Right-click ComponentsScanner.exe and select "Run as administrator", click Yes on the UAC (User Account Control) prompt which appears.
  • Follow the on-screen instructions.
  • Once complete, a report will be saved to your desktop called ComponentsScanner.txt.
  • Post the logfile ComponentsScanner.txt as attachment into your next reply.
 

Attachments

You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top