[SOLVED] sfc errors that I cannot resolve with DISM

K

ksorensen

Member
Joined
Jun 13, 2024
Posts
14
Sine my last issue was resolved here (thanks), the next server I looked at had the exact same issue (sames file and versions) so I re-used the same fix. I am a happy camper.

I have moving on to a new server. It has a very similar issue in that it looks to involve the same batch of initial files, but with a different version number.

As before:

I am unable to launch Check for Updates on my Windows 2019 Datacenter server. A widow comes up but then immediately closes.
SFC /scannow is reporting issues but not fixing them:
DISM is reporting source files that cannot be found

May thanks, in advance,
 

Attachments

  • 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.
  • The file will likely be too large to upload here, if so please upload to a file sharing service.
  • Examples of services to upload to are WeTransfer and TransferKit and SendFileOnline

Please post me the link to the file
 
WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.

  • Download SFCFix.exe and save it to your desktop.
  • Download the attachment SFCFix.zip and also save it on your desktop.
  • Save any work you have open, and close all programs.
  • Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
1p8eDnI.gif

  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt
  • Open the file, then copy and paste its content in your next reply.

Next ...

  • Click Search button and type Command Prompt
  • From the results, right click on the Command Prompt icon, and select Run as administrator
  • A Command Window will open.
  • Copy paste the command below into it, then press Enter
  • Dism /Online /Cleanup-Image /RestoreHealth
  • Once DISM has finished running ...
    • Please attach your ... C:\Windows\Logs\CBS\cbs.log ... to your next reply.
  • If the file is too large, upload it to a file sharing service, and post me the link.
  • Examples of services to upload to are WeTransfer and TransferKit and SendFileOnline
 

Attachments

Something strange showing in your latest CBS log, I need to discuss it with my colleagues.

May be a while before I get back to you.
 
What version of Windows Server are you using ????

I ask this because you have files and registry entries in your logs for both WS2016 and WS2019, which suggests to me that you have been patching this machine with the wrong components.

You stated in your opening post that this is a WS2019 Datacenter version, but your Component Scanner logs shows the machine to be ....

Code: 
Windows Version: Windows Server 2016 Standard x64 (10.0.14393.7070)

... and this seems to be confirmed by the Servicing Stack showing in your CBS.log ....

Code: 
2024-07-12 04:33:55, Info                  CBS    Loaded Servicing Stack v10.0.14393.7060 with Core: C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.14393.7060_none_7f2d1a6021d0f052\cbscore.dll
 
Hmm. My bad on describing it. It is in fact Windows Server 2016 Standard. I cut and pasted from a previous thread. I've been working on a series of machine most of which are Windows Server 2019 Data Center.

I cannot speak to what my predecessor may have tried in the past.
I have not been patching with anything other than the tools within the system (and what you provided based on my info).
We do have a 3rd party patch manager. It had been failing to apply some updates for quite a while. (The patch manager has correctly identified the server as 2016).

It appears that the updates, that were previously failing, succeeded between the time I applied the first fix you provided (so apparently it cleared things up enough for that to run) and applying the second fix file you provided.

This morning, at least one update was in a pending reboot state. I rebooted and ran another DISM health check. It appears all recommended updates have been applied. But, there are still problems reported. A new CBS log file is attached.

My apologies for the confusion.
 

Attachments

Before we do anything else, the first thing we need to do is to remove the files and Registry entries for the WS2019 components I had you install.

Once we've done that, we'll need to search for any other WS2019 components and remove them, but I'd prefer to do that once we've "corrected" things back to how they were when I picked up this topic.

So .....
WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.

  • Download the attachment SFCFixScript.txt and also save it on your desktop.
  • Save any work you have open, and close all programs.
  • Drag the SFCFixScript.txt file over the SFCFix.exe executable and release it.
1p8eDnI.gif

  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt
  • Open the file, then copy and paste its content in your next reply.

