Server 2016 (1607 OS Build 14393.3474)

O

omegace

Active member
Joined
Jan 9, 2023
Posts
30
Can't seem to upgrade a server 2016 system to latest updates. Have tried to apply both Cumulative Updates and Service Stack updates from about 1/2020 and present. SFC and DISM have been run multiple times but generally produce errors; in one instance SFC did say it repaired items but then went back to it could not and DISM usually always produces a 1726 error. Have also tried to reset Windows Update components, but no change (all steps completed successfully)

Attached are the SFC and DISM logs.

Thanks
 

Attachments


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 for the reply. Here is the attached SFCFix.txt. I then ran the DISM which completed successfully. I was able to install at least one update via MS Updates for the office products. I am however, unable to install any servicing stack updates or recent cumulative updates (it states not applicable for the computer). Is there anything more to do?

Thanks
 

Attachments

Hi,

Please provide a new copy of the CBS logs.
  • Open Windows Explorer and browse to the C:\Windows\Logs folder.
  • Right-click on the CBS folder and choose Send to > Compressed (zipped) folder.
  • Now the message will appear, "Windows cannot create the Compressed (zipped) Folder here. Do you want it to be placed on the desktop instead?"
  • Click on the Yes button here.
618e949e09fef-CBS-Folder.png

  • Attach the file CBS.zip to your next reply.
 
Rich (BB code): 
2023-01-12 11:32:54, Info                  CBS    Failed to find a matching version for servicing stack: C:\windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.14393.4349_none_7f09d74e21ec00ab\ [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
2023-01-12 11:32:54, Info                  CBS    Failed to find servicing stack directory in online store. [HRESULT = 0x80070490 - ERROR_NOT_FOUND]

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.


Open an elevated command prompt and run the following command. Attach Dirlist.txt to your next post.
Code: 
dir /s /a %systemroot%\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.14393.4349_none_7f09d74e21ec00ab > "%userprofile%\Desktop\Dirlist.txt"
 
Hi,

Please run the following script with FRST to get some more info about the Servicing Stack versions.

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.
 

Attachments

Rich (BB code): 
========= reg query "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Version" /s =========

ERROR: The system was unable to find the specified registry key or value.

Export CBS (Component Based Servicing) hive
  • Click on the Start button and type regedit
  • When you see regedit on the list, right-click on it and select Run as administrator.
  • When regedit opens, using the left pane, navigate to the following registry key and select it by clicking on it once.
    Code: 
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing
  • Once selected, click File > Export....
  • Change the Save as type: to Registry Hive Files (*.*).

    622dbef75cd3a-Export-CBS-hive.png

  • Name this file ComponentBasedServicing (with no file extension) and save it to your Desktop.
  • Right-click on the saved file and choose Send > Compressed (zipped) Folder.
  • Attach the .ZIP file to your next post.
  • If the file is too large to upload here, upload the file to www.wetransfer.com and post the link in your next reply.
 
I think I have some bad news, the Component Based Servicing hive is damaged beyond repair, it is just 136kB and several (complete) subkeys are missing.
 
What would be the best way of repairing? This is an RDS server (one of two that are nearly identical). Can the CBS hive from the other be copied over and replace the bad one?
 
Is it possible to use this CBS registry hive, from the other RDS server? This appears to be much larger.
 

Attachments

The possibilities of fixing this issue are next to nil. Do you have backups of the registry before the issue occured 2019/2020?

RDS2 (CBSTest.hive) is fully up-to-date so it seems? Due to the difference you cannot use it as donor/replacement. In cases like this there is no other way than rebuild te server from scratch.
 
Could you please provide the COMPONENTS hive of this backup as well - timestamp 2020/3/11:20:59:12.564 10.0.14393.3320 (rs1_release.191010-1741)
 
Hi,

Unfortunately, there is no way to rebuild the Component Based Servicing hive, the back-up is too old to use. So the only remaining option is a repair or clean install.
 
  • Sad
Reactions: tmp
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