[SOLVED] SFCfix crashes

C:\>DISM /online /cleanup-image /RestoreHealth

Deployment Image Servicing and Management tool
Version: 10.0.17763.3406

Image Version: 10.0.17763.3887

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

C:\>reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS
The operation completed successfully.

Started FRST with default options as administrator
 

Attachments

Please post a new copy of the COMPONENTS hive to look at.

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.
 
I've copy and paste a wrong "value name" for the last REG search. Please perform the following steps again.

1. Start the
55d04c7d453ca-Command_prompt_icon_%28windows%29.png
Command Prompt as administrator.
  • Open the startmenu and type the command cmd.
  • After you find the Command Prompt, right click on it and select Run as Administrator.
  • Copy and paste the following into the Command Prompt and press enter.
Code: 
reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS
2.Right-click on the file
577bf0efb8088-FRST.png
FRST.exe and choose Run as administrator.
  • Copy and paste the following (code) into the Search box and click the Search Registry button.
Code: 
InstallMapMissingComponentKey
  • When the scan is complete, a message will display that SearchReg.txt is saved in the same folder FRST was started from.
  • Post the logfile SearchReg.txt as attachment in your next reply.
 
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.

Afterwards reboot the server and attempt to update again. If it fails attach a new copy of the CBS log(s) and a new copy of the COMPONENTS hive.
 

Attachments

SFCfix still running... you don't want me to check with DISM before I attempt a Windows Update?
 
This fix can take some time so please wait! There's no need to run DISM this time before attempting to update, only a reboot.
 
- SFCfix
- Reboot
Just to be clear... I should NOT reset Software Distribution folder first?

Following is pending install (didn't do a WUP yet, just opened WUP) ... 2023-03 Samlet opdatering til Windows Server 2019 (1809) til x64-baserede systemer (KB5023702).

Danish update 😅
 
There is no need to delete files form the SoftwareDistribution folder. I would just try to update and see what happens now?
kimenemark said:
til x64-baserede systemer (KB5023702).

Danish update 😅
Click to expand...

This is almost similar to Dutch: gebaseerde systemen = baserede systemer... So I can read it a little bit... ;)
 
2023-03 Cumulative Update for Windows Server 2019 (1809) for x64-based Systems (KB5023702) - Error 0x80073701

At least it didn't crash this time 😅

Sending info asap... currently on slow connection :whistle: 😅
 
Please run the following tool as well.

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.
 
Rich (BB code): 
2023-04-09 16:29:43, Error                 CSI    0000003c (F) STATUS_SXS_ASSEMBLY_MISSING #3766238# from CCSDirectTransaction::OperateEnding at index 0 of 1 operations, disposition 2[gle=0xd015000c]
2023-04-09 16:29:43, Error                 CSI    0000003d (F) HRESULT_FROM_WIN32(ERROR_SXS_ASSEMBLY_MISSING) #3766080# from Windows::ServicingAPI::CCSITransaction::ICSITransaction_PinDeployment(Flags = 0, a = 52525d8a3f5d37e85f1bbf1c1ac7610a, version 10.0.17763.3887, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}, cb = (null), s = (null), rid = 'Package_992_for_KB5022286~31bf3856ad364e35~amd64~~10.0.1.7.5022286-1966_neutral', rah = '2', manpath = (null), catpath = (null), ed = 0, disp = 0)[gle=0x80073701]
2023-04-09 16:29:43, Info                  CBS    Failed to pin deployment while resolving Update: Package_992_for_KB5022286~31bf3856ad364e35~amd64~~10.0.1.7.5022286-1966_neutral from file: (null) [HRESULT = 0x80073701 - ERROR_SXS_ASSEMBLY_MISSING]
2023-04-09 16:29:43, Info                  CBS    Failed to bulk stage deployment manifest and pin deployment for package:Package_8951_for_KB5023702~31bf3856ad364e35~amd64~~10.0.1.10 [HRESULT = 0x80073701 - ERROR_SXS_ASSEMBLY_MISSING]

Please perform the following to take a look at KB5022286, because the COMPONENTS hive is replaced from another fully patched server.

Follow these instructions to remove an update.
  • Open the Start menu of Windows and type the command CMD
  • When you see Command Prompt on the list, right-click on it and select Run as administrator.
  • When command prompt opens, copy and paste the following command into it, then press enter.
Code: 
wusa /uninstall /KB:5022286
  • Let me know if it says it was successful or you get the message: The update KB5022286 is not installed on this computer.
 
KB5023702 still fail...

2023-03 Cumulative Update for Windows Server 2019 (1809) for x64-based Systems (KB5023702) - Error 0x800706be
 
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