Server 2016 help interpreting CBS.log

B

Brian Martin

Member
Joined
Mar 29, 2019
Posts
6
excerpts from the attached log file:

00000039 (F) STATUS_SXS_ASSEMBLY_MISSING #1414175# from CCSDirectTransaction::OperateEnding at index 0 of 1 operations, disposition 2[gle=0xd015000c]

0000003a (F) HRESULT_FROM_WIN32(ERROR_SXS_ASSEMBLY_MISSING) #1414023# from Windows::ServicingAPI::CCSITransaction::ICSITransaction_PinDeployment(Flags = 0, a = ...
fc66b3b1b891f5b2e87aebbe9af52ea5, version 10.0.14393.2430, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}, cb = (null), s = (null), rid = 'Package_76_for_KB4343887~31bf3856ad364e35~amd64~~10.0.1.10.4343887-224_neutral', rah = '2', manpath = (null), catpath = (null), ed = 0, disp = 0)[gle=0x80073701]

Failed to pin deployment while resolving Update: Package_76_for_KB4343887~31bf3856ad364e35~amd64~~10.0.1.10.4343887-224_neutral from file: (null) [HRESULT = 0x80073701 - ERROR_SXS_ASSEMBLY_MISSING]

Failed to bulk stage deployment manifest and pin deployment for package:Package_9140_for_KB4489889~31bf3856ad364e35~amd64~~10.0.1.6 [HRESULT = 0x80073701 - ERROR_SXS_ASSEMBLY_MISSING]




I assume this reads from the bottom up, so.....

Package_9140_for_KB4489889~31bf3856ad364e35~amd64~10.0.1.6 failed because Package 76 failed from KB4343887~31bf3856ad364e35~amd64~10.0.1.10.4343887-224_neutral
Package 76 failed because assembly 1414023 is missing

How do I determine what/where assembly 1414023 is and what to re-install ?
is it in KB4343887 ?
can I get it somwhere else ?
 

Attachments

Hello and welcome!

The issue seems to be the update KB4343887. We will try to search the registry for it and remove it completely and see if the KB4489889 installs then.

FRST Registry Search
1. Click your Start button and choose Control Panel.
2. In the upper right corner ensure the View by: is set to Category.
3. Select the Programs group.
4. Click the Turn Windows features on or off link. This will bring up the Windows Features dialog. Wait until this dialog populates with information. If this does not happen for some reason, please continue with the steps anyway.
Note: This loads your components hive which is what we want. Please keep this dialog open while you perform the remaining steps.
5. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
6. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
7. Copy and paste KB4343887 into the Search box and click the Search Registry button.
8. When the scan is complete a notepad window will open with the results. Please attach this to your next reply. It is saved on your desktop named SearchReg.txt.
9. You may close any remaining open windows now.
 
Step#1 - FRST Fix
NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system
1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
2. Download attached file and save it to the Desktop.
Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop).
3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
4. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.
6. Try updates and if any fail, attach CBS.log.
 

Attachments

some notes ......

I do not need backups or restore points. This is a copy of a vhd only used to test and I have created a checkpoint.
The machine name and IP have been changed on this VM.

I also have teamviewer access if you would rather poke around yourself.....
 

Attachments

I deleted any key within Component Based Servicing that was not en-us

shared is a procmon log after getting "the referenced assembly could not be found" from dism, a registry export, and the bat file used to delete


Shared items ‎4‎-‎5‎-‎2019



Remember, this is a copy of the vhd that I am working on, so I can experiment at will.....
 
I see a missing key:

SFCFix Script

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

  1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the attached file, SFCFixScript.txt, and save this to your Desktop. Ensure that this file is named SFCFixScript.txt - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFixScript.txt.
  5. Drag the file SFCFixScript.txt onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a log should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.
 

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