[SOLVED] Server 2016 - "Component Corruption" errors during update

G

GrantCornelius

Member
Joined
Dec 21, 2023
Posts
11
Server: 1607 OS Build 14393.5717

sfc /scannow - 14098 Error
Unable to install updates through GUI or manually downloaded MSU files.
"System Component Corruption" errors with no indication whatsoever as to what is corrupted.
 
Hi and welcome to Sysnative,

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,

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

Please run the following DISM command first and post the result. If it fails attach a new copy of the CBS log.
Code: 
DISM /online /cleanup-image /RestoreHealth
 
Updates installed without Issue! (Can't believe it was two dirty REG Entries.) Thank you, thank you, thank you!

Unless you have anything additional you need/want me to check, this appears to be fixed now.
 
Please run DISM as suggested in my previous post as well, just to be sure there are no remaining corruptions.
 
Well, darn, DISM did indeed fail. Out pt of command below, attaching the log as well.

dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.14393.4169

Image Version: 10.0.14393.4169

[==========================100.0%==========================]
Error: 0x800f081f

The source files could not be found.
Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see Configure a Windows Repair Source.

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

Attachments

Hi.

Please attach the latest CBS logs, the DISM log is not very heplful since it always refer to the CBS log...

Rich (BB code): 
2023-12-29 09:16:01, Error                 DISM   DISM Package Manager: PID=5772 TID=416 Failed while processing command cleanup-image. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800f081f)
2023-12-29 09:16:01, Info                  DISM   DISM Package Manager: PID=5772 TID=416 Further logs for online package and feature related operations can be found at %WINDIR%\logs\CBS\cbs.log

Upload a copy of the CBS folder
  • 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.
653a64385d891-618e949e09fef-CBS-Folder.png

  • Attach the file CBS.zip to your next reply.
 
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.
650c22f99662d-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

Oops I forgot to copy and paste the download link in my canned speech. But here it is..

Download
6530fbb0f4101-56f31e53c97da-SFCFix.PNG
SFCFix and save it to your desktop.
 
Disregard last post, I was able to locate the download in another thread.
DISM Results: "The operation completed successfully." "Yay!!!!"
Looks like that's good. Any point in running either a component health scan or an SFC ?
 
When DISM completed successfully without any issues it looks good to me, but let's run SFC /Scannow as well to see if it come back clean as well!
 
Great! Are there any remaining issues or is everything up and running and up-to-date? If so, then we can mark this as solved!
 
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