Next ...

  • Click Search button and type Command Prompt
  • From the results, right click on the Command Prompt icon, and select Run as administrator
  • A Command Window will open.
  • Copy paste the command below into it, then press Enter
  • Dism /Online /Cleanup-Image /RestoreHealth
  • Once DISM has finished running ...
    • Please attach your ... C:\Windows\Logs\CBS\cbs.log ... to your next reply.
  • If the file is too large, upload it to a file sharing service, and post me the link.
  • Examples of services to upload to are WeTransfer and TransferKit and SendFileOnline
 

Attachments

WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.

  • Download the attachment SFCFixScript.txt and also save it on your desktop.
  • Save any work you have open, and close all programs.
  • Drag the SFCFixScript.txt file over the SFCFix.exe executable and release it.
1p8eDnI.gif

  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt
  • Open the file, then copy and paste its content in your next reply.

Next ...

  • Click Search and type CMD
  • Right click the CMD App from the search results and select Run as Administrator
  • With the App open ...
    • Copy/Paste the following Command into it ...
    • reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS
      • This loads your COMPONENT hive.
    • You can now close the Command window.

  • Next ...

  • Download Farbar Recovery Scan Tool and save it to your Desktop
    • Note: Your antivirus program may report FRST incorrectly as an infection. If so, disable the real-time protection when downloading and running FRST
  • Right-click on FRST64.exe and choose Run as administrator
    • Copy and paste ... SearchAll: 10.0.17763 ... into the Search box.
    • Click the Search Files button.
    • When the scan is complete ...
      • A log will open on your Desktop ... Search.txt
    • Attach the file ... Search.txt ... to your next reply.
  • You may close any remaining open windows now.
 

Attachments

  • Click Search and type CMD
  • Right click the CMD App from the search results and select Run as Administrator
  • With the App open ...
    • Copy/Paste the following Command into it ...
    • reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS
      • This loads your COMPONENT hive.
    • You can now close the Command window.

Next ...

  • Download the attached fixlist.txt and save it to the same location as FRST (must be in same folder or it won't process).
  • NOTICE: This script was written specifically for this user. Running it on another machine may cause damage to your operating system
  • Start and run FRST
  • Now press the Fix button once and wait.
  • FRST will process fixlist.txt
  • When finished, it will produce a log fixlog.txt in the same folder/directory as FRST64.exe
  • Please post me the log
 

Attachments

  • Click Search button and type Command Prompt
  • From the results, right click on the Command Prompt icon, and select Run as administrator
  • A Command Window will open.
  • Copy paste the command below into it, then press Enter
  • Dism /Online /Cleanup-Image /RestoreHealth
  • Once DISM has finished running ...
    • Please attach your ... C:\Windows\Logs\CBS\cbs.log ... to your next reply.
  • If the file is too large, upload it to a file sharing service, and post me the link.
  • Examples of services to upload to are WeTransfer and TransferKit and SendFileOnline

Can you also post me an updated copy of your COMPONENTS hive file please.

  • 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.
  • The file will likely be too large to upload here, if so please upload to a file sharing service.
  • Examples of services to upload to are WeTransfer and TransferKit and SendFileOnline

Please post me the link to the file
 
WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.

  • Download the attachment SFCFix.zip and also save it on your desktop.
  • Save any work you have open, and close all programs.
  • Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
1p8eDnI.gif

  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt
  • Open the file, then copy and paste its content in your next reply.

Next ...

  • Click Search button and type Command Prompt
  • From the results, right click on the Command Prompt icon, and select Run as administrator
  • A Command Window will open.
  • Copy paste the command below into it, then press Enter
  • Dism /Online /Cleanup-Image /RestoreHealth
  • Once DISM has finished running ...
    • Please attach your ... C:\Windows\Logs\CBS\cbs.log ... to your next reply.
  • If the file is too large, upload it to a file sharing service, and post me the link.
  • Examples of services to upload to are WeTransfer and TransferKit and SendFileOnline
 

Attachments

Yes, not showing any errors, so if you can now update then I think we're finished.

Glad we were able to help you with your problem, and thanks for the donation it is much appreciated.
 
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